Re: calling currval() before nextval() patch adding

From: John Hansen <john(at)geeknet(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: calling currval() before nextval() patch adding
Date: 2004-11-08 01:49:08
Message-ID: 1099878548.16869.65.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

> Hmmm,.... is mysql's last_insert_id behaviour really that much to ask
> for?

Come to think of it,.... maybe the attached last_insert_id() patch is a
better option. Actually copying the behaviour of mysql's counterpart.

... John

Attachment Content-Type Size
last_insert_id.diff text/x-patch 5.5 KB

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2004-11-08 05:22:08 Re: cygwin build failure
Previous Message John Hansen 2004-11-08 00:26:07 Re: calling currval() before nextval() patch adding