From: | Ondrej Ivanič <ondrej(dot)ivanic(at)gmail(dot)com> |
---|---|
To: | Chris Travers <chris(dot)travers(at)gmail(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: How hard would a "path" operator be to implement in PostgreSQL |
Date: | 2012-08-20 02:25:28 |
Message-ID: | CAM6mieKXLVx0oF=YaSiyb_B5jMhfTvLqnzv3auKA-eBd6SUoAg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
On 20 August 2012 11:28, Chris Travers <chris(dot)travers(at)gmail(dot)com> wrote:
> I have been reading up on object-relational features of Oracle and DB2 and
> found that one of the big things they have that we don't is a path operator.
> The idea is that you can use the path operator to follow some subset of
> foreign keys called refs.
<snip>
> Any thoughts? If it can be done in plain SQL and inlined that would be
> ideal but in the prototyping state, that isn't so important and I expect
> that it is not.
You should look at ltree:
This module implements a data type ltree for representing labels of
data stored in a hierarchical tree-like structure. Extensive
facilities for searching through label trees are provided.
http://www.postgresql.org/docs/9.1/static/ltree.html
--
Ondrej Ivanic
(ondrej(dot)ivanic(at)gmail(dot)com)
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2012-08-20 03:01:22 | citext: citext=text is case sensitive |
Previous Message | Chris Travers | 2012-08-20 01:28:57 | How hard would a "path" operator be to implement in PostgreSQL |