Re: Help:updateRow() with CIDR types

On 24 Apr 2004, at 22:02, Kris Jurka wrote:

>
>
> On Sat, 24 Apr 2004, Moray Taylor wrote:
>
>> Thanks very much for the patch, but I'm having a problem with the
>> updated jars, I am getting a lot of these errors...
>>
>> ERROR:Operation requires a scrollable resultset, but this resultset is
>> FORWARD_ONLY.
>> org.postgresql.util.PSQLException: Operation requires a scrollable
>> resultset, but this resultset is FORWARD_ONLY.
>>     at
>> org.postgresql.jdbc2.AbstractJdbc2ResultSet.checkScrollable(AbstractJd
>> bc
>> 2ResultSet.java:179)
>>     at
>> org.postgresql.jdbc2.AbstractJdbc2ResultSet.first(AbstractJdbc2ResultS
>> et
>> .java:258)
>>
>> There errors occur when I do a getFirst() on the resultsets that get
>> create by methods like getCatalogs(), and getColumns()
>>
>> Has something else changed in the CVS that would cause this, I never
>> had these errors with the 7.5 (build 301) resultsets.
>>
>
> The cvs driver has been tightened up to default to TYPE_FORWARD_ONLY
> ResultSets per spec to try and increase the number of queries we can
> use
> cursor based fetches on.  Since it is a TYPE_FORWARD_ONLY ResultSet
> your
> getFirst() call fails because that only works on scrollable ResultSets.
> I don't think the TYPE_FORWARD_ONLY default should apply to the
> MetaData
> where the results are usually small and we want to allow the most
> flexibility in navigating them.
>
> Please try the attached patch or the newly uploaded jar files at
> http://www.ejurka.com/pgsql/jars/
>
> Kris Jurka
> <dbmdrstype.patch>


Does this mean the absolute() method will not work on any ResultSet
that I get from a query?

absolute() row access is totally critical to my application, will I
need to stick with 7.5 build 301?

Best regards

Moray