Re: [hibernate-dev] HHH-11147 - bytecode based "proxies"
Hi Steve, We had discussed releasing in 5.4, and possibly 5.3, with the default for hibernate.bytecode.allow_enhancement_as_proxy=false. I am in favor of this. Are you suggesting that the default behavior would effectively be to set hibernate.bytecode.allow_enhancement_as_proxy=true in 5.5? Do you think there would be any need to be able to restore the earlier behavior in 5.5? IOW, would we even need the property in 5.5? Regards, Gail On Mon, May 13, 2019 at 10:11 AM Sanne Grinovero wrote: > Hi Steve, > > like Christian, I would probably target ORM 6, but it's up to you. > > If you would rather recommend a 5.5 to get these improvements out > earlier, I have no objections and can help with that. > > Thanks, > Sanne > > On Mon, 13 May 2019 at 16:20, Christian Beikov > wrote: > > > > +1 for 6 > > > > Am 13.05.2019 um 15:25 schrieb Steve Ebersole: > > > Over the last 3 weeks or so, we have put a lot of work into HHH-11147 > which > > > essentially allows bytecode enhancement to behave like the more > traditional > > > proxy feature (create a reference based solely on the entity id). > > > > > > We are wrapping up development of that improvement, enhancement, > change, > > > whatever-you-want-to-call-it... One remaining question however is how > to > > > make this change available in terms of releases. It seems to big of a > deal > > > to simply drop in a new bug-fix release. > > > > > > Should we consider a 5.5 release? Push it to 6? Thoughts? > > > ___ > > > 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 > ___ > 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] HHH-11147 - bytecode based "proxies"
+1 for 6 Am 13.05.2019 um 15:25 schrieb Steve Ebersole: > Over the last 3 weeks or so, we have put a lot of work into HHH-11147 which > essentially allows bytecode enhancement to behave like the more traditional > proxy feature (create a reference based solely on the entity id). > > We are wrapping up development of that improvement, enhancement, change, > whatever-you-want-to-call-it... One remaining question however is how to > make this change available in terms of releases. It seems to big of a deal > to simply drop in a new bug-fix release. > > Should we consider a 5.5 release? Push it to 6? Thoughts? > ___ > 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
[hibernate-dev] HHH-11147 - bytecode based "proxies"
Over the last 3 weeks or so, we have put a lot of work into HHH-11147 which essentially allows bytecode enhancement to behave like the more traditional proxy feature (create a reference based solely on the entity id). We are wrapping up development of that improvement, enhancement, change, whatever-you-want-to-call-it... One remaining question however is how to make this change available in terms of releases. It seems to big of a deal to simply drop in a new bug-fix release. Should we consider a 5.5 release? Push it to 6? Thoughts? ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
[hibernate-dev] Post-connect queries for 6.1?
I thought it would be good to have an API that will call any registered queries upon connecting to the database, and maybe ones before returning it to the connection pool. I'm thinking it should be called in the implementations of ConnectionProvider and MultiTenantConnectionProvider. The basic purpose would be so you can set certain parameters. For example in setting the timezone in PostgreSQL: SET SESSION TIME ZONE 'UTC'; Or in MySQL: SET SESSION time_zone = 'Europe/Berlin'; This would of course require dialect handling, and access to some of the configuration settings given to the SessionFactory. There should also be a way for users to customize these with a per-persistence-unit configuration of some sort. They might want to pass other such runtime tweaks. Someone may want to send something like this to their MySQL: SET SESSION sql_mode = 'TRADITIONAL,ANSI'; I realize it's too late to think about this for 6.0, but it's something to consider for later on. ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
