db:create always returns with exit code 1
See original GitHub issueI’m submitting a…
- Bug report
- Feature request
- Question
Current behavior
db-migrate db:create asdf
return with exit code 1
Expected behavior
db-migrate db:create asdf
return with exit code 0
What is the motivation / use case for changing the behavior?
Exit code else then 0 stands for an error. Therefore some tools fail if the called command exits with error (return code not 0).
Environment
db-migrate version: 0.10.5
Additional information:
- Node version: v9.7.1
- Platform: Linux
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
SQLite db create error in real iOS device - Stack Overflow
If a query ever fails, I would call sqlite3_errmsg to get the error reported by SQLite. If open fails, always call sqlite3_close ....
Read more >How to Fix 'Terminated With Exit Code 1' Error - Komodor
Exit Code 1 indicates that a container shut down, either because of an application failure or because the image pointed to an invalid...
Read more >dbcreate() - CA-Clipper 5.3 . Guide To CA-Clipper - Long Entry
Returns DBCREATE () always returns NIL. Description DBCREATE() is a database function that creates a database file from an array containing the structure...
Read more >MySQL shared library error with Ruby on Rails - Databases
Hi, I'm getting this issue appearing at the point of test database creation. I'm not using a circle.yml. The 'undefined symbol' changes on ......
Read more >IBM Informix Messages and Corrections
-1 Not owner. An operating-system error code with the meaning shown was unexpectedly returned to the database server. Check the ownership and permissions...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@wzrdtales is there any progress made on this issue? if not, I may be able to help. Looking to use this functionality in an npm script and it functions correctly besides the exit status.
0.11.3 should deal with it. thanks for your patience though, I hope to be able to reserve more time, or find a good sponsor so I can finally push the pending changes through 😃