Skip to content
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

Open
roji opened this issue May 12, 2016 · 5 comments
Open

Map geometry/geography for EF6 #18

roji opened this issue May 12, 2016 · 5 comments

Comments

@roji
Copy link
Member

roji commented May 12, 2016

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

@roji
Copy link
Member Author

roji commented May 12, 2016

From @refactorman on July 8, 2015 5:39

Hi,
What's your plan about this feature? Me and my company uses npgsql for very long time with EF6. We have PostGis data types in our schema, and we do patches to make it work with EF...
Oh, and thanks for your great work!

@roji
Copy link
Member Author

roji commented May 12, 2016

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 :)

@pmeems
Copy link

pmeems commented Mar 30, 2017

Is there any progress on this?
We're moving our code from NHibernate+PostGIS to EF6+PostGIS and we can define the DbGeometry type in code, doing code first doesn't work because of the 'Not supported edm type: Edm.Geometry' error.

We at least would like to know if using Npgsql is still the best option or if we should move to another provider.

@atakansavas
Copy link

atakansavas commented Nov 13, 2017

Is there any progress on this? Im still waiting.

@roji
Copy link
Member Author

roji commented Nov 13, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants