Fix udt recognition #33
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…" and map it to string accordingly
… (and therefore failing with exception)
…s without crashing
…te an empty type instead.
|
To test this pull request, download the https://github.com/henrik-m/linqpad-postgresql-driver/tree/fix-udt-recognition branch and build it locally. You'll need to update the project references to your locally installed LINQPad.exe, then make sure the postbuild step in DynamicLinqPadPostgreSqlDriver.csproj actually copies all output files to %LOCALAPPDATA%\LINQPad\Drivers\DataContext\4.6\DynamicLinqPadPostgreSqlDriver (b79463f4d947ddea). I had to copy a few manually (Dapper, not sure why, maybe forgot to close LinqPAD?). Now you'll be able to add connections. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #18 and fixes #25. You still cannot call functions with UDT arguments from generated LINQPad C# code, but there should be no more exceptions generating the datacontext because of this.
Tested this on the official postgis docker image, where I could reproduce the issues, and extended the relevant test case to ensure it stays fixed.
Bumped the framework version to 4.6 because that was the version I had to use to compile against the latest LINQPad release.