On 07 Aug (11:11), Gavin_King/[EMAIL PROTECTED] wrote: > What I would really like to do is push responsibility for this into the > application by allowing the DISTINCT keyword in the Hiberante query and > remove the select="distinct|all" mapping attribute. > > Unfortunately, this change would break existing code that assumes a > distinct result set from a query without an explicit "DISTINCT".
Well, my concerns to this change are not technical. I appreciate the decision and think it's better to break things now in an early stage. But I think not a lot of people will be using Hibernate in a production environment. I have a small test application (an AddressBook) that I use to stress and feature test O/R mappers and all kind of things. It's really basic, the most complex thing is bidirectional one-to-many relationships (no M:N). Hibernate managed this application at 1.0.1, which was only two or three weeks ago. I know from my experience that it will take a lot more to make a useful application. I doubt anyone is currently using Hibernate for that purpose (no offence meant, I really believe it will be in the near future). -- Christian Bauer [EMAIL PROTECTED] ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
