-
Notifications
You must be signed in to change notification settings - Fork 583
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 upgrade/versioning support #10
Comments
We've added support for that recently. This feature is still in beta stage. Here's how you'd do it.
<meta-data android:name="VERSION" android:value="2" />
|
That sounds great! Like Rails migrations. I like it. |
What if I already have a DB? What Sugar will do the first time the app open (after the upgrade)? Will it have some Exceptions because the tables already exists, will it drop all the tables? And if I have scripts, will it just use the scripts or will it try to create the tables? Just some questions =P |
@tsuharesu An upgrade right now just executes the migration scripts. |
Hmm, understood. If I have the scripts, they will be executed. If not, dropTable > createTable. Thanks 👍 |
After upgrading my sugar[using 1.3] record, with alter table query i am adding a column to existing table. |
I have exactly the same problem as rastoarpit. |
I have the same problem as @rastoarpit and @refaelsh |
Need database upgrade/versioning support.
The text was updated successfully, but these errors were encountered: