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 y
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.201
+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 wrappin
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,
whateve
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 pur
