tree 2e83433892f58a8bdde70e0741245789adb18798
parent 33b500b18a25c665782d6794f09fcbc1039d4c14
author Daniel Santiago Rivera <danysantiago@google.com> 1694007438 -0400
committer Daniel Santiago Rivera <danysantiago@google.com> 1699967718 -0500

Add API for dropping all tables during destructive migrations.

The APIs are overloaded versions of the current fallbackToDestructiveMigration APIs with the older ones deprecated in order to have users migrate to the recommended behavior of dropping all tables, done so via the extra param in the overloaded version.

The API and behavior change addresses the issue of an application adding a new table in a version n+1 schema, then rolling back the deployment causing a downgrade but due to the table / entity not existing at version n Room would unknowingly keep the table (its untracked) thus causing a failure when the redeployment of the app at version n+1 is done again along with its migration.

Test: MigrationTest.dropAllTablesDuringDestructiveMigrations
Relnote: "Overload fallbackToDestructiveMigration APIs with a boolean parameter to indicate if all tables, including those not tracked by Room should be dropped during destructive migrations. Usually the value should be 'true' unless the database contains tables not defined via Room entities. The version of the APIs without the parameter are now deprecated and the default behavior of not destroying untracked tables is kept."
Change-Id: Ic8ef384aef7443430a1fc1e461aacaa18065126d