>Hibernate 2.0 beta
>==================
>* create a new module in CVS with improved directory
> structure
Yes! :)
> * rename packages to net.sf.hibernate
Yes! :)
>* replace existing configuration mechanisms
> with an interface that unifies the functionality
> of HibernateService, (the misnamed) Datastore,
> Hibernate.configure() and Configuration.
Kewl - but not a big thing in my book...but it might be for purists :)
>* query language enhancements, starting with:
> - OUTER JOIN, FULL JOIN, etc
> - AS instead of IN, IN CLASS
I've been thinking about this outer join thingy - and I hope it is one of
the first thing
we can get implemented. I tried last night, but I do not have enough
knowledge regarding the parser
to do it in due time. The reason I like to have it is that OUTER JOIN's in
the query language is
very important for many applications, and that I can't find a workaround to
this problem (except issuing two or more queries).
...
> - select new Foo(bar.name, bar.count) from .....
This one is going to be fuun :) (You didn't follow up on the discussion on
identity for these "value beans" - was it just to insane or ? :)
>* JCA implementation
Let's make this one as clean and simple as possible - no magic :)
>* removal of support for toplevel collections /
> subcollections
Fine by me :)
>Should 2.0 be 100% backward compatible with 1.2?
Not necessarily :)
>Because almost everything is defined by interfaces (and
>because I don't envisage any change in semantics for
>any operations of the core interfaces), we *could*
>continue to support the existing interfaces alongside
>the "new" net.sf.hibernate.* interfaces.
I see no reason why we should keep around the old cirrus.hibernate package
name....
I see three possibilities here:
(1) make a clean break - most applications will be portable
to 1.2 with nothing more than a few simple text search/
replace (s/cirrus.hibernate/net.sf.hibernate). This will
mean less code to manage / distribute.
(2) continue to support certain core interfaces:
- Session
- SessionFactory
- UserType
- Hibernate
- Query
- ScrollableResults
- ???
What is the difference between 1 and 2 ?
Are you going to change core names like Query, or is it the actual methods
on the interface you are going to change ?
Or is option 2 just about keeping the old cirrus.hibernate prefix for those
interfaces ?
Im at least +1 for (1)...
Another suggestion for Hibernate 1.2 is to look into adding support for
RowSet's - or at least provide enough information from the result of an
query to implement an RowSet efficently. I think RowSet is much better,
simpler and richer than just returning Collection of Object[] ....(and I
now the "new Foo(name, otherstuff)" will help here - but still :)
That was my 2 cents :)
/max
-------------------------------------------------------
This SF.NET email is sponsored by: Order your Holiday Geek Presents Now!
Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, Caffeinated Soap,
MP3 Players, XBox Games, Flying Saucers, WebCams, Smart Putty.
T H I N K G E E K . C O M http://www.thinkgeek.com/sf/
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel
