migrate to newer db

[indraAnisa]

i try to update my db file with new data, and update database version to 3. but the data is still from the old db. how to achieve this?

[humazed]

You only need to update the version. I will try to make a migration to make sure it's not a library bug.

…

On Mon, Aug 13, 2018, 8:31 AM Indra Anisa ***@***.***> wrote: i try to update my db file with new data, and update database version to 3. but the data is still from the old db. how to achieve this? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#13>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIbcJrJzeBlzjtvAPu7UmYO-ISFoZ76pks5uQR04gaJpZM4V58-V> .

[four01]

I have a similar issue.
I update the DB data upon every release, but would rather not change the version number unless the schema has changed. Previously I was using android-sqlite-asset-helper, which allowed the db to be overwritten upon every app upgrade. Does such a feature exist?

[humazed]

The lib uses android-sqlite-asset-helper under the hood I will look at supporting this.

I find the problem and I will release a new version with a fix.

[kusan-reveur]

Any news about this? It's quite important to be able to update the database.

I tried with fallbackToDestructiveMigrationFrom and it only deleted the old database without getting the new database.

[humazed]

I had no free time lately but I will start working on it actively soon -1 or 2 days- and hopefully fix this bug.

[alierdogan7]

My guess is that when you migrate with fallbackToDestructiveMigrationFrom, it doesn't really delete the db file. It only drops and regenerates all the tables and it prevents RoomAsset from loading the new db file from assets folder.

Any news about this? It's quite important to be able to update the database.

I tried with fallbackToDestructiveMigrationFrom and it only deleted the old database without getting the new database.

[indraAnisa]

i just manually delete data on table and read and loop sql file on migration.

[kusan-reveur]

@indraAnisa You're doing that manually? Make the use of the library useless then, no?

@humazed I don't know much about sqlite, but maybe this option can work:
https://github.com/jgilfelt/android-sqlite-asset-helper#upgrades-via-overwrite

[indraAnisa]

@indraAnisa You're doing that manually? Make the use of the library useless then, no?

yes, the performance is not bad though, about 1 second for 8K row sql insert.

[soundeos]

I had no free time lately but I will start working on it actively soon -1 or 2 days- and hopefully fix this bug.

I'm waiting for this fix too. Will you be working on this issue soon?

[humazed]

unfortunately, I have no free time lately to fix this issue
but PRs are welcomed.

[KulwinderSinghRahal]

I'm still facing this issue, do you have any solution for this ?

[getsadzeg]

Any news about this? It's quite important to be able to update the database.

"Quite important" is quite an understatement..