2.0 provider compatibility: HistoryRepository generates INSERT statements without quotes
See original GitHub issue(This was reported via email)
Creating an issue although there is a version mismatch because this could be a symptom that other 2.0 providers that update less often than Npgsql could be broken as well:
Microsoft.EntityFrameworkCore.PostgreSQL version is 2.0.1 Microsoft.EntityFrameworkCore version is 2.1.0-preview2
The INSERT statement into the __EFMigrationsHistory is missing single quotes for the VALUES listed:
Expected (working SQL from 2.0.2):
INSERT INTO "_EFMigrationsHistory" ("MigrationId", "ProductVersion") VALUES ('20180413232313Init2', '2.0.2-rtm-10011')
Actual (quotes missing, invalid SQL):
INSERT INTO "__EFMigrationsHistory" ("MigrationId", "ProductVersion") VALUES (20180413233035_Init3, 2.1.0-preview2-30571) <
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to remove the quotes from a string for SQL query in ...
from psycopg2.extensions import AsIs cur.execute("INSERT INTO %s VALUES(...);", AsIs(database_name)).
Read more >SET QUOTED_IDENTIFIER (Transact-SQL) - SQL Server
SET QUOTED_IDENTIFIER has no effect when it appears in the body of a stored procedure as static Transact-SQL.
Read more >Overview of the SQL Insert statement
This article explores SQL Insert statements including examples such as add multiple rows of data with and without default values, ...
Read more >Untitled
St.bridget school uniform, Insert url latex, Cole haan zerogrand womens sneakers, Ic la76931s 7l, 2684 margaret mitchell drive, Pengwern college cheltenham, ...
Read more >How to use single and double quotes in PostgreSQL - Prisma
Use double quotes sparingly for better compatibility, especially when creating objects. If you want to use double quotes, keep in mind that the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for looking into this and sorry for the bother, it’s a duplicate of https://github.com/npgsql/Npgsql.EntityFrameworkCore.PostgreSQL/issues/283 which has already been fixed for 2.0.2 (not yet released).
FYI released 2.0.2 yesterday so this should be ok now.