Skip to content

All versions since 3.0.1

3.0.1

Fixed

  • apply now works against SQLite. UseSqliteSchema(...) registers a DbDataSource (alongside the existing introspection source) so the core’s SQL executor can open connections to run the migration.

Security

  • Pin the bundled native SQLite library (SQLitePCLRaw.lib.e_sqlite3) forward to the patched 3.50.3, resolving advisory GHSA-2m69-gcr7-jv3q. This replaces the prior NuGetAudit suppression with an actual fix.

3.1.0

Changed

  • Updated Microsoft.Data.Sqlite from 10.0.3 to 10.0.9.
  • Breaking: The casing has been changed from SQLite to Sqlite to line up with the official Microsoft packages. This applies across all namespaces, but the NuGet package will probably be stuck with the old casing.

3.2.0

Added

  • Trigger Support. SQLite triggers run an inline BEGIN … END body, which the provider now supports, using the inline trigger Body added in NSchema.Core 3.2.0. A trigger is generated as CREATE TRIGGER … {BEFORE|AFTER} {event} ON t [FOR EACH ROW] [WHEN (…)] BEGIN … END and recovered from sqlite_master.

Changed

  • Bumped the NSchema.Core dependency to 3.2.0.

3.2.1

Fixed

  • The provider will now no-longer attempt to CREATE/DROP the main schema.

4.0.0

Added

  • Added plugin manifest to allow for automatic registration of the provider coming in `NSchema 4.0.0.

4.3.0 Latest

Added

  • Data migrations. Supports the MIGRATION … FOR data migrations introduced in NSchema.Core 4.3.