Gavin King wrote:
An even better (and much easier to implement) approach might be to simply
skip the nullification if the identifier of the transient instance indicates
that it already exists on the database.
Yep, it would be faster...
Thats easy to implement. You wanna take a stab at it Andre
: "Andrea Aime" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 10, 2002 11:31 PM
Subject: [Hibernate] Long transactions, object update and many-to-one...
> Hi everybody,
> I have a little feature request/question for you.
> Suppose you have t
Francois Beausoleil wrote:
Hello Andrea,
This has already been implemented. See Session.disconnect() in the
documentation.
Hope that helps !
Bye,
Francois
My application is a J2EE application, with both swing and html
interfaces (the
latter is more limited, for the public, the former is for
Hi everybody,
I have a little feature request/question for you.
Suppose you have two beans Customer, Country, and Customer
has a many-to-one property of type Country (not-null). In a long
transaction I load all of the Countries to fill in a JCombobox
in a form to input a new Customer. Then, when th
