February 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HBX-1997) Remove class 'org.hibernate.tool.api.reveng.SchemaSelection' and replace occurrences with new interface 'org.hibernate.tool.api.reveng.RevengStrategy.SchemaSelection'

by Koen Aers (JIRA)

5 years, 10 months

1
0
0 / 0

[JIRA] (HBX-1996) Move class 'org.hibernate.tool.api.export.ExporterUtil' from 'hibernate-orm' into 'org.hibernate.tool.ant.util.ExceptionUtil' in 'hibernate-ant'

by Koen Aers (JIRA)

5 years, 10 months

1
0
0 / 0

[JIRA] (HHH-13879) Slow query log should use System#nanoTime not System#currentTimeMillis

by Vlad Mihalcea (JIRA)

Vlad Mihalcea ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13879 ( https://hibernate.atlassian.net/browse/HHH-13879?atlOrigin=eyJpIjoiMThmOD... ) Re: Slow query log should use System#nanoTime not System#currentTimeMillis ( https://hibernate.atlassian.net/browse/HHH-13879?atlOrigin=eyJpIjoiMThmOD... ) Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The major problem with currentTimeMillis() is that the result is affected by NTP, so you could end up with negative durations. Bitronix was developed by Ludovic and Brett, and Brett has also switched to using nanoTime in HikariCP ( https://github.com/brettwooldridge/HikariCP/issues/215 ). Frankly, I’m not aware of any nonoTime() issue. From all the source code I checked, it seems everyone is using it for durations. That’s why I asked you if you can provide more details about the nonoTime() problem you are worried about? The only problem I’m now aware of is that, on some systems, if the OS does not support monotonic clocks, nanoTime will fall back to wall clock time, just like currentTimeMillis(). But, the major Operating Systems do support monotonic clocks. ( https://hibernate.atlassian.net/browse/HHH-13879#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13879#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121- sha1:a269fed )

5 years, 10 months

1
0
0 / 0

[JIRA] (HSEARCH-3839) Sorting by numeric value has an exception "(expected=NUMERIC). Use UninvertingReader or index with docvalues"

by Waldemar Kłaczyński (JIRA)

Waldemar Kłaczyński ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HSEARCH-3839 ( https://hibernate.atlassian.net/browse/HSEARCH-3839?atlOrigin=eyJpIjoiNDh... ) Re: Sorting by numeric value has an exception "(expected=NUMERIC). Use UninvertingReader or index with docvalues" ( https://hibernate.atlassian.net/browse/HSEARCH-3839?atlOrigin=eyJpIjoiNDh... ) It behaves similarly in 6.0Beta5 hibernate-cheeses. DocValuesField "prices.bruttoPrice_sort" appears more than once in this document (only one value is allowed per field) Lucene 8.0 allows multi-valued for numeric sorted fields. The field should be declared as SortedNumericDocValuesField. ( https://hibernate.atlassian.net/browse/HSEARCH-3839#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-3839#add-comment?atlOrigin... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121- sha1:a269fed )

5 years, 10 months

1
0
0 / 0

[JIRA] (HHH-13879) Slow query log should use System#nanoTime not System#currentTimeMillis

by Sanne Grinovero (JIRA)

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13879 ( https://hibernate.atlassian.net/browse/HHH-13879?atlOrigin=eyJpIjoiODY3Mz... ) Re: Slow query log should use System#nanoTime not System#currentTimeMillis ( https://hibernate.atlassian.net/browse/HHH-13879?atlOrigin=eyJpIjoiODY3Mz... ) There’s no specific JDK bug as it’s not a bug, it’s just how it works and it’s documented. Feel free to search, there’s many discussions on the topic. I don’t know why Bitronix did what they did - that certainly is giving them a monotonic clock, but ask yourself why didn’t they use nanoTime then? (hint: because it won’t work either). Anyway, I’m not saying that you shouldn’t change it to nanoTime.. just pointing out that neither is a gret fit ./ ( https://hibernate.atlassian.net/browse/HHH-13879#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13879#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121- sha1:a269fed )

5 years, 10 months

1
0
0 / 0

[JIRA] (HHH-13619) size() does not work properly as select expression

by Steve Ebersole (JIRA)

5 years, 10 months

1
0
0 / 0

[JIRA] (HHH-13619) size() does not work properly as select expression

by Gail Badner (JIRA)

Gail Badner ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-13619 ( https://hibernate.atlassian.net/browse/HHH-13619?atlOrigin=eyJpIjoiYzIyMT... ) Re: size() does not work properly as select expression ( https://hibernate.atlassian.net/browse/HHH-13619?atlOrigin=eyJpIjoiYzIyMT... ) I've set up tests at: https://github.com/gbadner/hibernate-core/tree/HHH-13619 ( https://hibernate.atlassian.net/browse/HHH-13619#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-13619#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100121- sha1:a269fed )

5 years, 10 months

1
0
0 / 0

[JIRA] (HBX-1996) Move class 'org.hibernate.tool.api.export.ExporterUtil' from 'hibernate-orm' into 'org.hibernate.tool.ant.util.ExceptionUtil' in 'hibernate-ant'

by Koen Aers (JIRA)

5 years, 10 months

1
0
0 / 0

[JIRA] (HBX-1995) Rename package 'org.hibernate.tool.internal.dialect' to 'org.hibernate.tool.internal.reveng.dialect'

by Koen Aers (JIRA)

5 years, 10 months

1
0
0 / 0

[JIRA] (HBX-1995) Rename package 'org.hibernate.tool.internal.dialect' to 'org.hibernate.tool.internal.reveng.dialect'

by Koen Aers (JIRA)

5 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2020