[hibernate-dev] Cache region names are not prefixed in 5.3

I see that cache region names are not being prefixed in 5.3. EnabledCaching sets the TimestampsRegion region name to TimestampsRegion.class.getName(), and sets the QueryResultsRegion region name to QueryResultsRegion.class.getName(). [1] Without a prefix, WildFly is failing intermittently when

Re: [hibernate-dev] Simplify SQL function registration when bootstrapping via JPA

Its not so much hindering 6.0 that I am concerned with. The problem is updatability for the user. The more things they use that change = the more work to upgrade. On Wed, May 16, 2018 at 6:51 AM Vlad Mihalcea wrote: > I suppose this will be refactored considerably in

Re: [hibernate-dev] Simplify SQL function registration when bootstrapping via JPA

I suppose this will be refactored considerably in 6.x. However, it's just a small change and I don't think it will hinder any 6.x changes. I'm thinking of defining an SqlFunctionContributor interface (@FunctionalInterface) which can be provided via the properties Map that's supplied when using

Re: [hibernate-dev] Simplify SQL function registration when bootstrapping via JPA

This should maybe wait for 6.0. We are ditching SQLFunction in favor of a more AST-friendly contract. Beyond that, go for it. On Wed, May 16, 2018, 6:34 AM Vlad Mihalcea wrote: > Hi, > > I realized that only the native Hibernate bootstrapping mechanism allows > for

[hibernate-dev] Simplify SQL function registration when bootstrapping via JPA

Hi, I realized that only the native Hibernate bootstrapping mechanism allows for passing custom SQL functions. For JPA, we can extend the Dialect to register, but that's not always desirable as it requires a code change every time the user switches to a new Dialect version. For this reason, I

[hibernate-dev] Mail System Error - Returned Mail

<¹>ÒyÄï̙W½…¬Î!#A;ÛQrZ6ïúËcþÄú㣠Ÿ\á-äó롘ï\