July 2023 - hibernate-issues - Jboss List Archives

[JIRA] (HHH-16997) Embedded components in HibernateProxy are not initilized when entity has reference to another entity of the same type

by Andrea Boriero (JIRA)

Andrea Boriero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16997 ( https://hibernate.atlassian.net/browse/HHH-16997?atlOrigin=eyJpIjoiZTcwN2... ) Re: Embedded components in HibernateProxy are not initilized when entity has reference to another entity of the same type ( https://hibernate.atlassian.net/browse/HHH-16997?atlOrigin=eyJpIjoiZTcwN2... ) Hi Bartlomiej Niemiec ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5cdd0b2... ) , have you read https://github.com/hibernate/hibernate-orm/blob/6.0/migration-guide.adoc#... ? Does the suggestion fix your issue? ( https://hibernate.atlassian.net/browse/HHH-16997#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16997#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#100233- sha1:62cfdef )

2 years, 4 months

1
0
0 / 0

[JIRA] (HHH-16998) Schema Validation fails.

by Ádám Simon (JIRA)

Ádám Simon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5d9c852... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYmQ0ZTFlMmQz... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16998?atlOrigin=eyJpIjoiYmQ0ZT... ) HHH-16998 ( https://hibernate.atlassian.net/browse/HHH-16998?atlOrigin=eyJpIjoiYmQ0ZT... ) Schema Validation fails. ( https://hibernate.atlassian.net/browse/HHH-16998?atlOrigin=eyJpIjoiYmQ0ZT... ) Change By: Ádám Simon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5d9c852... ) In our project we are using spring boot’s built in hibernate dependencies with Oracle DB. We are now updating spring boot 2.7 to 3.0. One of our test is containing schema validation with hibernate. There is an issue currently when it wants to validate a sequence that is not existing. I put the breakpoint in the AbstractSchemaValidator:194 and on the failing sequence (on step back) AbstractSchemaValidator:112 i get the following: (Sequence.contributor=”orm”). Looks like the orm made this sequence naming is: Identifier.key=a_table_name_SEQ, where a_table_name is an existing table, but this seq is non existent in the db. It lists (saw them in debugger->namespace->sequences) all the sequences correctly except one called “hibernate_sequence” (The exact name in our db. The other name (a_table_name) are made up to not be project specific) I’m not sure though if it is trying to name this hibernate_sequence to something else or is it a completely new one. I’m wondering if there is a setting to not let the validator validate orm created sequences. ( https://hibernate.atlassian.net/browse/HHH-16998#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16998#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#100233- sha1:62cfdef )

2 years, 4 months

1
0
0 / 0

[JIRA] (HHH-16998) Schema Validation fails.

by Ádám Simon (JIRA)

Ádám Simon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5d9c852... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiYjYwOWFmZTM1... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16998?atlOrigin=eyJpIjoiYjYwOW... ) HHH-16998 ( https://hibernate.atlassian.net/browse/HHH-16998?atlOrigin=eyJpIjoiYjYwOW... ) Schema Validation fails. ( https://hibernate.atlassian.net/browse/HHH-16998?atlOrigin=eyJpIjoiYjYwOW... ) Change By: Ádám Simon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5d9c852... ) In our project we are using spring boot’s built in hibernate dependencies. We are now updating spring boot 2.7 to 3.0. One of our test is containing schema validation with hibernate. There is an issue currently when it wants to validate a sequence that is not existing. I put the breakpoint in the AbstractSchemaValidator:194 and on the failing sequence (on step back) AbstractSchemaValidator:112 i get the following: (Sequence.contributor=”orm”). Looks like the orm made this sequence naming is: Identifier.key= A_TABLE_NAME_SEQ a_table_name_SEQ , where A_TABLE_NAME a_table_name is an existing table, but this seq is non existent in the db. It lists (saw them in debugger->namespace->sequences) all the sequences correctly except one called “hibernate_sequence” (The exact name in our db. The other names name (a_table_name) are made up to not be project specific) I’m not sure though if it is trying to name this hibernate_sequence to something else or is it a completely new one. I’m wondering if there is a setting to not let the validator validate orm created sequences. ( https://hibernate.atlassian.net/browse/HHH-16998#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16998#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#100233- sha1:62cfdef )

2 years, 4 months

1
0
0 / 0

[JIRA] (HHH-16991) EnhancedUserType cannot be used when defining relations

by Andrea Boriero (JIRA)

2 years, 4 months

1
0
0 / 0

[JIRA] (HHH-16998) Schema Validation fails.

by Ádám Simon (JIRA)

Ádám Simon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5d9c852... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZDFlNmEyMmQ2... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16998?atlOrigin=eyJpIjoiZDFlNm... ) HHH-16998 ( https://hibernate.atlassian.net/browse/HHH-16998?atlOrigin=eyJpIjoiZDFlNm... ) Schema Validation fails. ( https://hibernate.atlassian.net/browse/HHH-16998?atlOrigin=eyJpIjoiZDFlNm... ) Change By: Ádám Simon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5d9c852... ) In our project we are using spring boot’s built in hibernate dependencies. We are now updating spring boot 2.7 to 3.0. One of our test is containing schema validation with hibernate. There is an issue currently when it wants to validate a sequence that is not existing. I put the breakpoint in the AbstractSchemaValidator:194 and on the failing sequence (on step back) AbstractSchemaValidator:112 i get the following: (Sequence.contributor=”orm”). Looks like the orm made this sequence naming is: Identifier.key=A_TABLE_NAME_SEQ, where A_TABLE_NAME is an existing table, but this seq is not non existent in the db. It lists all the sequences correctly except one called “hibernate_sequence” (The exact name in our db. The other names are made up to not be project specific) I’m not sure though if it is trying to name this hibernate_sequence to something else or is it a completely new one. I’m wondering if there is a setting to not let the validator validate orm created sequences. ( https://hibernate.atlassian.net/browse/HHH-16998#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16998#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#100233- sha1:62cfdef )

2 years, 4 months

1
0
0 / 0

[JIRA] (HHH-16998) Schema Validation fails.

by Ádám Simon (JIRA)

Ádám Simon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5d9c852... ) *updated* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNWQyMmY5MmU2... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16998?atlOrigin=eyJpIjoiNWQyMm... ) HHH-16998 ( https://hibernate.atlassian.net/browse/HHH-16998?atlOrigin=eyJpIjoiNWQyMm... ) Schema Validation fails. ( https://hibernate.atlassian.net/browse/HHH-16998?atlOrigin=eyJpIjoiNWQyMm... ) Change By: Ádám Simon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5d9c852... ) In our project we are using spring boot’s built in hibernate dependencies. We are now updating spring boot 2.7 to 3.0. On One of our test is containing schema validation with hibernate. There is an issue currently when it wants to validate a sequence that is not existing. I put the breakpoint in the AbstractSchemaValidator:194 and on the failing sequence (on step back) AbstractSchemaValidator:112 i get the following: (Sequence.contributor=”orm”). Looks like the orm made this sequence naming is: Identifier.key=A_TABLE_NAME_SEQ, where A_TABLE_NAME is an existing table, but this seq is not. It lists all the sequences correctly except one called “hibernate_sequence” (The exact name in our db. The other names are made up to not be project specific) I’m not sure though if it is trying to name this hibernate_sequence to something else or is it a completely new one. I’m wondering if there is a setting to not let the validator validate orm created sequences. ( https://hibernate.atlassian.net/browse/HHH-16998#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16998#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#100233- sha1:62cfdef )

2 years, 4 months

1
0
0 / 0

[JIRA] (HHH-16998) Schema Validation fails.

by Ádám Simon (JIRA)

Ádám Simon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5d9c852... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiZGQ4YTcyZmIx... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16998?atlOrigin=eyJpIjoiZGQ4YT... ) HHH-16998 ( https://hibernate.atlassian.net/browse/HHH-16998?atlOrigin=eyJpIjoiZGQ4YT... ) Schema Validation fails. ( https://hibernate.atlassian.net/browse/HHH-16998?atlOrigin=eyJpIjoiZGQ4YT... ) Issue Type: Bug Affects Versions: 6.1.7 Assignee: Unassigned Components: hibernate-core Created: 26/Jul/2023 05:44 AM Priority: Major Reporter: Ádám Simon ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=5d9c852... ) In our project we are using spring boot’s built in hibernate dependencies. We are now updating spring boot 2.7 to 3.0. On of our test is containing schema validation with hibernate. There is an issue currently when it wants to validate a sequence that is not existing. I put the breakpoint in the AbstractSchemaValidator:194 and on the failing sequence (on step back) AbstractSchemaValidator:112 i get the following: (Sequence.contributor=”orm”). Looks like the orm made this sequence naming is: Identifier.key=A_TABLE_NAME_SEQ, where A_TABLE_NAME is an existing table, but this seq is not. It lists all the sequences correctly except one called “hibernate_sequence” (The exact name in our db. The other names are made up to not be project specific) I’m not sure though if it is trying to name this hibernate_sequence to something else or is it a completely new one. I’m wondering if there is a setting to not let the validator validate orm created sequences. ( https://hibernate.atlassian.net/browse/HHH-16998#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16998#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#100233- sha1:62cfdef )

2 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-4906) Test against latest Elasticsearch 7.17.12

by Marko Bekhta (JIRA)

2 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-4905) Add compatibility with OpenSearch 2.9.0

by Marko Bekhta (JIRA)

2 years, 4 months

1
0
0 / 0

[JIRA] (HSEARCH-4904) Upgrade to Elasticsearch client 8.9.0 and test against Elasticsearch 8.9.0

by Marko Bekhta (JIRA)

2 years, 4 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2023