You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/release-notes/2.2.md
-4Lines changed: 0 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,10 +39,6 @@ This will make the provider create a PostgreSQL range called `floatrange`, over
39
39
40
40
[See the documentation for more details](../mapping/range.md).
41
41
42
-
### Type-constrained PostGIS columns
43
-
44
-
The NetTopologySuite previously created PostGIS columns of type `GEOMETRY` (or `GEOGRAPHY`) in the database. With [#719](https://github.com/npgsql/Npgsql.EntityFrameworkCore.PostgreSQL/issues/719), a property of type `Point` will be instead mapped to columns of type `GEOMETRY (POINT)`.
45
-
46
42
### Seeding for Npgsql-specific types
47
43
48
44
When using some Npgsql-specific types, it wasn't possible to seed values for those types. With EF Core support for seeding any type, [#667](https://github.com/npgsql/Npgsql.EntityFrameworkCore.PostgreSQL/issues/667) allows seeding values for network, bit and range types (more are coming).
0 commit comments