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

Feature request: Allow Retriever to work without the CREATE permission if the database already exists #37

Closed
ethanwhite opened this issue Apr 25, 2012 · 1 comment

Comments

@ethanwhite
Copy link
Member

Via email I've received a request to support a situation where the database already exists, but the user does not have the permission to CREATE new databases. This is definitely an edge use case, but one that clearly can come up with shared resources.

A quick look at engine.py suggests that we can probably accomplish this fairly easily by adding a try-catch in create_db. The trick will be failing gracefully in the case where the user doesn't have permission to create and the database doesn't already exist.

@bendmorris
Copy link
Member

Trying to continue anyway after a CREATE fails is a good default; it certainly shouldn't hurt anything. I've made the change.

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

No branches or pull requests

2 participants