From: | Ryan Bradetich <rbrad(at)hpb50023(dot)boi(dot)hp(dot)com> |
---|---|
To: | clark(dot)evans(at)manhattanproject(dot)com |
Cc: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Sequences.... |
Date: | 1999-03-16 01:06:18 |
Message-ID: | 199903160106.SAA10356@hpb50023.boi.hp.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Ryan Bradetich wrote:
> > > Back to my origional point .. I think we need another system table to map
the
> > > sequence oid to the table's oid. I've noticed this done with the
inheritance,
> > > indexes, etc ... but I don't see a pg_sequence table.
>
> Sounds good.
>
> As long as a sequence can point to more than
> one table/column combination.
>
> Or, I guess, you can have the relationship 1-1 for
> the SERIAL type, but this should not prevent using
> sequences across more than one table if you don't use SERIAL.
> I often use a sequence for 3 or more tables in a system
> so that I can use 'generic' functions on the tables
> and produce reports without conficting primary keys..
>
> :) Clark
Hmm.. Good points.... I'll make sure that doesn't happen. Thanks for the tips.
:)
-Ryan
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Perdue | 1999-03-16 01:25:58 | Re: [HACKERS] "CANNOT EXTEND" - |
Previous Message | Patrick Welche | 1999-03-15 23:51:15 | Re: [HACKERS] Developers Globe (FINAL) |