October 2022 - hibernate-issues - Jboss List Archives

[JIRA] (HSEARCH-4726) Upgrade to AWS SDK 2.18

by Yoann Rodière (JIRA)

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15609) get schema incorrectly in Hibernate 6.1.4

by Ngo Manh Cuong (JIRA)

Ngo Manh Cuong ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=60f4170... ) *commented* on HHH-15609 ( https://hibernate.atlassian.net/browse/HHH-15609?atlOrigin=eyJpIjoiMzlkMj... ) Re: get schema incorrectly in Hibernate 6.1.4 ( https://hibernate.atlassian.net/browse/HHH-15609?atlOrigin=eyJpIjoiMzlkMj... ) Now I can resolve problem It’s becaue previous Hibernate able to work well without revinfo_seq When I upgrade to Hibernate 6, I try to use hbm2ddl to create revinfo_seq automatically, but it is generated in public schema When I try to create it manually, and set high value: select setval('tests.revinfo_seq', (SELECT MAX(rev) + 100 FROM tests.revinfo)); now it works well Thanks ! ( https://hibernate.atlassian.net/browse/HHH-15609#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15609#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#100209- sha1:392b984 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-4725) @ObjectProjection(includeDepth = ...) or @ObjectProjection(includePaths = ...) to apply projection constructors up to a certain depth

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiMzE0ZDZh... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-4725?atlOrigin=eyJpIjoiMzE... ) HSEARCH-4725 ( https://hibernate.atlassian.net/browse/HSEARCH-4725?atlOrigin=eyJpIjoiMzE... ) @ObjectProjection(includeDepth = ...) or @ObjectProjection(includePaths = ...) to apply projection constructors up to a certain depth ( https://hibernate.atlassian.net/browse/HSEARCH-4725?atlOrigin=eyJpIjoiMzE... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Pre-requisite: [https://hibernate.atlassian.net/browse/HSEARCH-4574|https://hibernate.atl...] Useful in complicated schemas, to break cycles in particular. E.g. the following schema wouldn’t work unless we support {{@ObjectProjection(includeDepth = ...)}} {noformat}@ProjectionConstructor public record WishList( UUID id, String title, Boolean restricted, @ObjectProjection(includeDepth = 1) List<Product> products ) {} {noformat} {noformat}@ProjectionConstructor public record Product( UUID id, String title, String keywords, String description, Integer rating, LocalDate dateAdded, LocalDate dateModified, @ObjectProjection(includeDepth = 1) WishList wishList ) { } {noformat} {{includePaths}} would be similarly useful: {noformat}@ProjectionConstructor public record Product( UUID id, String title, String keywords, String description, Integer rating, LocalDate dateAdded, LocalDate dateModified, @ObjectProjection(includePaths = {" id", title", "products. id", products. title"}) WishList wishList ) { } {noformat} ( https://hibernate.atlassian.net/browse/HSEARCH-4725#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4725#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#100209- sha1:392b984 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-4725) @ObjectProjection(includeDepth = ...) or @ObjectProjection(includePaths = ...) to apply projection constructors up to a certain depth

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *updated* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiOWIyYTVh... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-4725?atlOrigin=eyJpIjoiOWI... ) HSEARCH-4725 ( https://hibernate.atlassian.net/browse/HSEARCH-4725?atlOrigin=eyJpIjoiOWI... ) @ObjectProjection(includeDepth = ...) or @ObjectProjection(includePaths = ...) to apply projection constructors up to a certain depth ( https://hibernate.atlassian.net/browse/HSEARCH-4725?atlOrigin=eyJpIjoiOWI... ) Change By: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Pre-requisite: [https://hibernate.atlassian.net/browse/HSEARCH-4574|https://hibernate.atl...] Useful in complicated schemas, to break cycles in particular. E.g. the following schema wouldn’t work unless we support {{@ObjectProjection(includeDepth = ...)}} {noformat}@ProjectionConstructor public record WishList( UUID id, String title, Boolean restricted, @ObjectProjection(includeDepth = 1) List<Product> products ) {} {noformat} {noformat}@ProjectionConstructor public record Product( UUID id, String title, String keywords, String description, Integer rating, LocalDate dateAdded, LocalDate dateModified, @ObjectProjection(includeDepth = 1) WishList wishList ) { } {noformat} {{includePaths}} would be similarly useful: {noformat}@ProjectionConstructor public record Product( UUID id, String title, String keywords, String description, Integer rating, LocalDate dateAdded, LocalDate dateModified, @ObjectProjection(includePaths = {"title", "products.title"}) WishList wishList ) { } {noformat} ( https://hibernate.atlassian.net/browse/HSEARCH-4725#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4725#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#100209- sha1:392b984 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15228) "round()" function in H2Dialect always returns Double as return type irrespective of argument.

by Søren Jepsen (JIRA)

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15612) Bad SQL generation when using entity graph with ON clause on query

