Re: [Hibernate-devel] what to do about select distinct.....

[Gavin_King/Cirrus%<CI...@ci...>]

>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.

yeah, I do think that if something like this looks inevitable then 'tis
best it be done quickly.

But I *do* want to make it clear that I don't plan to make a habit of
things like this.....

>But I think not a lot of people will be using Hibernate in a production
>environment.

No not *many* people, but there are a few and I'm sensitive to their
concerns because they have been supporting the project from an early
stage. Of course, some of those projects can probably continue to use
whatever older version they are currenty using (or at least upgrade
as far as 1.0.1b which is quite reliable.

I will probably maintain 1.0.x as a seperate branch if any major bug shows
up in 1.0.1.

For projects in development, it probably isn't such a huge wrenching
change to add "distinct" in a couple of query strings. (Most queries
return distinct result sets with or without the distinct keyword
*anyway*)

P.S. Christian, I added the FAQ page to version 1.1 beta 2 but I had a
question for you: are we continuing to use AFT for the website? Or should I
be doing new stuff like this in docbook?