| From: | Clark Evans <clark(dot)evans(at)manhattanproject(dot)com> |
|---|---|
| To: | Ryan Bradetich <rbrad(at)hpb50023(dot)boi(dot)hp(dot)com> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Sequences.... |
| Date: | 1999-03-15 22:59:10 |
| Message-ID: | 36ED90BE.F904CF97@manhattanproject.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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-03-15 23:00:47 | Re: [HACKERS] Re: Developers Globe (FINAL) |
| Previous Message | Vince Vielhaber | 1999-03-15 22:57:35 | Re: [HACKERS] Re: Developers Globe (FINAL) |