-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Microsoft.EntityFrameworkCore.Sqlite.NetTopologySuite error during migration #25116
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
not sure why you guys are punting this issue, it seems to me like a pretty critical one. Are there any decent workarounds? |
Hmm, it looks like we're just forgetting to set the table here: efcore/src/EFCore.Sqlite.Core/Migrations/SqliteMigrationsSqlGenerator.cs Lines 313 to 327 in c146f7a
If you want to add |
thanks @bricelam, i only have visual studio 2019. So can i clone from a v5.017 tag and put tests in there? In other words, would you be able to work the fixes into a v5.018 release or is v15 dead at this point? |
EF Core 5.0 is out of support. We won't be releasing any more patches for it. |
@bricelam I created a fork and pushed your suggested fix along with a unit test here: https://github.com/d79ima/efcore_issue25116 |
@d79ima Looks great! |
…gySuite error during migration (#28476) * fix for create temp table bug for spatial column (was missing TableName) * build fix, forgot to add namespace using Co-authored-by: Dmitry Grinblat <dmitry.grinblat@inovageo.com>
File a bug
Using Microsoft.EntityFrameworkCore.Sqlite.NetTopologySuite provider, "dotnet ef database update" command throws exception with message "SQLite Error 1: 'table ef_temp_SomeBuildings has no column named Location' when mapping of class that contains spatial type changed.
Steps to reproduce
Include verbose output
Include provider and version information
Database provider: "Microsoft.EntityFrameworkCore.Sqlite.NetTopologySuite" Version="5.0.5"
Target framework: .NET 5.0
Operating system: Windows 10
IDE: Jetbrains Rider
The text was updated successfully, but these errors were encountered: