[hibernate-dev] Question regarding the JPA 1.0 decision of making ToOne associations as EAGER
Hi, Do you remember why the JPA User Group decided to make the ManyToOne and the OneToOne associations EAGER by default? In Hibernate 3.x, these associations used to be LAZY, so there must have been a reason for taking this decision. Thanks, Vlad ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Question regarding the JPA 1.0 decision of making ToOne associations as EAGER
The Hibernate team argued against this, but we were outvoted. So... sorry I cannot "justify it" ;) Obviously as our previous default shows we believe the associations should be lazy by default. On Sun, Feb 28, 2016 at 11:00 AM Vlad Mihalcea wrote: > Hi, > > > Do you remember why the JPA User Group decided to make the ManyToOne and > the OneToOne associations EAGER by default? > > In Hibernate 3.x, these associations used to be LAZY, so there must have > been a reason for taking this decision. > > > Thanks, > > Vlad > ___ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Question regarding the JPA 1.0 decision of making ToOne associations as EAGER
Thanks, Rhe only reason I found is this paragraph: "The EAGER default for OneToOne and ManyToOne is for implementation reasons (more difficult to implement), not because it is a good idea. Technically in JPA LAZY is just a hint, and a JPA provider is not required to support it, however in reality all main JPA providers support it, and they would be pretty useless if they did not." https://en.wikibooks.org/wiki/Java_Persistence/Relationships#Lazy_Fetching Vlad On Sun, Feb 28, 2016 at 7:08 PM, Steve Ebersole wrote: > The Hibernate team argued against this, but we were outvoted. So... sorry > I cannot "justify it" ;) > > Obviously as our previous default shows we believe the associations should > be lazy by default. > > > On Sun, Feb 28, 2016 at 11:00 AM Vlad Mihalcea > wrote: > >> Hi, >> >> >> Do you remember why the JPA User Group decided to make the ManyToOne and >> the OneToOne associations EAGER by default? >> >> In Hibernate 3.x, these associations used to be LAZY, so there must have >> been a reason for taking this decision. >> >> >> Thanks, >> >> Vlad >> ___ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] Question regarding the JPA 1.0 decision of making ToOne associations as EAGER
But to me that is not a reason EAGER is the default. As the passage says, LAZY is just a hint. So for a provider that does not support LAZY, EAGER would be used instead anyway. No, some of the EG members specifically argued for wanting to-one associations to be EAGER by default. IMO it was a bad decision. But the majority rule. On Sun, Feb 28, 2016 at 11:40 AM Vlad Mihalcea wrote: > Thanks, > > Rhe only reason I found is this paragraph: > > "The EAGER default for OneToOne and ManyToOne is for implementation > reasons (more difficult to implement), not because it is a good idea. > Technically in JPA LAZY is just a hint, and a JPA provider is not > required to support it, however in reality all main JPA providers support > it, and they would be pretty useless if they did not." > > https://en.wikibooks.org/wiki/Java_Persistence/Relationships#Lazy_Fetching > > Vlad > > On Sun, Feb 28, 2016 at 7:08 PM, Steve Ebersole > wrote: > >> The Hibernate team argued against this, but we were outvoted. So... >> sorry I cannot "justify it" ;) >> >> Obviously as our previous default shows we believe the associations >> should be lazy by default. >> >> >> On Sun, Feb 28, 2016 at 11:00 AM Vlad Mihalcea >> wrote: >> >>> Hi, >>> >>> >>> Do you remember why the JPA User Group decided to make the ManyToOne and >>> the OneToOne associations EAGER by default? >>> >>> In Hibernate 3.x, these associations used to be LAZY, so there must have >>> been a reason for taking this decision. >>> >>> >>> Thanks, >>> >>> Vlad >>> ___ >>> hibernate-dev mailing list >>> hibernate-dev@lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hibernate-dev >>> >> > ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [Search] Elasticsearch TermQuery translation
On 25 February 2016 at 16:25, Sanne Grinovero wrote: > On 25 February 2016 at 15:37, Gunnar Morling wrote: >> 2016-02-25 16:28 GMT+01:00 Sanne Grinovero : >>> On 25 February 2016 at 15:14, Gunnar Morling wrote: It's Monday morning. Having at least rudimentary docs would be great, but I won't be able to contribute to that by then :/ How about doing another "stealth Alpha" tomorrow and then do another, properly announced, one by the end of the current HSEARCH sprint? Then we can include some more useful stuff into the first "official" Alpha and also have a tad more time to work on docs. >>> >>> If you want a "stealth release" then you're not allowed to talk about >>> it in public ;) >> >> Hehe. >>> >>> I'd rather we start thinking about docs and get a bit of traction in the >>> news; >>> I don't expect massive chapters, but at least let's provide some >>> instructions >>> for people to start playing with it. >> >> Yes, I'd love that, too. >> >> It's just that I cannot do it myself right now, as I need to wrap up >> the slides/demo. So any help with some sort of "Getting started" guide >> would be greatly appreciated. Otherwise I can work on this next week. > > Of course. It's probably not effective to have more than 2 people > working on docs > at the same time anyway. I'll start myself and find a review peer.. > > I can do the release process over the weekend and push the announcement > on Monday, or maybe you want to reveal it on stage :) > Status: Alpha2 is in Maven, docs were written & uploaded. Only downside is they didn't get a review, but I think they are good enough for the current goal. - http://docs.jboss.org/hibernate/search/5.6/reference/en-US/html_single/#_integration_with_elasticsearch Let me know how you'd prefer we finalize the release; I still need to: - upload to sourceforge - update website - announcements ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] [Search] Elasticsearch TermQuery translation
Awesome! The docs look great, thanks a lot! +100 for pushing this out, I think it's ready for that. Cheers guys, --Gunnar 2016-02-29 1:59 GMT+01:00 Sanne Grinovero : > On 25 February 2016 at 16:25, Sanne Grinovero wrote: >> On 25 February 2016 at 15:37, Gunnar Morling wrote: >>> 2016-02-25 16:28 GMT+01:00 Sanne Grinovero : On 25 February 2016 at 15:14, Gunnar Morling wrote: > It's Monday morning. > > Having at least rudimentary docs would be great, but I won't be able > to contribute to that by then :/ > > How about doing another "stealth Alpha" tomorrow and then do another, > properly announced, one by the end of the current HSEARCH sprint? Then > we can include some more useful stuff into the first "official" Alpha > and also have a tad more time to work on docs. If you want a "stealth release" then you're not allowed to talk about it in public ;) >>> >>> Hehe. I'd rather we start thinking about docs and get a bit of traction in the news; I don't expect massive chapters, but at least let's provide some instructions for people to start playing with it. >>> >>> Yes, I'd love that, too. >>> >>> It's just that I cannot do it myself right now, as I need to wrap up >>> the slides/demo. So any help with some sort of "Getting started" guide >>> would be greatly appreciated. Otherwise I can work on this next week. >> >> Of course. It's probably not effective to have more than 2 people >> working on docs >> at the same time anyway. I'll start myself and find a review peer.. >> >> I can do the release process over the weekend and push the announcement >> on Monday, or maybe you want to reveal it on stage :) >> > > Status: Alpha2 is in Maven, docs were written & uploaded. > Only downside is they didn't get a review, but I think they are good > enough for the current goal. > - > http://docs.jboss.org/hibernate/search/5.6/reference/en-US/html_single/#_integration_with_elasticsearch > > Let me know how you'd prefer we finalize the release; I still need to: > - upload to sourceforge > - update website > - announcements ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
