brick_sqlite_abstract 1.0.0

brick_sqlite_abstract: ^1.0.0 copied to clipboard

• Null safety

• Declare a custom columnType with @Sqlite. Because this feature overrides Brick assumptions about the column type, the field will be inserted (toSqlite) as is and returned as is from deserialization (fromSqlite).
• BREAKING CHANGE Positional argument typeis no longer accepted when initializing SchemaColumn. The type was converted to a SQLite column type and rendered as the SQLite type in generators. Instead, explicitly define the columnType to use, such as Column.integer. For existing implementations, SchemaColumn should only be declared in generated schema.g.dart files. If the schema has not been committed to VCS (as recommended), no update steps will be necessary. Migrations remain unaffected.

• Escape tables created with reserved names in the index statement. For example: CREATE INDEX IF NOT EXISTS index_Group_on_id \Group`(`id`)`

• Remove Migration.wrapInTransaction static method. This was a misleading and unused method.
• Add index: option in @Sqlite for creating an index on a column.

• Add a DropIndex command to revert CreateIndex changes
• Detect CreateIndex changes and generate a migration

• When joins tables are created, add a unique index by both columns to ensure no duplicates are inserted. Prior applications will need to manually specify CreateIndex in a custom migration for existing joins tables. When new joins tables are generated in migrations, CreateIndex will also be generated.

• Fix a bug where a many-to-many association shared the same class name

0.0.7+2, 0.0.7+3 #

• Define onDeleteSetDefault on the field annotation. This 1) generates a new migration and 2) allows the schema to regenerate from user preferences instead of strictly historic migrations.

• Define onDeleteCascade on the field annotation. This 1) generates a new migration and 2) allows the schema to regenerate from user preferences instead of strictly historic migrations.

• When defining the migration for InsertForeignKey, onDeleteCascade can be set to determine whether the deletion of the record will delete all referencing children records. Defaults false.

• Sqlite#defaultValue updated to reflect FieldSerializable#defaultValue change

• Use single quotes when generating Migration#version to comply with default analyzer options
• Fix linter hints

• SqliteModel moved to this package from brick_offline_first_abstract