From: | "David Wilson" <david(dot)t(dot)wilson(at)gmail(dot)com> |
---|---|
To: | "Roberts, Jon" <Jon(dot)Roberts(at)asurion(dot)com> |
Cc: | "Mike Blackwell" <maiku41(at)sbcglobal(dot)net>, "Erik Jones" <erik(at)myemma(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Using meta-data for foreign key? |
Date: | 2008-04-17 18:05:28 |
Message-ID: | e7f9235d0804171105r29bfdd30x17755782be5c46a8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Apr 17, 2008 at 1:55 PM, Roberts, Jon <Jon(dot)Roberts(at)asurion(dot)com> wrote:
> Using the term "metadata" is misleading in your example. Metadata is
> data about data and in your example, you just have data. It is fine to
> join tables in an RDBMS.
>
I believe you missed the OP's actual goal. He's not interested in
linking printing options to specific rows of the foo table; he wants
each column of the foo table to have a single entry in the printing
options table; that is, he wants a foreign key reference to the system
catalog giving the columns of entity foo. He does, in fact, appear to
be interested in a foreign key reference to a table's metadata.
--
- David T. Wilson
david(dot)t(dot)wilson(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Joshua D. Drake | 2008-04-17 18:29:56 | In the belly of the beast (MySQLCon) |
Previous Message | Roberts, Jon | 2008-04-17 17:55:04 | Re: Using meta-data for foreign key? |