You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there – is there any way we could run this against an existing database (with a flag or something is fine) and not get errors? We'd like to add this to our migrations in our dev environments, but we end up having to create a new database, then import it into the primary db.
We'd be happy to make adjustments in a PR if you want to outline the easiest / best way to do so. Thanks :)
The text was updated successfully, but these errors were encountered:
Great to hear from users :) And it does make sense to be able to opt-out of db creation.
So these couple of days are going to be a bit hectic for me, thus I can take this on coming weekend to see what's the best way to do it..
My gut says that in every type of {database}_handler.py you will find a method that sort of does:
CREATE DATABASE {random_db_name here or the one that the user provides from --db}
Instead of directly going that route, fake2db checks if --db flag exists and then should check if a database already exists with that name. Then ofc instead of creation just setup the connection to the existing --db name
Hey there – is there any way we could run this against an existing database (with a flag or something is fine) and not get errors? We'd like to add this to our migrations in our dev environments, but we end up having to create a new database, then import it into the primary db.
We'd be happy to make adjustments in a PR if you want to outline the easiest / best way to do so. Thanks :)
The text was updated successfully, but these errors were encountered: