Skip to content

pg JSON user types #20

@mwpowellhtx

Description

@mwpowellhtx

Question about the JSON user type. I'm assuming that means the mapping would need to expose a JsonElement property in some way, shape or form, correct?

What about if you wanted to do any custom JSON serialization? i.e. the blanket serialization strategy might not be appropriate for all subjects in that regard. What then? That's first.

Second, it also deals in the new, Microsoft JsonElement vocabulary. Personally, not everybody likes that, I do not. I find, by contrast, the Newtonsoft.Json.Linq is a bit more congenial to work with, especially when pattern matching tokens are JContainer, JArray, JObject, or what have you. It also makes JSON object properties super easy to discover along similar lines. Vis-a-vis pg (F)NH extensions, what then.

I gather that the mapping time customization would probably be more appropiate, I'd expect, rather than the default mapping dialectic, i.e.

Map(...)
    .CustomType<MyCustomNpgsqlJsonUserType>();

Best, and thanks for the insights! 🍻

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions