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
If "database": "name" is not specified in database.json, tables are not created nor dropped during migration but it gives the indication that it does by giving the same "Processed migration ..." message.
Expected behavior
Migration should fail with appropriate message.
Minimal reproduction of the problem with instructions
What is the motivation / use case for changing the behavior?
Was experimenting if can get migration to create the database, so removed the database field. After created database via command line, forgot to enter it. Debugging would have been much easier had it failed with message.
Environment
node 9.3, OSX High Sierra
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I'm submitting a...
Current behavior
If "database": "name" is not specified in database.json, tables are not created nor dropped during migration but it gives the indication that it does by giving the same "Processed migration ..." message.
Expected behavior
Migration should fail with appropriate message.
Minimal reproduction of the problem with instructions
As specified above with pg. database.json used:
What is the motivation / use case for changing the behavior?
Was experimenting if can get migration to create the database, so removed the database field. After created database via command line, forgot to enter it. Debugging would have been much easier had it failed with message.
Environment
node 9.3, OSX High Sierra
The text was updated successfully, but these errors were encountered: