Ah, sorry for being slow, I understand now about autocommit. Thanks!

Yes, hopefully when I get out from underneath this project I will check
it out. For now, I think I have to stick with the release driver as we
are looking to be feature complete in three weeks. Just so you (and
everyone else) knows, this driver has made the project go so much more
smoothly than it otherwise would have.

-----Original Message-----
From: Roman Rokytskyy [mailto:rrokytskyy@...]
Sent: Wednesday, October 22, 2003 2:10 PM
To: Firebird-Java@yahoogroups.com
Subject: [Firebird-Java] Re: A suggestion

> No, I cache with autocommit OFF. Basically, I have code like this.
> Let me know if you see anything garingly wrong:

Seems to be ok, but I did not check it in details :)

My main point is that blob is represented by 8 byte ID. This ID is
stored in the result set row and is cached in the statement object.
When you access blob content, completely different API is used (namely
isc_get_segment and isc_put_segment function). In case when autocommit
is ON, we have to cache blob content and cleaning the references makes
sense. However, in case when autocommit is OFF, it makes little sense
to clear the reference to 8 bytes, you will not save too much.

Another question: would you mind to try new pooling classes from the
CVS version? We have added statement pooling there too and it would be
nice to get some feedback from you.

Roman


Yahoo! Groups Sponsor
ADVERTISEMENT




To unsubscribe from this group, send an email to:
Firebird-Java-unsubscribe@yahoogroups.com



Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.