Re: [hibernate-dev] Hibernate ORM master - 5.0
Forgot to CC hibernate-dev mailing list... - Original Message - > From: "Gail Badner" > To: "Steve Ebersole" > Sent: Tuesday, November 18, 2014 9:28:02 AM > Subject: Re: [hibernate-dev] Hibernate ORM master - 5.0 > > You mention possibly for 5.1: "Override EAGER fetching with LAZY (fetch > profiles, HQL, etc) refer to HHH-8558 and HHH-8559? > > - Original Message - > > From: "Steve Ebersole" > > To: "hibernate-dev" > > Sent: Thursday, October 30, 2014 8:44:23 AM > > Subject: [hibernate-dev] Hibernate ORM master - 5.0 > > > > It was decided that the massive work for 5.0 including metamodel and all > > the other changes was just taking too long, and that we'd split that work > > up into a number of intermediate versions. I wanted to highlight the > > proposed breakdown and solidify the roadmaps. The preliminary breakdown is > > as follows: > > > > > >- 5.0 > > - Java 6 or 7 (?) > > - EE 7 (JPA 2.1) > > - Wildfly 9 > > - Timeline : Spring 2015 > > - Required development > > - Transition to new bootstrapping APIs > > - MetadataSources, contributors, builders, etc for building > > SessionFactory > > - Keep Configuration as a migration aid, but align its > > processing and assumptions to follow new APIs > > - New naming strategy approach (implicit and physical split) > > - Pick "important" features from metamodel work based on new > > bootstrapping API > > - automatic quoting of identifiers that are keywords > > - ??? > > - Performance improvements > > - Cachng SPI changes based on feedback from Ehcahce and Infinispan > > - EntityKey proposal > > - Explore unifying entry keys for actual cache provider, cache > > SPI (CacheKey) and persistence-context (EntityKey) > > - Infinispan improvements, especially in local mode. Will > > require integrating a new Infinispan version and possible > > changes to > > hibernate-infinispan > > - ??? > > - OGM integration > > - "after persisters built" hook > >- others? > > - Java 8 type support > > - Date/Time > > - Optional > > - Java 9 type support > > - Money/Currency > > - Optional development (as time, resources allow) > > - Discriminator based multitenancy > > - JAXB instead of dom4j. > > - extended orm.xml xsd, deprecating hbm.xml format > > - Jandex usage > > - JdbcSession > > - Hibernate Spatial integration (depends on level of dependence on > > metamodel) > > - 5.1 > > - Java 6 or 7 (?) > > - EE 7 (JPA 2.1) > > - Widfly 9, or 10 > > - Timeline : TBD (Fall 2016?) > > - Required development > > - slips from 5.0 > > - new HQL parser > > - Antlr 3 or 4? > > - unified SQL generation? or limit to HQL parsing? > > - Optional development (as time, resources allow) > > - extend JPA criteria API with support for constructs from > > Hibernate's legacy criteria API > > - extend JPA criteria API with fluent support > > - Possibly - Override EAGER fetching with LAZY (fetch profiles, HQL, > > etc) > >- 5.2 > > - (if needed) > > - Java 6 or 7 (?) > > - EE 7 (JPA 2.1) > > - Widfly 9, or 10 > > - Required development > > - splits from 5.1 > > - 6.0 > > - SE and EE support levels TBD, but at least SE 8 > > - Required development > > - metamodel > > > > > > One additional consideration... I have been told (have not verified the > > details yet myself) that Hibernate ORM will currently not run in Java 8 at > > least in part because dom4j will not work in Java 8 (maybe just the version > > we use? again, have not verified details yet). If running 5.x versions of > > Hibernate in Java 8 is important to anyone, we might need to increase the > > priority of moving to JAXB over dom4j. > > ___ > > 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] MySQL fractional second precision (HHH-9444)
MySQL support for fractional seconds in temporal values is documented in [1]: Prior to MySQL 5.6.4, when storing a value into a column of any temporal data type, fractional part is discarded (truncated). When a column is defined as TIMESTAMP(N), N indicates display width rather than fractional seconds. MySQL 5.6.4 and up allows enabling fractional second support by defining a column like: TIME(n), DATETIME(n), TIMESTAMP(n), where 0 <= n <= 6. A value of 0 indicates no fractional seconds. For compatibiliby with previous MySQL versions, if no value for n is provided, then 0 is the default. This is inconsistent with standard SQL, which has a default of 6. In addition, inserting a temporal value in a column will result in rounding if the column is defined with fewer fractional digits than the value. Starting from MySQL 5.6.4, there are also differences in functions that involve temporal values. MySQL functions like NOW(), CURTIME(), SYSDATE(), or UTC_TIMESTAMP() can optionally take an argument for fractional seconds precision as in NOW(n), CURTIME(n), SYSDATE(n), or UTC_TIMESTAMP(n), where 0 <= n <= 6. For compatibiliby with previous MySQL versions, if no value for n is provided, then 0 is the default. I'm working on a new dialect to support fractional seconds. Since the support for fractional seconds began in MySQL 5.6.4 it kind of complicates naming. I assume MySQL5InnoDBDialect needs to be extended for the InnoDB engine. Is "MySQL564InnoDBDialect" too ugly? Is there any need to have a new dialect for other (non-InnoDB) MySQL engines (e.g., MySQL564DBDialect that extends MySQL5Dialect)? IIUC, to be consistent with the SQL standard the default for the temporal types in the new dialect(s) should be: registerColumnType( Types.TIMESTAMP, "datetime(6)" ); registerColumnType( Types.TIME, "time(6)" ); Is there a need the new dialect(s) to allow an application to define the number of fractional seconds to anything other than 6? If so, would it work to also add the following? registerColumnType( Types.TIMESTAMP, 6, "datetime($l)" ); registerColumnType( Types.TIME, 6, "time($l)" ); Also, IMO, Hibernate should render NOW(), CURTIME(), SYSDATE(), UTC_TIMESTAMP() as NOW(6), CURTIME(6), SYSDATE(6), or UTC_TIMESTAMP(6), respectively, unless an argument is specifically provided. As far as I can tell, Hibernate does not use MySQL's TIMESTAMP column type, so I don't think anything needs to be done to support fractional seconds for that type, or am I missing something here? Comments? Thanks, Gail [1] http://dev.mysql.com/doc/refman/5.6/en/fractional-seconds.html [2] https://hibernate.atlassian.net/browse/HHH-9444 ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] MySQL fractional second precision (HHH-8401, HHH-9444)
To clarify, HHH-8401 is to support MySQL fractional seconds; HHH-9444 is to fix test failures due MySQL's new support for fractional seconds. - Original Message - > From: "Gail Badner" > To: "Hibernate Dev" > Sent: Tuesday, November 18, 2014 1:59:26 PM > Subject: MySQL fractional second precision (HHH-9444) > > MySQL support for fractional seconds in temporal values is documented in [1]: > > Prior to MySQL 5.6.4, when storing a value into a column of any temporal data > type, fractional part is discarded (truncated). When a column is defined as > TIMESTAMP(N), N indicates display width rather than fractional seconds. > > MySQL 5.6.4 and up allows enabling fractional second support by defining a > column like: TIME(n), DATETIME(n), TIMESTAMP(n), where 0 <= n <= 6. A value > of 0 indicates no fractional seconds. For compatibiliby with previous MySQL > versions, if no value for n is provided, then 0 is the default. This is > inconsistent with standard SQL, which has a default of 6. In addition, > inserting a temporal value in a column will result in rounding if the column > is defined with fewer fractional digits than the value. > > Starting from MySQL 5.6.4, there are also differences in functions that > involve temporal values. MySQL functions like NOW(), CURTIME(), SYSDATE(), > or UTC_TIMESTAMP() can optionally take an argument for fractional seconds > precision as in NOW(n), CURTIME(n), SYSDATE(n), or UTC_TIMESTAMP(n), where 0 > <= n <= 6. For compatibiliby with previous MySQL versions, if no value for n > is provided, then 0 is the default. > > I'm working on a new dialect to support fractional seconds. Since the support > for fractional seconds began in MySQL 5.6.4 it kind of complicates naming. I > assume MySQL5InnoDBDialect needs to be extended for the InnoDB engine. > > Is "MySQL564InnoDBDialect" too ugly? > > Is there any need to have a new dialect for other (non-InnoDB) MySQL engines > (e.g., MySQL564DBDialect that extends MySQL5Dialect)? > > IIUC, to be consistent with the SQL standard the default for the temporal > types in the new dialect(s) should be: > registerColumnType( Types.TIMESTAMP, "datetime(6)" ); > registerColumnType( Types.TIME, "time(6)" ); > > Is there a need the new dialect(s) to allow an application to define the > number of fractional seconds to anything other than 6? If so, would it work > to also add the following? > registerColumnType( Types.TIMESTAMP, 6, "datetime($l)" ); > registerColumnType( Types.TIME, 6, "time($l)" ); > > Also, IMO, Hibernate should render NOW(), CURTIME(), SYSDATE(), > UTC_TIMESTAMP() as NOW(6), CURTIME(6), SYSDATE(6), or UTC_TIMESTAMP(6), > respectively, unless an argument is specifically provided. > > As far as I can tell, Hibernate does not use MySQL's TIMESTAMP column type, > so I don't think anything needs to be done to support fractional seconds for > that type, or am I missing something here? > > Comments? > > Thanks, > Gail > > [1] http://dev.mysql.com/doc/refman/5.6/en/fractional-seconds.html > [2] https://hibernate.atlassian.net/browse/HHH-9444 ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] ORM master
Only metamodel-related code was merged from the old metamodel branch into master, so there is definitely unmerged work still in metamodel-old. I would keep it around until things get sorted out. - Original Message - > From: "Steve Ebersole" > To: "hibernate-dev" > Sent: Wednesday, October 29, 2014 4:00:38 AM > Subject: Re: [hibernate-dev] ORM master > > FYI, does anyone need metamodel-old anymore? Can I just delete that one > upstream? > > On Wed, Oct 29, 2014 at 6:00 AM, Steve Ebersole wrote: > > > Ok, all done now. So at this point: > > > > 1) upstream/metamodel-old is the "metamodel" code as of the point before > > when we merged it to master > > 2) upstream/metamodel is the current state of metamodel work > > 3) upstream/master is currently the same as 4.3. It is the base from > > which I will start the discussed simplified 5.0 development > > > > > > > > On Wed, Oct 29, 2014 at 5:22 AM, Steve Ebersole > > wrote: > > > >> I just noticed that the old metamodel branch was still around upstream. > >> So far I have: > >> > >> 1) moved upstream/metamodel -> upstream/metamodel-old > >> 2) deleted upstream/metamodel > >> 3) moved upstream/master -> upstream/metamodel > >> > >> I'll wait a few minutes still before deleting master and re-priming it > >> from 4.3 > >> > >> > >> On Wed, Oct 29, 2014 at 4:13 AM, Steve Ebersole > >> wrote: > >> > >>> Per the face to face discussion yesterday (I'll send out more details > >>> later) I am working on branching master off to a new "metamodel" dev > >>> branch > >>> and priming a "new master" from 4.3 (the basic idea being to start work > >>> on > >>> a more targeted 5.0). > >>> > >>> Part of this is of course a massive change to the state of master > >>> upstream. If anyone needs me to wait before starting this please let me > >>> know immediately. Thanks. > >>> > >> > >> > > > ___ > 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] ORM master
If there is something you want then pull it over. On Nov 18, 2014 5:08 PM, "Gail Badner" wrote: > Only metamodel-related code was merged from the old metamodel branch into > master, so there is definitely unmerged work still in metamodel-old. I > would keep it around until things get sorted out. > > - Original Message - > > From: "Steve Ebersole" > > To: "hibernate-dev" > > Sent: Wednesday, October 29, 2014 4:00:38 AM > > Subject: Re: [hibernate-dev] ORM master > > > > FYI, does anyone need metamodel-old anymore? Can I just delete that one > > upstream? > > > > On Wed, Oct 29, 2014 at 6:00 AM, Steve Ebersole > wrote: > > > > > Ok, all done now. So at this point: > > > > > > 1) upstream/metamodel-old is the "metamodel" code as of the point > before > > > when we merged it to master > > > 2) upstream/metamodel is the current state of metamodel work > > > 3) upstream/master is currently the same as 4.3. It is the base from > > > which I will start the discussed simplified 5.0 development > > > > > > > > > > > > On Wed, Oct 29, 2014 at 5:22 AM, Steve Ebersole > > > wrote: > > > > > >> I just noticed that the old metamodel branch was still around > upstream. > > >> So far I have: > > >> > > >> 1) moved upstream/metamodel -> upstream/metamodel-old > > >> 2) deleted upstream/metamodel > > >> 3) moved upstream/master -> upstream/metamodel > > >> > > >> I'll wait a few minutes still before deleting master and re-priming it > > >> from 4.3 > > >> > > >> > > >> On Wed, Oct 29, 2014 at 4:13 AM, Steve Ebersole > > >> wrote: > > >> > > >>> Per the face to face discussion yesterday (I'll send out more details > > >>> later) I am working on branching master off to a new "metamodel" dev > > >>> branch > > >>> and priming a "new master" from 4.3 (the basic idea being to start > work > > >>> on > > >>> a more targeted 5.0). > > >>> > > >>> Part of this is of course a massive change to the state of master > > >>> upstream. If anyone needs me to wait before starting this please let > me > > >>> know immediately. Thanks. > > >>> > > >> > > >> > > > > > ___ > > 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] did hibernate.org crash?
Trying to open http://hibernate.org/dtd/hibernate-configuration-3.0.dtd, gives a: " Site temporarily disabled This page has been temporarily disabled due to a misconfigured custom domain. Are you the site owner? Follow the instructions for setting up a custom domain with GitHub pages to update your site's DNS records to point to the proper IP address. You can find more information in our GitHub Pages legacy IP deprecation blog post. If you have any questions, please contact support. " The above causes a WildFly test failure http://pastebin.com/fm8VMCcb (from org.hibernate.service.internal.JaxbProcessor.unmarshal). Scott ___ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
Re: [hibernate-dev] did hibernate.org crash?
Related question, should we instead be using the org/hibernate/hibernate-configuration-3.0.dtd in hibernate-core-4.3.7.Final.jar (instead of accessing the hibernate.org website)? On 11/18/2014 07:48 PM, Scott Marlow wrote: > Trying to open http://hibernate.org/dtd/hibernate-configuration-3.0.dtd, > gives a: > > " > Site temporarily disabled > > This page has been temporarily disabled due to a misconfigured custom > domain. > > Are you the site owner? Follow the instructions for setting up a custom > domain with GitHub pages to update your site's DNS records to point to > the proper IP address. > > You can find more information in our GitHub Pages legacy IP deprecation > blog post. If you have any questions, please contact support. > " > > The above causes a WildFly test failure http://pastebin.com/fm8VMCcb > (from org.hibernate.service.internal.JaxbProcessor.unmarshal). > > Scott > ___ > 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