by Christian Beikov (JIRA)

Christian Beikov ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15612 ( https://hibernate.atlassian.net/browse/HHH-15612?atlOrigin=eyJpIjoiOTAyNm... ) Re: Bad SQL generation when using entity graph with ON clause on query ( https://hibernate.atlassian.net/browse/HHH-15612?atlOrigin=eyJpIjoiOTAyNm... ) You will have to use Hibernate filters or a join fetch in HQL if you want to filter elements of fetched associations. ( https://hibernate.atlassian.net/browse/HHH-15612#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15612#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#100209- sha1:392b984 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15612) Bad SQL generation when using entity graph with ON clause on query

by Wilber Saca (JIRA)

Wilber Saca ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-15612 ( https://hibernate.atlassian.net/browse/HHH-15612?atlOrigin=eyJpIjoiMzU0Nz... ) Re: Bad SQL generation when using entity graph with ON clause on query ( https://hibernate.atlassian.net/browse/HHH-15612?atlOrigin=eyJpIjoiMzU0Nz... ) I’m not getting duplicate elements, my problem is the deleted elements are not filtered due to the new JOIN added by the entity graph. It’s worse if I add a combination of ORDER BY + DISTINCT to the same query, in that case I receive a database exception ORA-01791: not a SELECTed expression ( http://oraclequirks.blogspot.com/2009/04/ora-01791-not-selected-expressio... ) because the query JOIN is replaced by the entity graph JOIN in the SELECTed results and they are not used to declare the order in the original query. On internet there are solutions similar to mine https://stackoverflow.com/a/65703150/1432916 ( https://stackoverflow.com/a/65703150/1432916 ) , does this means with Hibernate 6 we can’t use LEFT JOIN + ON with entity graph to fetch data? I have used Blaze before and would be a good option, but now I’m trying to migrate a project to Jakarta 10 making as few changes as possible. ( https://hibernate.atlassian.net/browse/HHH-15612#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15612#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#100209- sha1:392b984 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HHH-15621) Clearify configuration of datasource based multitenancy

by Staffan Hörke (JIRA)

Staffan Hörke ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiOWFiNmQzYjQw... ) / Improvement ( https://hibernate.atlassian.net/browse/HHH-15621?atlOrigin=eyJpIjoiOWFiNm... ) HHH-15621 ( https://hibernate.atlassian.net/browse/HHH-15621?atlOrigin=eyJpIjoiOWFiNm... ) Clearify configuration of datasource based multitenancy ( https://hibernate.atlassian.net/browse/HHH-15621?atlOrigin=eyJpIjoiOWFiNm... ) Issue Type: Improvement Affects Versions: 6.1.4 Assignee: Unassigned Components: hibernate-core Created: 21/Oct/2022 09:08 AM Environment: Wildfly 27.0.0.Beta1 Priority: Minor Reporter: Staffan Hörke ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Hi, I have been using hibernate multitenency features with Hibernate 5 by specifying the following hibernate properties: <property name="hibernate.multiTenancy" value="DATABASE" /> <property name="hibernate.connection.datasource" value="java:jboss/datasources" /> <property name="hibernate.multi_tenant.datasource.identifier_for_any" value="myDefaultDatasource" /> <property name="hibernate.tenant_identifier_resolver" value="MyTenantIdentifierResolverImpl" /> Moving to Hibernate 6 this no longer worked instead an exception is thrown: Caused by: java.lang.ClassCastException: class org.jboss.as.naming.NamingContext cannot be cast to class javax.sql.DataSource (org.jboss.as.naming.NamingContext is in unnamed module of loader 'org.jboss.as.naming(a)27.0.0.Beta1' @3e7df9b1; javax.sql.DataSource is in module java.sql of loader 'platform') Adding the following property makes it work with Hibernate 6: <property name="hibernate.multi_tenant_connection_provider" value="org.hibernate.engine.jdbc.connections.spi.DataSourceBasedMultiTenantConnectionProviderImpl" /> But should the user have to do that? Looking in the user guide its says that: The MultiTenantConnectionProvider to use can be specified in a number of ways: * Use the hibernate.multi_tenant_connection_provider setting. It could name a MultiTenantConnectionProvider instance, a MultiTenantConnectionProvider implementation class reference or a MultiTenantConnectionProvider implementation class name. * Passed directly to the org.hibernate.boot.registry.StandardServiceRegistryBuilder. * If none of the above options match, but the settings do specify a hibernate.connection.datasource value, Hibernate will assume it should use the specific DataSourceBasedMultiTenantConnectionProviderImpl implementation which works on a number of pretty reasonable assumptions when running inside of an app server and using one javax.sql.DataSource per tenant. See its Javadocs ( https://docs.jboss.org/hibernate/orm/6.1/javadocs/org/hibernate/engine/jd... ) for more details. Number three looks like my case, but it doesn’t work. Looking at the code i can see that JdbcEnvironmentInitiator assumes only multitenency if hibernate.multi_tenant_connection_provider is set: private JdbcConnectionAccess buildJdbcConnectionAccess(Map<?,?> configValues, ServiceRegistryImplementor registry) { if ( !configValues.containsKey( AvailableSettings.MULTI_TENANT_CONNECTION_PROVIDER ) ) { ConnectionProvider connectionProvider = registry.getService( ConnectionProvider.class ); return new ConnectionProviderJdbcConnectionAccess( connectionProvider ); } else { final MultiTenantConnectionProvider multiTenantConnectionProvider = registry.getService( MultiTenantConnectionProvider.class ); return new MultiTenantConnectionProviderJdbcConnectionAccess( multiTenantConnectionProvider ); } } MultiTenantConnectionProviderInitiator has a case for dealing with this part but I can’t see that it ever will be reached: if ( !configurationValues.containsKey( AvailableSettings.MULTI_TENANT_CONNECTION_PROVIDER ) ) { // nothing to do , but given the separate hierarchies have to handle this here. return null ; } final Object configValue = configurationValues.get( AvailableSettings.MULTI_TENANT_CONNECTION_PROVIDER ); if ( configValue == null ) { // if they also specified the data source *name*, then lets assume they want // DataSourceBasedMultiTenantConnectionProviderImpl final Object dataSourceConfigValue = configurationValues.get( AvailableSettings.DATASOURCE ); if ( dataSourceConfigValue instanceof String ) { return new DataSourceBasedMultiTenantConnectionProviderImpl(); } return null ; } ( https://hibernate.atlassian.net/browse/HHH-15621#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15621#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#100209- sha1:392b984 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-4725) @ObjectProjection(includeDepth = ...) or @ObjectProjection(includePaths = ...) to apply projection constructors up to a certain depth

by Yoann Rodière (JIRA)

Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate Search ( https://hibernate.atlassian.net/browse/HSEARCH?atlOrigin=eyJpIjoiZTdlODlk... ) / Improvement ( https://hibernate.atlassian.net/browse/HSEARCH-4725?atlOrigin=eyJpIjoiZTd... ) HSEARCH-4725 ( https://hibernate.atlassian.net/browse/HSEARCH-4725?atlOrigin=eyJpIjoiZTd... ) @ObjectProjection(includeDepth = ...) or @ObjectProjection(includePaths = ...) to apply projection constructors up to a certain depth ( https://hibernate.atlassian.net/browse/HSEARCH-4725?atlOrigin=eyJpIjoiZTd... ) Issue Type: Improvement Assignee: Unassigned Components: mapper-pojo-base Created: 21/Oct/2022 08:27 AM Fix Versions: 6.2-backlog Priority: Major Reporter: Yoann Rodière ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) Pre-requisite: https://hibernate.atlassian.net/browse/HSEARCH-4574 ( https://hibernate.atlassian.net/browse/HSEARCH-4574 ) Useful in complicated schemas, to break cycles in particular. E.g. the following schema wouldn’t work unless we support @ObjectProjection(includeDepth = ...) @ProjectionConstructor public record WishList( UUID id, String title, Boolean restricted, @ObjectProjection(includeDepth = 1) List<Product> products ) {} @ProjectionConstructor public record Product( UUID id, String title, String keywords, String description, Integer rating, LocalDate dateAdded, LocalDate dateModified, @ObjectProjection(includeDepth = 1) WishList wishList ) { } ( https://hibernate.atlassian.net/browse/HSEARCH-4725#add-comment?atlOrigin... ) Add Comment ( https://hibernate.atlassian.net/browse/HSEARCH-4725#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#100209- sha1:392b984 )

2 years, 3 months

1
0
0 / 0

[JIRA] (HSEARCH-4700) Configurable behavior on full queues for indexing operations

by Automation for Jira (JIRA)

2 years, 3 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 October 2022