Npgsql: Use EnableDynamicJson
to unlock better container type mappings
#777
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.
About
This patch resolves a few FIXME admonitions introduced by a recent patch that started to validate all of CrateDB's data types with Npgsql.
Npgsql.CrateDB
instead of vanillaNpgsql
#776Details
Vanilla Npgsql provides good enough support to handle CrateDB's ARRAY and OBJECT types better than just plain strings. This patch demonstrates type mappings using three different variants:
System.Collections.Generic.List
andSystem.Collections.Generic.Dictionary
types.System.Text.Json.JsonDocument
type. 1 Thanks, @simonprickett.What's Inside
NpgsqlDbType.Json
explicitly where applicable, for example when communicating parameters usingAddWithValue()
.EnableDynamicJson()
on theNpgsqlDataSourceBuilder
, for POCO andDictionary
mappings that didn't work before.What's Next
Include relevant information into a dedicated documentation page, in order to educate readers properly in the spirit of "seeing is believing".
Footnotes
Currently works with OBJECT for me, but not ARRAY. ↩