From: Gavin_King/Cirrus%<CI...@ci...> - 2002-05-29 02:49:14
|
I have finished the lifecycle objects feature (finally!) which I suspect a lot of people will be very happy about. I'm looking for a bit of input on details: Basically, at the moment, you can do things like: <many-to-one name="child" cascade="all"/> <set role="children" cascade="all"/> <key column="parent_id" <one-to-many class="ChildClass"/> </set> to force associated objects to be saved/deleted/updated along with the parent object. This should save a lot of application code. I was wondering: (a) is 'dependant' better than 'cascade' (b) would it be useful to support cascade="save", cascade="delete", cascade ="update" along with cascade="all", cascade="none"? I can't really see any great use to the extra stuff in (b). In other news, I decided to deprecate Session.create(). Does anyone have any objections to this? I am now working on documentation / tests / examples .... no new features for now. Gavin. |