Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Migrate development data #345

Open
g105b opened this issue Mar 16, 2023 · 0 comments
Open

Migrate development data #345

g105b opened this issue Mar 16, 2023 · 0 comments
Labels
enhancement question

Comments

@g105b
Copy link
Member

g105b commented Mar 16, 2023

I'm finding it more and more useful to have some pre-seeded fake data in the database during development, but this sort of data can't end up in a migration.

Would it be a good idea to have a query/_migration/dev directory to apply AFTER the migration completes for the first time (or with --force), that's only applied on development - maybe with a --dev flag?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@g105b