[hibernate-dev] JDK 11 Early Access build 8 available

2018-04-12 Thread Rory O'Donnell 
Hi Sanne,

**JDK 11 EA build 8, *under both the GPL and Oracle EA licenses, is 
now available at **http://jdk.java.net/11**. **
*

  * Newly approved Schedule, status & features
  o http://openjdk.java.net/projects/jdk/11/
  * Release Notes:
  o http://jdk.java.net/11/release-notes
  * Summary of changes
  o https://download.java.net/java/early_access/jdk11/8/jdk-11+8.html

*Notable changes in JDK 11 EA builds since last email:*

  * Build 8:
  o If you have a library that uses the Selector API heavily then
now would be a good time to test it out. [1]
  * Build 7
  o The VM option "-XX:+AggressiveOpts" is deprecated in JDK 11 and
will be removed in a future release.
  * Build 6:
  o JDK-8193033 : remove terminally deprecated
sun.misc.Unsafe.defineClass. Users should use the public
replacement `java.lang.invoke.MethodHandles.Lookup.defineClass`
which was added in Java SE 9. [2]

**


*SURVEY: The HotSpot Serviceability Agent (SA) *[3]

  * If you have used, or have (support) processes that utilize the
Serviceability Agent or related APIs, then we would definitely
appreciate if you would complete this survey:
https://www.surveymonkey.com/r/CF3MYDL


Regards,
Rory

[1] http://mail.openjdk.java.net/pipermail/nio-dev/2018-April/004964.html
[2] 
https://docs.oracle.com/javase/9/docs/api/java/lang/invoke/MethodHandles.Lookup.html#defineClass-byte:A-
 

[3] http://mail.openjdk.java.net/pipermail/jdk-dev/2018-April/001052.html

-- 
Rgds,Rory O'Donnell
Quality Engineering Manager
Oracle EMEA , Dublin, Ireland

___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

[hibernate-dev] HHH-8944 - ColumnTransformer handling is too aggressive in qualifying "column names"

2018-04-12 Thread Steve Ebersole 
Anyone know of places where we document ColumnTransformer read-fragment
handling as qualifying columns other than the column the transformer is
attached to?  E.g., consider:

@Column( name="dob" )
@ColumnTransformer( read="SYSDATE - dob / 365", ... )
public int getAge() { ... }

Currently, Hibernate will try to qualify both "SYSDATE" and "dob" with
table alias.  The simple fix is to simply limit the qualification to the
column that the transformer is attached to ("dob").  Just want to make sure
that we do not document anywhere that multiple column references will all
be replaced.  E.g. (contrived):

@Column( name="dob" )
@ColumnTransformer( read="(SYSDATE - dob / 365) + offset", ... )
public int getAge() { ... }

The question is whether both "dob" and "offset" columns will get
qualified.  Allowing this is much more involved, requiring that we somehow
allow configuration of all the referenced columns that should be qualified
(which has its own set of difficulties when it comes to multi-table
structures).

I propose the simple solution, unless there are any objections
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev

Re: [hibernate-dev] HHH-8944 - ColumnTransformer handling is too aggressive in qualifying "column names"

2018-04-12 Thread Steve Ebersole 
https://github.com/hibernate/hibernate-orm/pull/2237

On Thu, Apr 12, 2018 at 7:45 AM Steve Ebersole  wrote:

> Anyone know of places where we document ColumnTransformer read-fragment
> handling as qualifying columns other than the column the transformer is
> attached to?  E.g., consider:
>
> @Column( name="dob" )
> @ColumnTransformer( read="SYSDATE - dob / 365", ... )
> public int getAge() { ... }
>
> Currently, Hibernate will try to qualify both "SYSDATE" and "dob" with
> table alias.  The simple fix is to simply limit the qualification to the
> column that the transformer is attached to ("dob").  Just want to make sure
> that we do not document anywhere that multiple column references will all
> be replaced.  E.g. (contrived):
>
> @Column( name="dob" )
> @ColumnTransformer( read="(SYSDATE - dob / 365) + offset", ... )
> public int getAge() { ... }
>
> The question is whether both "dob" and "offset" columns will get
> qualified.  Allowing this is much more involved, requiring that we somehow
> allow configuration of all the referenced columns that should be qualified
> (which has its own set of difficulties when it comes to multi-table
> structures).
>
> I propose the simple solution, unless there are any objections
>
___
hibernate-dev mailing list
hibernate-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev