SQLiteAutoVacuumMode

Entries


NONE	[jvm] NONE Auto-vacuum is disabled. When auto-vacuum is disabled and data is deleted data from a database, the database file remains the same size. Unused database file pages are added to a "freelist" and reused for subsequent inserts. So no database file space is lost. However, the database file does not shrink. In this mode vacuum can be used to rebuild the entire database file and thus reclaim unused disk space.
FULL	[jvm] FULL The freelist pages are moved to the end of the database file and the database file is truncated to remove the freelist pages at every transaction commit. Note, however, that auto-vacuum only truncates the freelist pages from the file. Auto-vacuum does not defragment the database nor repack individual database pages the way that vacuum does. In fact, because it moves pages around within the file, auto-vacuum can actually make fragmentation worse.
INCREMENTAL	[jvm] INCREMENTAL The additional information needed to do auto-vacuuming is stored in the database file but auto-vacuuming does not occur automatically at each commit as it does with "full". In incremental mode, the separate incremental vacuum pragma must be invoked to cause the auto-vacuum to occur.

Name	Summary
entries	[jvm] val entries: EnumEntries<SQLiteAutoVacuumMode> Returns a representation of an immutable list of all enum entries, in the order they're declared.
name	[jvm] val name: String
ordinal	[jvm] val ordinal: Int

Name	Summary
invoke	[jvm] operator fun invoke(): Int
valueOf	[jvm] fun valueOf(value: String): SQLiteAutoVacuumMode Returns the enum constant of this type with the specified name. The string must match exactly an identifier used to declare an enum constant in this type. (Extraneous whitespace characters are not permitted.)
values	[jvm] fun values(): Array<SQLiteAutoVacuumMode> Returns an array containing the constants of this enum type, in the order they're declared.