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.

Sign up for GitHub

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

Jump to bottom

DbContext Scaffolding of geography type columns fail #3014

Closed
apDyn opened this issue Sep 4, 2015 · 6 comments
Closed

DbContext Scaffolding of geography type columns fail #3014

apDyn opened this issue Sep 4, 2015 · 6 comments
Labels
closed-no-further-action The issue is closed and no further action is planned. customer-reported

Comments

@apDyn
Copy link

apDyn commented Sep 4, 2015

Executing dnx ef dbcontext scaffold EntityFramework.SqlServer
For column [country][coordinates]. Could not find type mapping for SQL Server type geography. Skipping column.
@ErikEJ
Copy link
Contributor

ErikEJ commented Sep 4, 2015

That is by design, there is currently no support for geography columns. It is in the backlog: #1100

@apDyn
Copy link
Author

apDyn commented Sep 4, 2015

Do you have any recommended workarounds?

@ErikEJ
Copy link
Contributor

ErikEJ commented Sep 4, 2015

If you are running on full .NET 4.5/4.6, use EF 6.x!

@rowanmiller
Copy link
Contributor

BTW we may be able to introduce an interim workaround until we have proper spatial support #3076

@tsasioglu
Copy link

For anyone that ends up here from google, this is now supported via adding the nuget package Microsoft.EntityFrameworkCore.SqlServer.NetTopologySuite. Details at https://docs.microsoft.com/en-us/ef/core/modeling/spatial

@Freysi21
Copy link

Freysi21 commented Nov 27, 2020 •
edited
Loading

Not the hero we deserve but the hero we need

@ajcvickers ajcvickers added customer-reported closed-no-further-action The issue is closed and no further action is planned. labels Nov 16, 2021
@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
closed-no-further-action The issue is closed and no further action is planned. customer-reported
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@ajcvickers @ErikEJ @rowanmiller @Freysi21 @tsasioglu @apDyn