From: | Tim Uckun <timuckun(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: "Reverse" inheritance? |
Date: | 2017-04-04 03:19:53 |
Message-ID: | CAGuHJrOjXxe3ASicS-KxmK4KNfiL+1Nd5CrX6_nZjTRvtQxqJA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I have thought of doing something like a single table inheritance and it
could be done but I thought this might be a little more elegant.
On Tue, Apr 4, 2017 at 2:15 PM, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Mon, Apr 3, 2017 at 7:07 PM, Tim Uckun <timuckun(at)gmail(dot)com> wrote:
>
>> I am trying to make postgres tables work like an object hierarchy. As an
>> example I have done this.
>>
>
> I suspect you are barking up the wrong tree ;)
>
> You are probably better off incorporating something like the "ltree" type
> to encode the taxonomy.
>
> https://www.postgresql.org/docs/current/static/ltree.html
>
> I haven't had a chance to leverage it myself but the concept it embodies
> is solid.
>
> David J.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | vinny | 2017-04-04 06:43:10 | Re: "Reverse" inheritance? |
Previous Message | David G. Johnston | 2017-04-04 02:15:46 | Re: "Reverse" inheritance? |