| From: | Rob Brown-Bayliss <rob(at)zoism(dot)org> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Andrew Sullivan <andrew(at)libertyrms(dot)info>, PostgreSQL General List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: oid's and primary keys on insert |
| Date: | 2002-08-10 03:33:52 |
| Message-ID: | 1028950431.3626.6.camel@everglade.zoism.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, 2002-08-10 at 15:23, Joe Conway wrote:
> > Thats realy the only reason I didn't do that. Not realy a goot reason
> > at that...
> >
>
> I had the exact same experience. Having a 2 column primary key on every
> table (and hence for every foreign key as well) gets unmanageable pretty
> quickly.
Yep, exactly. I have just been thinking that it was not really a good
reason and I must have had another reason there it is, foreign keys...
Thanks, I almost convinced myself to go back...
--
*
* Rob Brown-Bayliss
*
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2002-08-10 05:04:24 | Re: [GENERAL] workaround for lack of REPLACE() function |
| Previous Message | Joe Conway | 2002-08-10 03:23:54 | Re: oid's and primary keys on insert |