From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Guyren Howe <guyren(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: First-class Polymorphic joins? |
Date: | 2015-08-14 01:04:37 |
Message-ID: | 55CD3EA5.8090309@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 08/13/2015 05:59 PM, Guyren Howe wrote:
Ccing list
> On Aug 13, 2015, at 17:49 , Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>>
>>> A polymorphic join is where a fk contains not just an id but an indicator of which table it refers to.
>>
>> I am pretty sure it already does that:
>>
>> http://www.postgresql.org/docs/9.4/interactive/sql-createtable.html
>>
>> REFERENCES reftable [ ( refcolumn ) ]
>
> I apologize for not being clearer.
>
> The point is that the fk in different rows can reference different tables. I might want to be able to attach a tag to a person or a blog post, say. And then I want to find all the persons and blog posts with a particular tag, in a single query.
Could you just not turn that around?:
tag
tag_id
tag_desc
person
person_id
tag_fk references tag
blog
blog_id
tag_fk references tag
>
> The simplest implementation is to have a table reference as a first-class value I can store in a field.
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2015-08-14 02:17:08 | Re: Migrations |
Previous Message | Adrian Klaver | 2015-08-14 00:58:29 | Re: Foreign Keys as first class citizens at design time? |