Subject Re: serious problem with FBResultSet
Author rrokytskyy
> Well... Blobs again... I've been using that version of the driver
> that
> returned FBResultSetWithFields when a query was executed.
> FBResultSetWithFields cached the Blobs (Binaries, does not matter
> now), so when one wanted to read it, it returned an actually
> pre-fetched blob.
>
> Now that version I got from CVS yesterday, uses FBResultSet. This
> does
> not cache the blob values. Problem is the following: in autocommit
> mode, FBStatement starts the transaction, executes the query,
> creates
> the results, *immediately commits* the transaction and returns the
> resultset. Blobs can be read only with a valid transaction, but in
> autocommit mode before the first next() is called we already have no
> valid transaction.

Hmmm... sounds strange to me. Caching of the Blob data is still
there. I will check the FBResultSet. It might be that it was lost
when merging the FBResultSet and FBResultSetWithFields.

Regards,
Roman