-
Notifications
You must be signed in to change notification settings - Fork 51
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
Map geometry/geography for EF6 #18
Comments
From @refactorman on July 8, 2015 5:39 Hi, |
It's definitely something we'd like to see, but unfortunately we're much too busy with other stuff to do it at the moment (Npgsql 3.0.0, Entity Framework 7). Also, before this can implemented, PostGIS support needs to be implemented at the Npgsql ADO.NET level (i.e. outside the EF6 provider), this is issue #529. Note that EF7 seems to allow for totally custom types, which make it ideal for supporting PostGIS and other PostgreSQL-specific types. Basically if anyone is willing to contribute that would be great :) |
Is there any progress on this? We at least would like to know if using Npgsql is still the best option or if we should move to another provider. |
Is there any progress on this? Im still waiting. |
I'm sorry that there hasn't been any progress on this, but Npgsql is an open-source project and my time is limited. As this issue is flagged "up for grabs", it's basically waiting for someone to come along and implement it. |
From @roji on May 25, 2015 15:7
I happened to notice that Entity Framework's
PrimitiveTypeKind
enum has geography/geometry members, this probably means we can use EF to cleanly map PostgreSQL geometry types and/or PostGIS types (which aren't yet implemented: #529).Copied from original issue: npgsql/npgsql#623
The text was updated successfully, but these errors were encountered: