hibernate-devel

[Hibernate-devel] big improvement

[Gavin_King/Cirrus%<CI...@ci...>]

I've just done some work today that removes one of the more annoying
restrictions. You no longer have to be careful about the order you create
(), save() and delete() objects in. Hibernate now does all that
automagically. This also makes use of save() much more desirable and makes
hibernate more efficient (performance-wise) by side effect :)

for example, previously you couldn't write code like this:

session = fac.openSession();

foo = new Foo();
bar = new Bar();

foo.setBar(bar);
bar.setFoo(foo);

session.save(foo);
session.save(bar);

session.commit();

session = fac.openSession();

// get the same foo and bar

session.delete(foo);
session.delete(bar);
session.commit();

Re: [Hibernate-devel] big improvement

[Paul S. <pau...@ne...>]

Gavin_King/Cirrus%CI...@ci... wrote:
> I've just done some work today that removes one of the more annoying
> restrictions. You no longer have to be careful about the order you create
> (), save() and delete() objects in. Hibernate now does all that
> automagically. This also makes use of save() much more desirable and makes
> hibernate more efficient (performance-wise) by side effect :)

I have one question that you might know the answer to off the top of 
your head.

The doco says somewhere that hibernate will do create's before delete's. 
If I use a primary key that's not a synthesised "oid" but a real-world 
attribute (e.g. part-number), as in the case of a legacy DB table 
structure, I get problems when I try to delete one object and then 
re-insert another object with that same primary key value.

Is this still the case? I know I can split it over two transactions, but 
that's not always possible or desirable.

Thanks, PaulS.