November 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6855) SequenceStyleGenerator should force use of TableStructure when the optimizer is PooledLo

by Oskar Berggren (JIRA)

SequenceStyleGenerator should force use of TableStructure when the optimizer is PooledLo ---------------------------------------------------------------------------------------- Key: HHH-6855 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6855 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.CR6, 3.6.8 Reporter: Oskar Berggren The SequenceStyleGenerator's configure() method contains the following snippet: if ( dialect.supportsSequences() && !forceTableUse ) { if ( OptimizerFactory.POOL.equals( optimizationStrategy ) && !dialect.supportsPooledSequences() ) { forceTableUse = true; LOG.forcingTableUse(); } } Since "supportsPooledSequences" is about initial value and increment size, it seems tables should be forced also for the PooledLo optimizer. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-6840) to_char function with hsqldb doesn't work

by Roozbeh Maadani (JIRA)

to_char function with hsqldb doesn't work ----------------------------------------- Key: HHH-6840 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6840 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.6.8 Environment: Hibernate 3.6.8.Final and HSQLDB 2.2.4 Reporter: Roozbeh Maadani Priority: Minor Hi, We are developing a project which uses hibernate 3.6.8.final , Oracle 10g database in production and a in-memory Hsqldb for unittests. In our hql queries, we use "to_char" function which should work both for Oracle 10g and Hsqldb version 2.2 and above. There is no problem in production (Oracle10gDialect) but when we run the tests (for tests we use HSQLDialect ) we get the following mystic error: org.hsqldb.HsqlException: user lacks privilege or object not found: TO_CHAR And it is possible to see in the logs that HSQLDialect doesn't generate correct sql. After tracing the code I found out that HSQLDialect doesn't register "to_char" function for hsqldb 2.2.x. The following code solved the problem: public class MyHSQLDialect extends HSQLDialect { public MyHSQLDialect() { super(); registerFunction( "to_char", new StandardSQLFunction( "to_char" ) ); } } I suppose it is possible to move this code to the HSQLDialect constructor and solve this issue. Regards, Roozbeh Maadani -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5257) @JoinTable results in redundant join in the generated SQL

by Sharath Reddy (JIRA)

@JoinTable results in redundant join in the generated SQL --------------------------------------------------------- Key: HHH-5257 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5257 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2 Reporter: Sharath Reddy Priority: Minor Fix For: 3.6 Attachments: testcase.zip An Account can have several Clients: @Entity @Table(name = "CLIENT") public class Client implements Serializable { private String street; private String code; private String city; @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private int id; @ManyToOne @JoinTable(name = "CLIENT_ACCOUNT", joinColumns = {@JoinColumn(name = "FK_CLIENT", referencedColumnName = "ID")}, inverseJoinColumns = {@JoinColumn(name = "FK_ACCOUNT", referencedColumnName = "ID")}) private Account account; ..... } @Entity @Table(name = "ACCOUNT") public class Account implements Serializable { @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private int id; private String number; private double balance; @OneToMany (fetch = FetchType.EAGER, mappedBy="account") private Set<Client> holders; ... } When we load the Account entity: Account a1 = (Account) session.load(Account.class, accountId); We see that there is a redundant join at the end - from the CLIENT table to the CLIENT_ACCOUNT table: select account0_.id as id2_1_, account0_.balance as balance2_1_, account0_.number as number2_1_, holders1_.FK_ACCOUNT as FK1_2_3_, client2_.id as FK2_3_, client2_.id as id0_0_, client2_.city as city0_0_, client2_.code as code0_0_, client2_.street as street0_0_, client2_1_.FK_ACCOUNT as FK1_1_0_ from ACCOUNT account0_ left outer join CLIENT_ACCOUNT holders1_ on account0_.id=holders1_.FK_ACCOUNT left outer join CLIENT client2_ on holders1_.FK_CLIENT=client2_.id left outer join CLIENT_ACCOUNT client2_1_ on client2_.id=client2_1_.FK_CLIENT where account0_.id=? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

5
22
0 / 0

[Hibernate-JIRA] Created: (HHH-2511) generated="insert/always" ignored for property in composite-element?

by James Garrison (JIRA)

