| From: | Rob Brown-Bayliss <rob(at)zoism(dot)org> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Richard Huxton <dev(at)archonet(dot)com>, PostgreSQL General List <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: oid's and primary keys on insert |
| Date: | 2002-08-09 20:32:39 |
| Message-ID: | 1028925158.1849.43.camel@everglade.zoism.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, 2002-08-10 at 08:22, Joe Conway wrote:
> what we called it, but same concept). We have the application call this
> function first to get the primary key for the main header record, then
> insert the header record, then reuse that value as the foreign key in
> the detail records.
Yeah, that would work, It would requirechanging the trigger, but as the
app is not in use yet thats not a big problem, call the function and
then insert with the key generated...
Why are the developers (maybe) getting rid of OID's? Wont they then
have to come up with another way of identifiying data inside postgresql?
--
*
* Rob Brown-Bayliss
*
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2002-08-09 20:34:35 | Re: oid's and primary keys on insert |
| Previous Message | Rob Brown-Bayliss | 2002-08-09 20:25:33 | Re: oid's and primary keys on insert |