Ah makes sense. Ok. If all primitive types are supported, either adding an option to the existing pg_json extension or creating a new extension sounds good to me!
Thanks much for your help. If there is anything I can do to help to get this out, please let me know. Alex On Tuesday, April 30, 2019 at 10:16:11 AM UTC-4, Jeremy Evans wrote: > > On Tuesday, April 30, 2019 at 7:01:05 AM UTC-7, [email protected] > <javascript:> wrote: >> >> I agree with you that it seems odd to support some JSON primitives and >> not others. >> >> Are you suggesting a config option that would support all JSON primitive >> types? Or just int, string, and true? >> >> If all primitive types are supported, I like this option! Otherwise, >> having to remember which types are supported vs. not supported is an added >> layer of complexity that I would rather not think about. >> > > This would support all primitive types. It may be an option to the > existing pg_json extension, or I may add another extension > (pg_json_primitives) for it if that is possible. > > >> Can you give a more detailed example of why wrapping null and false would >> be a breaking change? Thanks for your help! >> > > if row[:json_column] > # currently not called if JSON null/false, would be called if you wrap > end > > Thanks, > Jeremy > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
