tree 71cd229d94b181637fab2e69b5a01c5d2d6c4643
parent 667076446b86cf50e832a86a7503ea325a14e5b4
author Elif Bilgin <elifbilgin@google.com> 1617726273 -0700
committer Elif Bilgin <elifbilgin@google.com> 1618351555 -0700

Implementing support for handling all schema changes including FTS Table related ones.

This change handles detecting all schema changes involving FTS tables in order to generate an auto migration. During code generation, it is important to note that the normal (non-fts) tables that have complex schema changes are processed before FTS table related changes are processed. This is to handle the case where content tables FTS tables reference may have schema changes such as table renames.

Test: Tests have been added to verify different FTS table related changes are assessed correctly. In addition, a test has been added in AutoMigrationTest.kt to verify that a user defined Migration is chosen over an auto migration, when both are present (the user has defined an auto migration manually as well as added an @AutoMigration annotation in the Database with the same "from" and "to" versions).
Bug: 180395129, 181777611
Change-Id: I250d695becdaaa6240b011c2dc03ec31eaceed17