hibernate-devel

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?

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

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

>Please use AFT for the website until I have more time (should be in one
>week) to work further on the documentation and eventually the website.

cool :)

I'm starting to think about some tutorial-style introductory documentation
but I'm just not sure that I'm the best person to write it...

>I'm on the Resin server mailinglist and also read/write in some Java
>centric newsgroups and a lot of people have problems deciding for an O/R
>mapper or even get a grip on the technology itself. I received three
>mails last week from developers asking me what to do, as I have evaluated
>most options (and mentioned that on the lists and groups).  Well, I guess
>Hibernate will get more downloads in the near future. :)

Ace.

(aaaah I keep forgetting thats Australian slang ... like "heaps")

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

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

Okay, there seems general agreement on this. So last night I actually tried
the change out. Two observations:


(1) Only three of my tests failed after the change + I have some fairly
wierd looking queries in there. I added "distinct" to the three offending
queries + all was working again.
(2) I think I spotted a measurable performance improvement. I need to do
some more tests to comfirm this.


So I checked that change in.


Incidentally benchmarking Hibernate has been a difficult problem because
its essentially such a small overhead above the actual JDBC calls (now
generally about 10% on my machines) that comparisons get flooded out by
random variation in the JDBC processing.

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

[Christian B. <chr...@bl...>]

On 07 Aug (11:42), Gavin_King/Cirrus%CI...@ci... wrote:

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

Please use AFT for the website until I have more time (should be in one
week) to work further on the documentation and eventually the website.
Everone's on vacation right now, pretty busy...

I'm on the Resin server mailinglist and also read/write in some Java
centric newsgroups and a lot of people have problems deciding for an O/R
mapper or even get a grip on the technology itself. I received three
mails last week from developers asking me what to do, as I have evaluated 
most options (and mentioned that on the lists and groups).  Well, I guess 
Hibernate will get more downloads in the near future. :)

-- 
Christian Bauer
tu...@in...

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

[Jon L. <jon...@xe...>]

Hi...

I thought I would chime in since I am one of the few people who has a
project using Hibernate in a production environment.

I took a look at my code and I don't think this change would break anything,
however you never know. :-)  I'm sure other people could do what I do and
bundle a specific version of Hibernate with a specific version of their
application.  In my case, I have bundled the 1.0 release of Hibernate with
the 1.0 release of my project since I know everything is working correctly
together.

As to making the change.  I support it.  That was one thing I always
wondered why it wasn't in the query language.

Jon...

----- Original Message -----
From: <Gavin_King/Cirrus%CI...@ci...>
To: "Christian Bauer" <chr...@bl...>
Cc: <hib...@so...>
Sent: Wednesday, August 07, 2002 3:42 AM
Subject: Re: [Hibernate-devel] what to do about select 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.
>
> 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?
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Hibernate-devel mailing list
> Hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>

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

[Brad C. <bra...@wo...>]

we r also using hibernate in a production environment.  this change makes
sense and is not a big deal for us, so go for it.

brad

----- Original Message -----
From: "Jon Lipsky" <jon...@xe...>
To: "Christian Bauer" <chr...@bl...>;
<Gavin_King/Cirrus%CI...@ci...>
Cc: <hib...@so...>
Sent: Wednesday, August 07, 2002 4:06 PM
Subject: Re: [Hibernate-devel] what to do about select distinct.....


> Hi...
>
> I thought I would chime in since I am one of the few people who has a
> project using Hibernate in a production environment.
>
> I took a look at my code and I don't think this change would break
anything,
> however you never know. :-)  I'm sure other people could do what I do and
> bundle a specific version of Hibernate with a specific version of their
> application.  In my case, I have bundled the 1.0 release of Hibernate with
> the 1.0 release of my project since I know everything is working correctly
> together.
>
> As to making the change.  I support it.  That was one thing I always
> wondered why it wasn't in the query language.
>
> Jon...
>
> ----- Original Message -----
> From: <Gavin_King/Cirrus%CI...@ci...>
> To: "Christian Bauer" <chr...@bl...>
> Cc: <hib...@so...>
> Sent: Wednesday, August 07, 2002 3:42 AM
> Subject: Re: [Hibernate-devel] what to do about select 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.
> >
> > 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?
> >
> >
> >
> > -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > Hibernate-devel mailing list
> > Hib...@li...
> > https://lists.sourceforge.net/lists/listinfo/hibernate-devel
> >
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Hibernate-devel mailing list
> Hib...@li...
> https://lists.sourceforge.net/lists/listinfo/hibernate-devel
>