generated="insert/always" ignored for property in composite-element? -------------------------------------------------------------------- Key: HHH-2511 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2511 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.2 Environment: Hibernate 3.2.2, Windows XP SP2, Oracle 9i Reporter: James Garrison Priority: Minor I have a composite-element (in an idbag) that has a db-generated timestamp property. I have defined the property with update="false" insert="false" generated="insert", but Hibernate is trying to insert a null value when saving a transient object. See below, the "createTs" property (column=CREATE_TS) in the "comments" composite-element. DDL: create table CR_COMMENT ( COMMENT_ID integer not null, REQ_ID integer not null, CREATE_TS timestamp default sysdate not null, SECTION_ID char(1) not null, USER_ID varchar2(20) not null, TEXT varchar2(4000) not null, primary key(COMMENT_ID), foreign key(REQ_ID) references CR_REQUEST (REQ_ID) on delete cascade ); Mapping: <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping package="com.wholefoods.ittoolkit.ws.ccf"> <class name="Request" table="CR_REQUEST"> <id name="reqId" column="REQ_ID" type="long"> <generator class="sequence"> <param name="sequence">CR_REQUEST_ID</param> </generator> </id> [snip] <idbag name="comments" table="CR_COMMENT"> <collection-id type="long" column="COMMENT_ID"> <generator class="sequence"> <param name="sequence">CR_COMMENT_ID</param> </generator> </collection-id> <key column="REQ_ID" /> <composite-element class="Comment"> <property name="createTs" column="CREATE_TS" type="calendar" access="field" update="false" insert="false" generated="insert" /> <property name="sectionId" column="SECTION_ID" /> <property name="userId" column="USER_ID" /> <property name="text" column="TEXT"/> </composite-element> </idbag> </class> </hibernate-mapping> Log Output: Hibernate: /* insert collection row com.wholefoods.ittoolkit.ws.ccf.Request.comments */ insert into ITTOOLKIT.CR_COMMENT (REQ_ID, COMMENT_ID, CREATE_TS, SECTION_ID, USER_ID, TEXT) values (?, ?, ?, ?, ?, ?) 10:15:01,659 DEBUG org.hibernate.jdbc.AbstractBatcher:476 - preparing statement 10:15:01,675 DEBUG org.hibernate.type.LongType:133 - binding '47' to parameter: 1 10:15:01,675 DEBUG org.hibernate.type.LongType:133 - binding '7' to parameter: 2 10:15:01,675 DEBUG org.hibernate.type.CalendarType:126 - binding null to parameter: 3 10:15:01,675 DEBUG org.hibernate.type.StringType:133 - binding 'A' to parameter: 4 10:15:01,690 DEBUG org.hibernate.type.StringType:133 - binding 'garrisoj' to parameter: 5 10:15:01,690 DEBUG org.hibernate.type.StringType:133 - binding 'This is a test comment' to parameter: 6 10:15:01,690 DEBUG org.hibernate.persister.collection.AbstractCollectionPersister:1172 - done inserting collection: 1 rows inserted 10:15:01,690 DEBUG org.hibernate.jdbc.AbstractBatcher:44 - Executing batch size: 1 10:15:01,737 DEBUG org.hibernate.jdbc.AbstractBatcher:366 - about to close PreparedStatement (open PreparedStatements: 1, globally: 1) 10:15:01,737 DEBUG org.hibernate.jdbc.AbstractBatcher:525 - closing statement 10:15:01,768 DEBUG org.hibernate.util.JDBCExceptionReporter:69 - Could not execute JDBC batch update [/* insert collection row com.wholefoods.ittoolkit.ws.ccf.Request.comments */ insert into ITTOOLKIT.CR_COMMENT (REQ_ID, COMMENT_ID, CREATE_TS, SECTION_ID, USER_ID, TEXT) values (?, ?, ?, ?, ?, ?)] java.sql.BatchUpdateException: ORA-01400: cannot insert NULL into ("ITTOOLKIT"."CR_COMMENT"."CREATE_TS") -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

6
11
0 / 0

[Hibernate-JIRA] Created: (HHH-6063) The fix for HHH-5126 breaks array constructor in PostgreSQL

by Jon Vincent (JIRA)

The fix for HHH-5126 breaks array constructor in PostgreSQL ----------------------------------------------------------- Key: HHH-6063 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6063 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.Alpha1, 3.6.2, 3.6.1 Environment: PostgreSQL, any version Reporter: Jon Vincent The fix for HHH-5126 supports this JPA2-compliant IN query: {{{ SELECT * FROM my_table WHERE id IN :collection }}} Before HHH-5126 was fixed, Hibernate required the developer to surround collection-valued parameters with parentheses: {{{ SELECT * FROM my_table WHERE id IN (:collection) }}} The implemented fix was simply to output parentheses in the generated SQL. Unfortunately, this breaks _other_ uses of collection-values parameters, such as for arrays in PostgreSQL: {{{ CREATE TABLE my_table (some_array INTEGER[]); INSERT INTO my_table (some_array) VALUES (ARRAY[:collection]); }}} Is there a way to turn off the fix for HHH-5126? For us, at least, the old code was more flexible and allowed access to important database features. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3820) Criterion should implement equals and hashCode

