hello all,

I'm working on an application with Hibernate.  When a record is
modified, instead of updating that DB row, a new row is inserted and
the original row is marked obsoleted, so that all user actions can be
traced back when there's need.

As an example, now I update the field quantity from 1 to 20.  Here is
how I do it with hibernate:

...
newInfo = sess.load( key );
newInfo.setQty( 20 );

// update the old rec
oldInfo = sess.load( key );
oldInfo.setObsoYn( "Y" );
sess.update( oldInfo );

// add a new rec
sess.save( info );
trans.commit();
...

Sadly, newInfo and oldInfo seems to be pointing to the same instance,
and after all the actions I end up getting both records to have
qty==1.

Is there any way I can avoid them to interfere with each other?

thx
george