> This "portable" function is so unportable that I see no reason to
> accept it as precedent.
Hm. Instead of altering the syntax, what slipping in the last
inserted/updated tuple into the PQResult object? Maybe is a protocol
level option? Now everybody gets to use it with minimal muss.
pgsql-hackers by date
|Next:||From: Joshua D. Drake||Date: 2005-02-02 21:54:48|
|Subject: Re: pg_dump bug in 7.3.9 with sequences|
|Previous:||From: Tom Lane||Date: 2005-02-02 21:21:48|
|Subject: Re: pg_dump bug in 7.3.9 with sequences |