Skip to content
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

Support custom json decoder and encoder when dealing with JSON/JSONB columns #126

Closed
jordanebelanger opened this issue Sep 4, 2020 · 0 comments · Fixed by #127
Closed

Comments

@jordanebelanger
Copy link
Contributor

At the moment, every-time a Postgres json value is decoded, a new Foundation.JSONDecoder is created on the spot for the decoding. The same thing is done for encoding json columns.

For performance (notably on Linux) and floating point encoding accuracy reasons, we should be able to use custom, i.e non-Foundation, json encoders and decoders when dealing with json and jsonb columns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant