-
Notifications
You must be signed in to change notification settings - Fork 860
Add support for postgresql type names with dots #5971
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.
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
Conversation
Thanks, mind adding a few test cases? Contributes to #5710 |
Contributes to #5972 |
Added test case with schema_name."Test.type.name" |
I need this fix in Npgsql v8, is it possible? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Yeah, we'll probably backport it to npgsql 8. BTW could you try to rebase on the latest main? It looks like there is an issue with the CI pipeline. |
Huh, for some reason it shows much more changes than it should... |
5b4ebb7
to
d2e7534
Compare
For composite type with dots in name, Postgresql returns name with quotes - scheme."My.type.name", but for npgsql mapping we should use names without quotes - scheme.My.type.name
d2e7534
to
d7159a0
Compare
Fixed, but unfortunately a few more reviewers were added because of this error |
OK, I think it's fine to merge this now. |
Fixed the problem of converting type names with dots, for example the name "public.audit.sessiontype" was parsed incorrectly and had namespace after parse "audit" and name - "sessiontype".
If the schema is not null or empty, then displayname must contain only the type name.