IssueTracker

Component used: KAPT
Version used: 2.6.1
Devices/Android versions reproduced on: All


I have multiple tables where I must add a new `appId` column.
This new `appId` is part of my foreign key constraints.

The problem is that Room applies the table migration alphabetically but then checks for the foreign key constraints after each table migration.
Therefore, my foreign key is not OK since the old table doesn't have the new column yet.

Example:
Table_A: id, name, tableB_id
Table_B: id, name
Room will add the "appId" to Table_A and set the foreign key constraint to be on the columns `tableB_id` and `appId`, then execute:
DBUtil.foreignKeyCheck(db, "Table_A");

Yet, at that point, Table_B is still: id, name — and not: id, name, appId.