June 2020 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-14089) Physical sequence information not fetched correctly when using pooled optimizer

by Darko Pejchinov (JIRA)

3 years, 10 months

1
0
0 / 0

[JIRA] (HHH-14089) Physical sequence information not fetched correctly when using pooled optimizer

by Darko Pejchinov (JIRA)

3 years, 10 months

1
0
0 / 0

[JIRA] (HHH-14089) Physical sequence information not fetched correctly when using pooled optimizer

by Darko Pejchinov (JIRA)

Darko Pejchinov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ef73cb... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYmM0NjQ4ZWM4... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14089?atlOrigin=eyJpIjoiYmM0Nj... ) HHH-14089 ( https://hibernate.atlassian.net/browse/HHH-14089?atlOrigin=eyJpIjoiYmM0Nj... ) Physical sequence information not fetched correctly when using pooled optimizer ( https://hibernate.atlassian.net/browse/HHH-14089?atlOrigin=eyJpIjoiYmM0Nj... ) Change By: Darko Pejchinov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ef73cb... ) When using a pooled sequence optimizer, although the sequences in the DB have correct increment size, the SequenceStyleGenerator throws a MappingException {quote}The increment size of the \[s_test \ ] sequence is set to \[1000 \ ] in the entity mapping while the associated database sequence increment size is \[1 \ ].{quote} The problem was root caused in the Oracle dialect (all dialects are affected), more specifically the problem is caused by the fact that no schema column name is returned by this method {{org.hibernate.tool.schema.extract.internal.SequenceInformationExtractorOracleDatabaseImpl.sequenceSchemaColumn()}} We have multiple schemas on the same database (that contain sequences that have same names, however different increment steps). Considering that the QualifiedSequenceName _QualifiedSequenceName_ in the sequence information list returned by the {{org.hibernate.tool.schema.extract.internal.SequenceInformationExtractorLegacyImpl.extractMetadata(ExtractionContext)}} is composed from catalog name, schema name and sequence name and the fact that both the schema name and the catalog name will be always null, hibernate has no way to identify the correct sequence for the list of fetched sequences (if multiple schemas contain the same sequence name - as in our case). ( https://hibernate.atlassian.net/browse/HHH-14089#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14089#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#100130- sha1:d095cd6 )

3 years, 10 months

1
0
0 / 0

[JIRA] (HHH-14089) Physical sequence information not fetched correctly when using pooled optimizer

by Darko Pejchinov (JIRA)

Darko Pejchinov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ef73cb... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYzJhMzFkZDE4... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14089?atlOrigin=eyJpIjoiYzJhMz... ) HHH-14089 ( https://hibernate.atlassian.net/browse/HHH-14089?atlOrigin=eyJpIjoiYzJhMz... ) Physical sequence information not fetched correctly when using pooled optimizer ( https://hibernate.atlassian.net/browse/HHH-14089?atlOrigin=eyJpIjoiYzJhMz... ) Issue Type: Bug Affects Versions: 5.4.18 Assignee: Unassigned Created: 27/Jun/2020 08:36 AM Environment: Oracle 12c DB, Apache Tomcat 9, Java 8 All DB sequences set to use increment step of 1000 Labels: Oracle dialect hibernate sequence Priority: Major Reporter: Darko Pejchinov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5ef73cb... ) When using a pooled sequence optimizer, although the sequences in the DB have correct increment size, the SequenceStyleGenerator throws a MappingException > > > > The increment size of the [s_test] sequence is set to [1000] in the entity > mapping while the associated database sequence increment size is [1]. > > The problem was root caused in the Oracle dialect (all dialects are affected), more specifically the problem is caused by the fact that no schema column name is returned by this method org.hibernate.tool.schema.extract.internal.SequenceInformationExtractorOracleDatabaseImpl.sequenceSchemaColumn() We have multiple schemas on the same database (that contain sequences that have same names, however different increment steps). Considering that the QualifiedSequenceName in the sequence information list returned by the org.hibernate.tool.schema.extract.internal.SequenceInformationExtractorLegacyImpl.extractMetadata(ExtractionContext) is composed from catalog name, schema name and sequence name and the fact that both the schema name and the catalog name will be always null, hibernate has no way to identify the correct sequence for the list of fetched sequences (if multiple schemas contain the same sequence name - as in our case). ( https://hibernate.atlassian.net/browse/HHH-14089#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14089#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#100130- sha1:d095cd6 )

3 years, 10 months

1
0
0 / 0

[JIRA] (HHH-6143) ElementCollection in Embeddable in Entity is ignored on merge

by Jan-Willem Gmelig Meyling (JIRA)

Jan-Willem Gmelig Meyling ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-6143 ( https://hibernate.atlassian.net/browse/HHH-6143?atlOrigin=eyJpIjoiYWI5ZDR... ) Re: ElementCollection in Embeddable in Entity is ignored on merge ( https://hibernate.atlassian.net/browse/HHH-6143?atlOrigin=eyJpIjoiYWI5ZDR... ) Probably more related to https://hibernate.atlassian.net/browse/HHH-5187 instead ( https://hibernate.atlassian.net/browse/HHH-6143#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-6143#add-comment?atlOrigin=eyJ... ) 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#100130- sha1:d095cd6 )

3 years, 10 months

1
0
0 / 0

[JIRA] (HHH-6143) ElementCollection in Embeddable in Entity is ignored on merge

by Jan-Willem Gmelig Meyling (JIRA)

Jan-Willem Gmelig Meyling ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-6143 ( https://hibernate.atlassian.net/browse/HHH-6143?atlOrigin=eyJpIjoiYWEyZWN... ) Re: ElementCollection in Embeddable in Entity is ignored on merge ( https://hibernate.atlassian.net/browse/HHH-6143?atlOrigin=eyJpIjoiYWEyZWN... ) I am not sure if this is truly a duplicate of HHH-3218 ( https://hibernate.atlassian.net/browse/HHH-3218 ) Closed. This issue describes an ElementCollection that is declared inside an Embeddable, the other issue mentions an ElementCollection of Embeddable values. I can reproduce the issue in Hibernate 5.4.x ( https://hibernate.atlassian.net/browse/HHH-6143#add-comment?atlOrigin=eyJ... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-6143#add-comment?atlOrigin=eyJ... ) 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#100130- sha1:d095cd6 )

3 years, 10 months

1
0
0 / 0

[JIRA] (HHH-14088) Schema validation fails with same name sequences in different schemas

by Alex CD (JIRA)

Alex CD ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiMjEwZTlmMmZl... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-14088?atlOrigin=eyJpIjoiMjEwZT... ) HHH-14088 ( https://hibernate.atlassian.net/browse/HHH-14088?atlOrigin=eyJpIjoiMjEwZT... ) Schema validation fails with same name sequences in different schemas ( https://hibernate.atlassian.net/browse/HHH-14088?atlOrigin=eyJpIjoiMjEwZT... ) Change By: Alex CD ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Using multiple schemas with same name sequences but different parameters. I use a default schema name, but the sequence information extractor retrieves all sequences and database information is initialized with sequences devoid of schema name in the order received from the extractor. So if the result is a sequence from default schema followed by the same sequence from another schema, it will be overwritten with invalid information from another schema. Extractor uses [select * from information_schema.sequences|https://github.com/hibernate/hibernate-orm/b...] to get all sequences disregarding any default schema configuration. Then, DatabaseInformationImpl _DatabaseInformationImpl. java java_ populates sequenceInformationMap _sequenceInformationMap_ in order received from executing the above sql, removing schema qualifier and overwriting without any check. [source|https://github.com/hibernate/hibernate-orm/blob/604b594226355dc789...] ( https://hibernate.atlassian.net/browse/HHH-14088#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14088#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#100130- sha1:d095cd6 )

3 years, 10 months

1
0
0 / 0

[JIRA] (HHH-14088) Schema validation fails with same name sequences in different schemas

by Alex CD (JIRA)

Alex CD ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-14088 ( https://hibernate.atlassian.net/browse/HHH-14088?atlOrigin=eyJpIjoiNmZmMj... ) Re: Schema validation fails with same name sequences in different schemas ( https://hibernate.atlassian.net/browse/HHH-14088?atlOrigin=eyJpIjoiNmZmMj... ) Should database metadata contain all sequences from all schemas? ExtractedDatabaseMetaData.getSequenceInformationList() contains all sequences and has one usage ( https://github.com/hibernate/hibernate-orm/blob/604b594226355dc789586c40f... ) where it filters the required schema (valid). This may produce bugs in the futures if it is used in other locations without filtering the required schema. ( https://hibernate.atlassian.net/browse/HHH-14088#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-14088#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#100130- sha1:d095cd6 )

3 years, 10 months

1
0
0 / 0

[JIRA] (HHH-14088) Schema validation fails with same name sequences in different schemas

by Alex CD (JIRA)

3 years, 10 months

1
0
0 / 0

[JIRA] (HHH-14088) Schema validation fails with same name sequences in different schemas

by Alex CD (JIRA)

3 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2020