[castor-dev] Long Transactions suggestion

[Niko Efthymiou]

Hi all,

I have a suggestion how to improve long transaction support, although I 
don't know if it's a good one...

My idea is no to close a result set if the object type that was queried 
implements the Timestampable interface. This would make life much easier 
wenn working with long transactions. (Otherwise you first have to copie 
all the objects into a new Collection and then close the db. This I 
think could cause gret performance loss if the noumber of objects 
returned ist big)

Alternative to this an aditional method could be added to the Database 
class, which returns an alternative implementation of ResultSet that 
doesn't close uppon commit().

Please tell me what you think?

Greets,

Niko

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
       unsubscribe castor-dev