On 20/01/16 13:32, Bill Moran wrote:
> On Tue, 19 Jan 2016 23:53:19 -0300
> Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
>
>> Bill Moran wrote:
>>
>>> As far as a current solution: my solution would be to decompose the
>>> JSON into an optimized table. I.e.:
>>>
>>> CREATE TABLE store1 (
>>> id SERIAL PRIMARY KEY,
>>> data JSONB
>>> );
>>>
>>> CREATE TABLE store2 (
>>> id INT NOT NULL REFERENCES store1(id),
>>> top_level_key VARCHAR(1024),
>>> data JSONB,
>>> PRIMARY KEY(top_level_key, id)
>>> );
>> Isn't this what ToroDB already does?
>> https://www.8kdata.com/torodb/
> Looks like. I wasn't aware of ToroDB, thanks for the link.
>
Hi Bill.
Effectively, that's what ToroDB does. You will have a dynamic
schema, but automatically created for you. It will be a relational
schema, no json/jsonb needed for your data.
Please read the FAQ: https://github.com/torodb/torodb/wiki/FAQ and
let us know (https://groups.google.com/forum/#!forum/torodb-dev) if you
would have any additional question.
Thanks, Álvaro, for the reference :)
Cheers,
Álvaro