-
Notifications
You must be signed in to change notification settings - Fork 111
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
Database schema does not match ixmp schema #455
Comments
@khaeru I added you here, I hope it's fine. I suggest if it's not possible to update the schema of local DB when upgrading to a newer version of |
It could also be the opposite. As far as I understand, the Java code under the JDBCBackend has a way of migrating from one version of the database schema to a newer version, but not the reverse. So if a user uses an old version of ixmp to connect to a database that has already been migrated, it cannot ‘rewind’ the schema of that database. This could occur:
Some other wrinkles:
This would be difficult to create tests for; however I could add some code that tries to catch particular Java exceptions and re-raise them. However, I can only do this if I have a complete error traceback with the precise message and the code that raises it. Could you get this from the user in question? |
@behnam-zakeri - the problen happens with a local database? |
Thanks @khaeru and @peterkolp. This experience was from a local database, and after updating to a higher version of |
One of the users has reported that they receive the following error message when loading the modelling platform from ixmp "schema of the database does not match the schema of this version of ixmp". Does it mean that after updating to a newer version of message_ix (and ixmp) the databases created by previous versions are obsolete? Is there any approach to resolve this?
The text was updated successfully, but these errors were encountered: