pgsql-server: ResultSet.moveToCurrentRow was checking the cached

From: jurka(at)svr1(dot)postgresql(dot)org (Kris Jurka)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql-server: ResultSet.moveToCurrentRow was checking the cached
Date: 2004-09-13 07:14:30
Message-ID: 20040913071430.B6711329E45@svr1.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Kris Jurka 2004-09-13 08:02:42 pgsql-server: Protected access to variable m_preparedCount via
Previous Message Neil Conway 2004-09-13 01:59:39 pgsql-server: Due to popular domand, backport fix for a typo in the