如何在Android Room Persistence Library中创建不迁移版本的表?

时间:2018-07-10 06:25:04

标签: android sqlite android-sqlite android-room

仅创建表而不更改其他表和数据时,是否需要迁移数据库?

由于google tutorial和谷歌搜索,其中大多数表示我们必须迁移数据库,如果每次升级都创建表,则必须增加数据库版本和迁移,这非常令人困惑

1 个答案:

答案 0 :(得分:2)

是的。 Room在开始时就比较数据库架构,如果架构不同,它将运行迁移。如果架构不同,并且不会添加迁移,则可能会抛出IllegalStateException。

此外,当您更改数据库版本并且对架构没有任何更改时,应将Migration对象添加到构建器。如果没有,Room将清除您的数据库并重新创建它们。您可以在RoomDatabase.java类的文档中阅读更多内容:

  /**
         * Adds a migration to the builder.
         * <p>
         * Each Migration has a start and end versions and Room runs these migrations to bring the
         * database to the latest version.
         * <p>
         * If a migration item is missing between current version and the latest version, Room
         * will clear the database and recreate so even if you have no changes between 2 versions,
         * you should still provide a Migration object to the builder.
         * <p>
         * A migration can handle more than 1 version (e.g. if you have a faster path to choose when
         * going version 3 to 5 without going to version 4). If Room opens a database at version
         * 3 and latest version is &gt;= 5, Room will use the migration object that can migrate from
         * 3 to 5 instead of 3 to 4 and 4 to 5.
         *
         * @param migrations The migration object that can modify the database and to the necessary
         *                   changes.
         * @return this
         */
        @NonNull
        public Builder<T> addMigrations(Migration... migrations) {
            mMigrationContainer.addMigrations(migrations);
            return this;
        }

 /**
         * Allows Room to destructively recreate database tables if {@link Migration}s that would
         * migrate old database schemas to the latest schema version are not found.
         * <p>
         * When the database version on the device does not match the latest schema version, Room
         * runs necessary {@link Migration}s on the database.
         * <p>
         * If it cannot find the set of {@link Migration}s that will bring the database to the
         * current version, it will throw an {@link IllegalStateException}.
         * <p>
         * You can call this method to change this behavior to re-create the database instead of
         * crashing.
         * <p>
         * Note that this will delete all of the data in the database tables managed by Room.
         *
         * @return this
         */
        @NonNull
        public Builder<T> fallbackToDestructiveMigration() {
            mRequireMigration = false;
            return this;
        }