Re: INSERT INTO ... RETURNING id not behaving as expected with SQLNumResultCols - Mailing list pgsql-odbc

From Gustavo Pinsard
Subject Re: INSERT INTO ... RETURNING id not behaving as expected with SQLNumResultCols
Date
Msg-id 4CADAAFD.2020501@rocksolid.com.br
Whole thread Raw
In response to INSERT INTO ... RETURNING id not behaving as expected with SQLNumResultCols  (Ryan Pfeiffer <malice_ryan@yahoo.com>)
Responses Re: INSERT INTO ... RETURNING id not behaving as expected with SQLNumResultCols  (Ryan Pfeiffer <malice_ryan@yahoo.com>)
List pgsql-odbc
Ryan,

What language are you writing your app? What is the code you're using to
capture the returning id?

Also, are you aware that you can fire a new SELECT statement after
you're done inserting?  In scenarios where you wouldn't have much
concurrency that can be a valid approach.

And don't forget that the OID column is there for you to inspect. Ever
tried a SELECT OID FROM MyTable ORDER BY OID DESC LIMIT 1 ?

Gustavo

On 07/10/2010 01:04, Ryan Pfeiffer wrote:
> I'm using Postgres 8.4.1 and psqlodbc 08.04.0200. I'm trying to execute a statement INSERT INTO table/values
RETURNINGid to get the serial id. Problem is, SQLNumResultCols shows that there are zero columns. The statement I used
worksfine in pgadmin. This seems really basic and I am somewhat new to databases and odbc, but does anyone have a
solution?
>
> Thanks,
> Ryan
>
>
>
>


Attachment

pgsql-odbc by date:

Previous
From: Ryan Pfeiffer
Date:
Subject: INSERT INTO ... RETURNING id not behaving as expected with SQLNumResultCols
Next
From: Hiroshi Inoue
Date:
Subject: Re: [BUGS] BUG #5694: Postgres ODBC SQLTables is not working correctly