I have clarified on HHH-10418, but I'll repeat the back-port portion: imo
it is a bad idea to back-port this.
In general I'd say that HHH-10418 should be closed as out-of-date as of 5.2
On Fri, Nov 17, 2017 at 12:29 AM Gail Badner wrote:
> I see that HHH-11356 is scheduled for 6.0.0.Beta1. Any
I see that HHH-11356 is scheduled for 6.0.0.Beta1. Any chance it could be
fixed in 5.3?
On Thu, Nov 16, 2017 at 10:23 PM, Gail Badner wrote:
> Oh, OK. There's a comment that made it sound like HHH-10418 was fixed in
> master. [1]
>
> Maybe it's just the CCE that got fixed. I'll add a comment to
Oh, OK. There's a comment that made it sound like HHH-10418 was fixed in
master. [1]
Maybe it's just the CCE that got fixed. I'll add a comment to HHH-10418 to
clarify that entities and collections still cannot be stored in the same
region in 5.2.
[1]
https://hibernate.atlassian.net/browse/HHH-10
No that is currently broken. See
https://hibernate.atlassian.net/browse/HHH-11356
This won't be fixed in 5.x as fixing it required significant changes to the
caching SPIs to resolve.
On Thu, Nov 16, 2017 at 8:10 PM Gail Badner wrote:
> Steve/Radim,
>
> Is it OK if an entity and collection regi
Steve/Radim,
Is it OK if an entity and collection region have the same name, they will
use the same AdvancedCache? I realize that the key will be different (as
long as hibernate.cache.keys_factory != simple).
I'm assuming they use the same access strategies, etc. I know there would
be problems if
