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

db:drop should not fail if the database does not exist #599

Open
jjulian opened this issue Dec 19, 2017 · 3 comments
Open

db:drop should not fail if the database does not exist #599

jjulian opened this issue Dec 19, 2017 · 3 comments
Labels
bug dependency

Comments

@jjulian
Copy link
Contributor

jjulian commented Dec 19, 2017

What you are doing?

$ sequelize db:drop

What do you expect to happen?

When the database does not exist, I expect the command to exit with status code 0

What is actually happening?

The command fails with exit code 1

Dialect: postgres
Sequelize CLI version: 3
@Telokis Telokis mentioned this issue May 7, 2018
Closed
codetriage-readme-bot pushed a commit to codetriage-readme-bot/cli that referenced this issue Jun 5, 2019
Merge pull request sequelize#599 from exercism/invalid-validate
ddb18c7 
Fix token validation logic
@mahnunchik
Copy link

+1

@stale
Copy link

stale bot commented Jun 21, 2020

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.

@stale stale bot added stale and removed stale labels Jun 21, 2020
@mahnunchik
Copy link

It should not be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug dependency
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jjulian @mahnunchik @sushantdhiman