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

Database self-check on startup #5

Open

GoogleCodeExporter opened this issue Aug 29, 2015 · 0 comments

Labels

auto-migrated Component-Persistence Priority-Low Type-Enhancement Usability

GoogleCodeExporter commented Aug 29, 2015

It would be nice if the SQLDataStore checked the database to make sure that all 
the tables, views 
etc. are as it expects. This would help prevent bugs and problems being 
perceived due to an 
incorrectly formatted database.

If they are ok, it should accept the data base, if not, then it could either 
give a debug message and 
fail to initialize, or it could delete the database.

Original issue reported on code.google.com by daniel.a...@it.uu.se on 31 Aug 2009 at 7:08

The text was updated successfully, but these errors were encountered:

GoogleCodeExporter added auto-migrated Component-Persistence Priority-Low Type-Enhancement Usability labels

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