RE: [Hibernate-devel] Lifecycle Objects

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

> I assume calling save() early on isn't practical, before initialization
of
> the object is complete.

calling save() "early on" is _exactly_ the same as calling create(). Its
inefficient, however, because you end up INSERTing a row full of nulls that
must then be immediately UPDATEd. So you accomplish in two SQL statements
what would normally be doable in one. (Thats why i'm deprecating create,
incidently.) Somewhere back in the dim dark past this was how hibernate
avoided violating foreign key constraints. Now it has a much cleverer
approach....