-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create PostGIS columns with the proper type constraints #719
Labels
Comments
roji
added
enhancement
New feature or request
and removed
bug
Something isn't working
labels
Nov 23, 2018
roji
added a commit
to roji/efcore.pg
that referenced
this issue
Nov 24, 2018
We previously generated PostgreSQL GEOMETRY (or GEOGRAPHY) columns, not taking into account the CLR type. We now include that as a constraint on the column. Note that SRID support still needs to be done (npgsql#717). Fixes npgsql#719
roji
added a commit
to roji/efcore.pg
that referenced
this issue
Nov 30, 2018
We previously generated PostgreSQL GEOMETRY (or GEOGRAPHY) columns, not taking into account the CLR type. We now include that as a constraint on the column. Note that SRID support still needs to be done (npgsql#717). Fixes npgsql#719
roji
added a commit
that referenced
this issue
Nov 30, 2018
Closed
roji
added a commit
to roji/efcore.pg
that referenced
this issue
Dec 7, 2018
roji
added a commit
that referenced
this issue
Dec 7, 2018
Reverted via #738. |
roji
added a commit
to roji/efcore.pg
that referenced
this issue
Dec 12, 2018
roji
added a commit
that referenced
this issue
Dec 13, 2018
Add docs on constraining spatial columns See #719
roji
added a commit
that referenced
this issue
Dec 13, 2018
roji
added a commit
that referenced
this issue
Dec 13, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently generate PostGIS columns with type
GEOMETRY
andGEOGRAPHY
, when we should be looking at the NTS CLR type (Point
,LineString
) and generating columns such asGEOMETRY (POINT)
.See #717 for a similar request to constrain the SRID in the generated column.
Note: we need to think about what this implies in terms of backwards compatibility with 2.1.
Originally raised in #718
The text was updated successfully, but these errors were encountered: