Future plans:
Next release: 1.2.1
===================
* various bugfixes
* full support for Clob and Blob
* FlushMode API + deprecation of suspend/resumeFlushes
* Improved logging of bind variables, etc.
1.2.1 is almost ready to go. Should be released in one
to two weeks. This will be a very stable platform for
development and we should continue to fix any bugs in
the 1.2 branch concurrently with 2.0 development.
Hibernate 2.0 beta
==================
* create a new module in CVS with improved directory
structure
* rename packages to net.sf.hibernate
* replace existing configuration mechanisms
with an interface that unifies the functionality
of HibernateService, (the misnamed) Datastore,
Hibernate.configure() and Configuration.
* query language enhancements, starting with:
- OUTER JOIN, FULL JOIN, etc
- AS instead of IN, IN CLASS
- select new Foo(bar.name, bar.count) from .....
* JCA implementation
* removal of support for toplevel collections /
subcollections
That list of features (for 2.0) should be considered a
proposal. If anyone thinks there are more urgent things
than those listed (ie. more urgent for the user base as
a whole, rather than for themseleves personally), we can
vote on it.
Something I would like everyone to consider and vote on
at this stage is:
Should 2.0 be 100% backward compatible with 1.2?
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.
However, I am quite keen to actually rip out a lot of code
relating to support for toplevel collections and the various
old configuration mechanisms.
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
- ???
(3) Full backward compatibility
Lets discuss / vote on this now, even though we won't be
starting work on 2.0 for a few weeks now. People voting for
(3) will be assumed to be volunteering for some of the
extra work involved in implementing / maintaining this ;)
I suspect that many people would be tempted to vote for (2).
But is there really *that* much value in that for the users?
The interfaces themselves arent changing, so its a simple
search/replace followed be recompile.
peace
Gavin
********** CAUTION - Disclaimer **********
This message may contain privileged and confidential
information. If you are not the intended recipient of this
message (or responsible for delivery of the message to
such person) you are hereby notified that any use,
dissemination, distribution or reproduction of this message
is prohibited. If you have received this message in error,
you should destroy it and kindly notify the sender by reply
e-mail. Please advise immediately if you or your employer
do not consent to Internet e-mail for messages of this kind.
Opinions, conclusions and other information in this
message that do not relate to the official business of
Expert Information Services Pty Ltd ("The Company")
shall be understood as neither given nor endorsed by it.
The Company advises that this e-mail and any attached
files should be scanned to detect viruses. The Company
accepts no liability for loss or damage (whether caused
by negligence or not) resulting from the use of any
attached files.
**EIS******** End of Disclaimer **********
-------------------------------------------------------
This SF.NET email is sponsored by: The Best Geek Holiday Gifts!
Time is running out! Thinkgeek.com has the coolest gifts for
your favorite geek. Let your fingers do the typing. Visit Now.
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