by Craig (JIRA)

Criterion should implement equals and hashCode ---------------------------------------------- Key: HHH-3820 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3820 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.6 Reporter: Craig .equals() doesn't work as expected for Criterion and its subclasses. For example: assertEquals(Restrictions.isEmpty("parents"),Restrictions.isEmpty("parents")); fails, when clearly, it should work. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2455) "Could not close a JDBC result set" output very often

by Dirk Feufel (JIRA)

"Could not close a JDBC result set" output very often ----------------------------------------------------- Key: HHH-2455 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2455 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.2 Reporter: Dirk Feufel Priority: Minor If you call this type of code (like the DbTimestampType class does), the AbstractBatcher outputs a warning "Could not close a JDBC result set". The problem should be that closing the prepared statement internally also closes the associated result sets and the AbstractBatcher still has a reference to this result set. One possible solution might be to provide an additional method public void closeStatement(PreparedStatement ps, ResultSet rs); (as already present for closeQueryStatement) in the AbstractBatcher allowing to close both in the right order. PreparedStatement ps = null; try { ps = session.getBatcher().prepareStatement( timestampSelectString ); ResultSet rs = session.getBatcher().getResultSet( ps ); .... } finally { if ( ps != null ) { session.getBatcher().closeStatement( ps ); } } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
17
0 / 0

[Hibernate-JIRA] Created: (HHH-6809) FooBarTest.testFindByCriteria() fails on SQL Server due to mixed expectations for Criteria.setMaxResults(0)

by John Verhaeg (JIRA)

FooBarTest.testFindByCriteria() fails on SQL Server due to mixed expectations for Criteria.setMaxResults(0) ----------------------------------------------------------------------------------------------------------- Key: HHH-6809 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6809 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 4.0.0.CR5 Environment: MS SQL Server Reporter: John Verhaeg Fix For: 4.0.0.next Looks like some dialects treat 0 as meaning no limit and others as literally zero rows. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HHH-6812) HQL query for map value leads to incorrect joins in SQL

by Neukomm (JIRA)

HQL query for map value leads to incorrect joins in SQL ------------------------------------------------------- Key: HHH-6812 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6812 Project: Hibernate Core Issue Type: Bug Components: query-hql, query-sql Affects Versions: 3.6.7 Environment: Oracle Java 1.6.0_29, Hibernate 3.6.7-Final, Hsqldb 2.2.5 Reporter: Neukomm Attachments: map_query_test.zip Whenever an expression like 'where p.map['key'] = :val' is used in HQL, the join between the entity table and the map value table is not done correctly. This leads to missing results. The attached test case uses HQL like this: from MapQueryEntity p where p.name = 'B' or p.map['key'] = 'value' the corresponding sql looks like this: select mapqueryen0_.id as id0_, mapqueryen0_.name as name0_ from MapQueryEntity mapqueryen0_ cross join MapQueryEntity_map map1_ where mapqueryen0_.id=map1_.ident and map1_.mkey = 'key' and ( mapqueryen0_.name='B' or map1_.mvalue='value' ) This leads to all entities that don't have a map entry for key 'key' not to be in the result, even if they have name 'B'. SQL that would return the correct rows (at least on hsqldb) could e.g. look like this: select mapqueryen0_.id as id0_, mapqueryen0_.name as name0_ from MapQueryEntity mapqueryen0_ left outer join MapQueryEntity_map map1_ on mapqueryen0_.id=map1_.ident where mapqueryen0_.name='B' or (map1_.mkey = 'key' and map1_.mvalue='value') Looks like org.hibernate.hql.ast.tree.IndexNode (which seems to be responsible for the hql/sql translation if '[]' is used) doesn't work correctly for this case. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HV-482) Weblogic ConstrantDeclationException HVbeta2

by Tim Canavan (JIRA)

Weblogic ConstrantDeclationException HVbeta2 -------------------------------------------- Key: HV-482 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-482 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.2.0.Beta2 Environment: Weblogic 10.3 Reporter: Tim Canavan After upgrading to HV beta2 and changing all our validations to be at the interface level we get the constraint declaration exception Caused by: javax.validation.ConstraintDeclarationException: Only the root method of an overridden method in an inheritance hierarchy may be annotated with parameter constraints. The following method itself has no parameter constraints but it is not defined on a sub-type of class Under OpenEJB which our unit tests use everything works fine. Is there any code that HV could use that would allow it to understand these proxies or would an option be available to turn the check off. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 3 months

4
23
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 November 2011