Key changes in 3.0.0

Main goal of this release was to accommodate the Npgsql 4.* dependency.

Besides the usage of Npgsql 4, our biggest change was making the default schema object creation mode to CreateOrUpdate. Meaning that Marten even in its default mode will not drop any existing tables, even in development mode. You can still opt into the full "sure, I’ll blow away a table and start over if it’s incompatible" mode, but we felt like this option was safer after a few user problems were reported with the previous rules. See Schema Migrations and Patches for more information.

We also aligned usage of EnumStorage. Previously, Enum Duplicated Field was always stored as varchar. Now it's using setting from JsonSerializer options - so by default it's integer. We felt that it's not consistent to have different default setting for Enums stored in json and in duplicated fields.

See full list of the fixed issues on GitHub.

You can also read more in Jeremy's blog post from.

Migration from 2.*

• To keep Marten fully rebuilding your schema (so to allow Marten drop tables) set store options to:

AutoCreateSchemaObjects = AutoCreate.All

• To keep Duplicated Enum Fields being stored as varchar set store options to:

DuplicatedFieldEnumStorage = EnumStorage.AsString;

• To keep Duplicated DateTime Fields being stored as timestamp with time zone set store options to:

DuplicatedFieldUseTimestampWithoutTimeZoneForDateTime = false;