need simple strategy for universal extension table - Mailing list pgsql-general

From TJ Talluto
Subject need simple strategy for universal extension table
Date
Msg-id UL8kd.80193$Kl3.64029@twister.socal.rr.com
Whole thread Raw
Responses Re: need simple strategy for universal extension table
List pgsql-general
Instead of putting the same 12 columns on every table (these 12 columns
contain info about who created the record and when, for example)... It may
be more efficient to make a new table to hold that data.

This new table would act as a universal extension table.  Instead of having
FKs back to any particular table, it would contain regular keys that point
back to whatever table::record is its source.

I was thinking of using two keys only:

xmOwnerInfo
COL1 PK* oidParentTable
COL2 PK* oidParentTablesRecord
COL3-15 [attribs]

Thoughts?

--
TJ Talluto
torpedo51 at yahoo dot com

pgsql-general by date:

Previous
From: "Arthur L. Rubin"
Date:
Subject: Re: Important Info on comp.databases.postgresql.general
Next
From: Dawid Kuroczko
Date:
Subject: Re: How many secondary databases can I create?