Well, we've made huge progress on the 2.1 roadmap. So I'm considering
finidhing the caching stuff, bumping the multi-table mappings stuff to 2.2
and then going into bugfix mode.

But anyway, getting to the point.....we now have a fully working Criteria
query API, with full support for associations, etc.

cats = session
    .createCriteria(Cat.class)
    .setMaxResults(10)
    .setFetchMode("mate", FetchMode.LAZY)
    .createCriteria("kittens")
        .add ( Expression.like("name", name) )
    .list();


I would VERY much appreciate if people would take the time to check out
what I've done and give feedback. The QBC API is documented in both the
user manual and Javadoc, so you should be able to figure it out.


All in the v21branch.


**********************************************************************
Any personal or sensitive information contained in this email and
attachments must be handled in accordance with the Victorian Information
Privacy Act 2000, the Health Records Act 2001 or the Privacy Act 1988
(Commonwealth), as applicable.

This email, including all attachments, is confidential.  If you are not the
intended recipient, you must not disclose, distribute, copy or use the
information contained in this email or attachments.  Any confidentiality or
privilege is not waived or lost because this email has been sent to you in
error.  If you have received it in error, please let us know by reply
email, delete it from your system and destroy any copies.
**********************************************************************






-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
hibernate-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/hibernate-devel

Reply via email to