Re: Harmonization of json functions (SQLITE)

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Tobias Schönit <tobias(dot)schoenit(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Harmonization of json functions (SQLITE)
Date: 2017-02-03 10:52:07
Message-ID: CAFj8pRB+zb9tNw9xO1h53rS9po2VV1QA2+-0AzC88K5q9Jdk-w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

2017-02-03 8:52 GMT+01:00 Tobias Schönit <tobias(dot)schoenit(at)gmail(dot)com>:

> Hello,
>
>
>
> I just saw on hackernews the announcement that sqlite includes a json
> extension.
>
> The proposed functions are really well documented and easy to apply and I
> was wondering if postgres could extend their json functions to be similar
> to those.
>
>
>
> https://www.sqlite.org/json1.html
>
>
>
> Some functions are similar (json_each) while others are missing in
> postgresql (json_set)
>
>
>
> Maybe it would also be a viable path to create a plugin and reuse some oft
> he code from the sqlite community?
>

I am not sure, if PostgreSQL upstream code can reuse SQLite code.

What I know the PostgreSQL target is SQL/JSON syntax - but SQLite
compatible JSON can be nice extension (maybe some more bigger - SQLitefce -
like Orafce)

Some work can be shared - SQLite has uses JSONPath that is required by
SQL/JSON

Regards

Pavel

>
> Regards,
>
> Tobias
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Erik Rijkers 2017-02-03 11:00:49 Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless)
Previous Message Pavel Stehule 2017-02-03 10:36:42 Re: proposal: session server side variables