On Mon, 16 Feb 2009 10:37:27 +0100, Heikki Linnakangas
wrote:
You can read the value returned by currval into a host language variable
and send it back as a ?.
Wouldn't it be possible to do UPDATE booking_entries SET date = ? where id =
(SELECT currval('booking_entries_id_seq'::regclass)); t
toruvinn wrote:
On Mon, 16 Feb 2009 10:37:27 +0100, Heikki Linnakangas
wrote:
You can read the value returned by currval into a host language
variable and send it back as a ?.
Wouldn't it be possible to do UPDATE booking_entries SET date = ? where
id = (SELECT currval('booking_entries_id_seq':
Mathias Seiler wrote:
I'm not sure if I'm doing something terribly wrong here, but I when I
noticed a slowdown during a large transaction I dig into the problem and
found that when I use this prepared statement:
UPDATE booking_entries SET date = ? where id =
currval('booking_entries_id_seq'::reg
The following bug has been logged online:
Bug reference: 4656
Logged by: Mathias Seiler
Email address: mathias.sei...@gmail.com
PostgreSQL version: 8.3.6
Operating system: Debian Linux Lenny (testing)
Description:Indexes not used when comparing nextval() and currval()