Skip to content

Commit

Permalink
Add release note on timestamptz scaffolding change
Browse files Browse the repository at this point in the history
2.1 scaffolds to DateTime and not to DateTimeOffset as before.
  • Loading branch information
roji committed Jul 14, 2018
1 parent 76da2f3 commit 343e80d
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions doc/release-notes/2.1.md
Original file line number Diff line number Diff line change
Expand Up @@ -75,6 +75,7 @@ Here's the [full list of issues](https://github.com/npgsql/Npgsql.EntityFramewor
> [!CAUTION]
> The provider's classes have been moved from the namespace `Microsoft.EntityFrameworkCore` to `Npgsql.EntityFrameworkCore.PostgreSQL`. As a result, any migrations already generated in your project (as well as the mode snapshot) will have to be manually updated to use the new namespace. You will need to add `using Npgsql.EntityFrameworkCore.PostgreSQL.Metadata` to all the relevant files.
* Columns of type `timestamp with time zone` will now be scaffolded as `DateTime` properties, and nt `DateTimeOffset` properties. The general use of `timestamp with time zone` is discouraged (this type does *not* store the timezone in the database), consider using regular `timestamp` instead.
* If you're specifying index methods with `ForNpgsqlHasMethod()`, then you will have to fix migrations which generate those indices. In these migrations, you will find code such as `.Annotation("Npgsql:Npgsql:IndexMethod", "gin")`. You must remove the extra `Npgsql:`, leaving `.Annotation("Npgsql:IndexMethod", "gin")`.
* Specifying versions when specifying PostgreSQL extensions on your model is no longer supported - this was a very rarely-used feature which interfered with extension scaffolding.
* If you're still referencing the nuget package Npgsql.EntityFrameworkCore.PostgreSQL.Design, please remove it - it's no longer needed or up to date.

0 comments on commit 343e80d

Please sign in to comment.