Hello Guillaume,
Thanks for your help.
I also think that it's a bug because, IMHO, prepared statements should
behave like non-prepared ones and delete on a view should be consistent
whatever is really done in the underlying structure of the database. Note
that, in my real code, once marked as del
On Sat, 2013-05-25 at 14:49 +0200, Brice André wrote:
> Hi Wolfe,
>
> First, thanks for your help.
>
> I tried your code, but it does not work... the function returns a string :
> "0". When I check, this command properly modifies one row, as expected.
>
It works for me with PQntuples.
> I don'
Hi Wolfe,
First, thanks for your help.
I tried your code, but it does not work... the function returns a string :
"0". When I check, this command properly modifies one row, as expected.
I don't know if it may help, but just in case... The DELETE operation is
not performed on a table : it is perf
Hi Brice,
I believe that you'll need PQcmdTuples - "Returns the number of rows
affected by the SQL command."
Watch out, it returns char* instead of int. I believe it's supposed to
be used for the UPDATE ... RETURNING as well, but I'd double check on
that.
It's under "30.3.3. Retrieving Re
Dear all,
I am trying to translate a code written in php to C++. So, I am now using
lipq in order to access my postgresql database from C++.
As performance is an important feature, I am using prepared statements.
I have a SQL statement that performs a 'DELETE ... RETURNING ... ' stuff
and I exec
Hi,
I have read in the future PostgreSQL 8.2 release note
(http://developer.postgresql.org/pgdocs/postgres/release-8-2.html) that
DELETE RETURNING will be supported. Tom, could please confirm that the
following PL/PGSQL statements will work on PostgreSQL 8.2?
INSERT INTO a(x, y)
DELETE FRO
