Heikki Linnakangas wrote:
Yes, that's an intentional change. From release notes:
I had the same problem this morning. We provide a sample database with
LATIN1 encoding (included in our setup). So how can i change my encoding
to have a database that can be used with PG 8.1; 8.1; 8.2 and 8.3
wit
It would have failed if you had run the cursor far enough to fetch one
of the bad rows.
regards, tom lane
The difference is that in one case the query fails and in the other the
FETCH command fails.
Our problem is that if a query succeeds we use a count(*) of that q
Following query fails in pgAdmin which is OK because the field PLZZ
contains characters:
select * from "PERSONEN" where (CAST("PERSONEN"."PLZZ" AS INTEGER) >=
7 );
but if using the same query with a cursor ist works:
START TRANSACTION;
DECLARE c21112234 SCROLL CURSOR FOR select * from "
