| From: | Erik Jones <erik(at)myemma(dot)com> | 
|---|---|
| To: | Mike Blackwell <maiku41(at)sbcglobal(dot)net> | 
| Cc: | pgsql-general(at)postgresql(dot)org | 
| Subject: | Re: Using meta-data for foreign key? | 
| Date: | 2008-04-17 16:14:57 | 
| Message-ID: | F3BD08A6-13C8-49DB-8CF3-A81981361B8A@myemma.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
On Apr 17, 2008, at 10:23 AM, Mike Blackwell wrote:
> I have an existing table in an app, along the lines of:
>
> CREATE TABLE foo (
>  name text,
>  address text,
>  some_numeric_info integer,
>  <a bunch of additional fields here>
> );
>
> I now need to be able to associate additional information (e.g.  
> printing
> order) with each field.  Is it a bad idea to use the (fully qualified)
> field name as a foreign key to link back to the table meta-data?  Is
> there a better way?
You're going to have to be *much* more specific about what you're  
trying to do/talk about.  A complete example would be best.
Erik Jones
DBA | Emma®
erik(at)myemma(dot)com
800.595.4401 or 615.292.5888
615.292.0777 (fax)
Emma helps organizations everywhere communicate & market in style.
Visit us online at http://www.myemma.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Blackwell | 2008-04-17 16:32:28 | Re: Using meta-data for foreign key? | 
| Previous Message | Ottavio Campana | 2008-04-17 16:04:50 | problem with tsearch and utf-8 on postgresql 8.1 |