pgsql-server: ResultSet.moveToCurrentRow was checking the cached - Mailing list pgsql-committers

From jurka@svr1.postgresql.org (Kris Jurka)
Subject pgsql-server: ResultSet.moveToCurrentRow was checking the cached
Date
Msg-id 20040913071430.B6711329E45@svr1.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
ResultSet.moveToCurrentRow was checking the cached updateability flag
assuming it had been set instead of correctly calling the
isUpdateable() method which sets the flag if needed.  This usually
worked because moveToCurrentRow is only useful after a
moveToInsertRow call which would set the flag, but this is not
required.

David Bucciarelli

Tags:
----
REL7_4_STABLE

Modified Files:
--------------
    pgsql-server/src/interfaces/jdbc/org/postgresql/jdbc2:
        AbstractJdbc2ResultSet.java (r1.25.2.8 -> r1.25.2.9)

(http://developer.postgresql.org/cvsweb.cgi/pgsql-server/src/interfaces/jdbc/org/postgresql/jdbc2/AbstractJdbc2ResultSet.java.diff?r1=1.25.2.8&r2=1.25.2.9)

pgsql-committers by date:

Previous
From: neilc@svr1.postgresql.org (Neil Conway)
Date:
Subject: pgsql-server: Due to popular domand, backport fix for a typo in the
Next
From: jurka@svr1.postgresql.org (Kris Jurka)
Date:
Subject: pgsql-server: Protected access to variable m_preparedCount via