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.
NpgsqlSnakeCaseNameTranslator breaking change
See original GitHub issueSteps to reproduce
In version 4.0.9, the NpgsqlSnakeCaseNameTranslator.TranslateMemberName method would translate the name En13757Index as en13757_index, as one would expect.
In version 4.1.1, the result is en13757index. This leads to column not found in the queries.
This breaking change is not listed in the release notes.
Should this change be reverted before I upgrade to the newer version, or should I change my database schema to use the new (wrong?) column name?
Further technical details
Npgsql version: 4.1.1 PostgreSQL version: 12 Operating system: Windows 10
Using Entity Framework Core 2, but this class is probably not related to EF. If it is, please move this issue to the EF repo.
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (9 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
@ygoe thanks for your understanding - the name translator API is indeed meant for you to create your own implementations as you see fit. The version of NpgsqlSnakeCaseNameTranslator which was used in 4.0.10 is here.
Okay, that makes this feature unusable for me. Fortunately I can just replace it. I’ll have to copy out the old code into my application to get reasonable results. While I’m searching it, does somebody have a link to it at hand?