-
Notifications
You must be signed in to change notification settings - Fork 36
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
Q: autoJSONify #32
Comments
Yes, it's been on our long-term todo for a while. Not sure when people will have tuits for this: it's a non-trivial task. |
@turnstep are you thinking of rolling-your-own serialization/deserialization, or just hooking into |
We need to do our own parsing regardless, in the same way the arrays are done now. Whether or how to involve JSON::XS is somewhat secondary at the moment. |
JSON is probably the most important type for automatic conversion in DBD::Pg, but not the only one. Do the thing I am thinking about is to allow custom conversion for the data types. A user may be given a possibility to specify converters for the data types (like TRANSFORMS in stored procedures). Something like |
That sounds nice in theory, but I'm not sure how that would work in practice. The conversions happen in the Perl XS code, and involve low-level transformations of textual representations of certain types to Perl objects. |
What areas does the complexity reside in? |
Hi!
Let me stupid question. Do you have planned to autoJSONify from Perl data to PG json/jsonb data types and backwards?
Regards.
The text was updated successfully, but these errors were encountered: