Re: json accessors - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: json accessors
Date
Msg-id FDA23402-7386-4B70-9D16-2707482A5A12@justatheory.com
Whole thread Raw
In response to Re: json accessors  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: json accessors
Re: json accessors
List pgsql-hackers
On Dec 5, 2012, at 9:57 AM, Merlin Moncure <mmoncure@gmail.com> wrote:

> Indexing large documents for fancy querying is a niche case but also
> quite complex.  This isn't very well covered by xmlpath either btw --
> I think for inspiration we should be looking at hstore.

Agreed, although hstore, IIRC, does not support nesting.

> That said, how would you do that?  The first thing that jumps into my
> mind is to cut right to the chase:  Maybe the semantics could be
> defined so that implement hackstack @> needle would reasonable cover
> most cases.

Yes.

> So my takeaways are:
> *) decomposition != precise searching.  andrew's api handles the
> former and stands on it's own merits.

Agreed.

> *) xmlpath/jsonpath do searching (and decomposition) but are very
> clunky from sql perspective and probably absolutely nogo in terms if
> GIST/GIN.  postgres spiritually wants to do things via operators and
> we should (if possible) at least consider that first

I don't understand how xmlpath/jsonpath is not able to be implemented with operators.

Best,

David




pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: ALTER TABLE ... NOREWRITE option
Next
From: Robert Haas
Date:
Subject: Re: Dumping an Extension's Script