Database upgrade/versioning support about sugar HOT 8 CLOSED

We've added support for that recently. This feature is still in beta stage.

Here's how you'd do it.

1. Create a folder named "sugar_upgrades" in your assets folder.
2. Create a file named <db_version>.sql in that folder. eg. 1.sql, 2.sql
3. This file would contain all the update/alter queries for that particular version.
4. Change the version field in AndroidManifest.xml

<meta-data android:name="VERSION" android:value="2" />

1. This would execute all the .sql files that have changed from your current version.

from sugar.

That sounds great! Like Rails migrations. I like it.

from sugar.

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

from sugar.

@tsuharesu An upgrade right now just executes the migration scripts.
http://satyan.github.io/sugar/migration.html

from sugar.

Hmm, understood. If I have the scripts, they will be executed. If not, dropTable > createTable.
https://github.com/satyan/sugar/blob/master/library/src/com/orm/SugarDb.java#L137

Thanks 👍

from sugar.

After upgrading my sugar[using 1.3] record, with alter table query i am adding a column to existing table.
Column is there but when i add a value and save it then it does not work rather it takes a null/default value even after the upgrade. While everything works great on fresh install where table gets created with this column already.

from sugar.

I have exactly the same problem as rastoarpit.

from sugar.

I have the same problem as @rastoarpit and @refaelsh
Even in the log it appears the alter table
I/Sugar: ALTER TABLE ROSCA ADD COLUMN PHOTO TEXT
However debugging the new column not appears

from sugar.