Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support ForNpgsqlUseIdentityAlwaysColumns with HasData
See original GitHub issueCurrently Entity Framework Core’s data seeding feature HasData does not support ForNpgsqlUseIdentityAlwaysColumns, because GENERATED ALWAYS AS IDENTITY does not allow inserting values in the identity column if OVERRIDING SYSTEM VALUE is not specified in the INSERT clause.
This could be supported by adding InsertDataOperation hook to NpgsqlMigrationsSqlGenerator. For inspiration, here’s the SqlServerMigrationsSqlGenerator implementation using SET IDENTITY_INSERT.
See also the earlier discussion.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:17 (12 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Done, seeding now works with IDENTITY ALWAYS. However, you still need to use negative values to avoid conflicts.
@Sigvaard that’s right - seed with negative values to make sure seeded values don’t collide with values later generate from the identity sequence.