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.

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

Hello there! #1

Open
mpasternak opened this issue Feb 8, 2024 · 0 comments
Open

Hello there! #1

mpasternak opened this issue Feb 8, 2024 · 0 comments

Comments

@mpasternak
Copy link

mpasternak commented Feb 8, 2024

Not really an issue, just trying to share some thoughts...

I thought about it for some time. The "seeds" as you call them could be auto-generated for example with every 10 transactions and used automatically by the CI server. I think I tried something similar for some time... and then I had to install my project from scratch on the clean database and suddenly the migrations didn't work. So I realized, I need to test those too.

I perform a single createdb and then I clone it. But the seeds... "migration checkpoints" as I called them... do you think they could be created automatically somehow? In other words... what needs to be done in your opinion so we could have the functionality of demo-django-seed-db in the mainline Django sources?

EDIT: "migrating to 0005_wtf_lol took more than 10 seconds, saving a checkpoint". But the time really means nothing in a multi-tasking environment, it could be lagging because of anything...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant