On Tue, Nov 29, 2016 at 05:18:17PM +0100, Petr Jelinek wrote: > Just to add to this, the SQL/JSON proposals I've seen so far, and what > Oracle, MSSQL and Teradata chose to implement already is basically > subset of jsonpath (some proposals/implementations also include > lax/strict prefix keyword on top of that). I think that should give us > some hint on what the base functionality should look like.
Yes, that'd be base functionality. You can go above and beyond. I agree with Pavel that jq could be used as a user-defined function, but proper integration would be better because it would avoid the need to format and parse JSON around calls to jq, and also because PG could compile jq programs when preparing SQL statements. Besides, the libjq jv API is *very* nice. Nico -- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
