Re: [Hibernate] Hibernate 2

[Christoph S. <ch...@sc...>]

hey all and happy new year

Gavin King wrote:

> Well, I imported the Hibernate2 sourcetree last night. Its in
> its own module which means that for the next couple of months
> we need to be *very* careful about handling patches. Bugfixes
> and minor improvements must be applied against *both* trees.
> (New features need only go into the Hibernate2 module.) As
> promised, the following changes were made:
>
> * packages are now net.sf.hibernate.*
> * project structure is changed; all java is now in src dir
> * code and tests relating to toplevel collections and  subcollections 
> was removed
>
> I have created a new hibernate-mapping-2.0.dtd, since we no
> longer need the <collection>, <subcollection>, <generated-key>
> elements and since collections may no longer appear beneath
> the root element.
>
> In the new DTD, I have also renamed the 'readonly' attribute to 
> 'inverse', since its name was causing all kinds of confusion for new 
> (and not-so-new) users.
>
> Please vote on the following proposals:
>
> * Rename the 'role' attribute to 'name' in all collection
>  elements in the new DTD, for consistency with <many-to-one>,  <id> 
> and <property> elements. The role attribute no longer
>  has any extra semantics beyond being a simple property
>  name.
>
> I am +1
>
+1

>
> * Change the default for unsaved-value to "null" in the new  DTD. The 
> current default is surprising to new users.
>
> I am +1
>
+1

>
> * Change the default for default-cascade to "save-update"
>  in the new DTD.
>
> I am undecided ... interested to hear the views of others.
>
+0

>
> * Remove the exception that occurs if you save an object
>  that is already associated with the session. This
>  makes save() consistent with saveOrUpdate().
>
> I am probably a +1 on this
>
+1

>
> * Remove the exception that occurs if you delete an object
>  that is already deleted in that session.
> I am undecided. The current behaviour forces people to
> think about who "owns" an object, who is responsible for
> deleting it. However, it *can* be a pain in the ass.
> In particular it means that:
>
> session.delete("from o in class java.lang.Object");
>
+1

>
>  
>