May 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5245) Introduce LobHelper

by Steve Ebersole (JIRA)

Introduce LobHelper ------------------- Key: HHH-5245 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5245 Project: Hibernate Core Issue Type: Improvement Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6 As the preferred way to interact with JDBCSupport as currently defined on org.hibernate.Hibernate (and deprecate those) -- 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

16 years

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5248) Introduce CompositeType interface (to replace AbstractComponentType interface)

by Steve Ebersole (JIRA)

Introduce CompositeType interface (to replace AbstractComponentType interface) ------------------------------------------------------------------------------ Key: HHH-5248 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5248 Project: Hibernate Core Issue Type: Improvement Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6 -- 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

16 years

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5200) Prepare to use H2 as the default testing datbase

by Steve Ebersole (JIRA)

Prepare to use H2 as the default testing datbase ------------------------------------------------ Key: HHH-5200 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5200 Project: Hibernate Core Issue Type: Task Components: core, testsuite Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6 Evaluate the current couple of errors against H2 to determine cause(s). -- 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

16 years

1
7
0 / 0

[Hibernate-JIRA] Created: (HHH-5069) Fix annotation documentation wrt setup

by Steve Ebersole (JIRA)

Fix annotation documentation wrt setup -------------------------------------- Key: HHH-5069 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5069 Project: Hibernate Core Issue Type: Bug Components: annotations, documentation Affects Versions: 3.5.0-Final Reporter: Steve Ebersole Fix For: 3.5.x http://in.relation.to/Bloggers/Hibernate350FinalRelease#comment15080 The annotation guide seems to document incorrectly the steps getting started in terms of copying jars from the distribution to the developer project. Specificially it appears to call call for copying: * hibernate-annotations.jar (part of hibernate3.jar) * lib/hibernate-comons-annotations.jar (part of hibernate3.jar) * lib/hibernate-jpa-2.0-api.jar (actually under jpa/, not lib/) -- 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

16 years

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5218) Provide a new "pooled value" based optimizer which interprets the database value as the low boundary instead of upper boundary

by Steve Ebersole (JIRA)

Provide a new "pooled value" based optimizer which interprets the database value as the low boundary instead of upper boundary ------------------------------------------------------------------------------------------------------------------------------ Key: HHH-5218 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5218 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.2.6 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.2, 3.6 Splitting up HHH-3608 into its individual tasks. This part deals with the assumption made in PooledOptimizer that the sequence value is the upper boundary of the current range of values. This is an assumption and the other assumption that the value is the lower boundary is just as valid, so provide for both by adding a new optimizer. The new optimizer class will be org.hibernate.id.enhanced.OptimizerFactory.PooledLoOptimizer and its short name will be "pooled-lo". The already existing one will remain the default, but I will add a config option to allow users to specify which to use per setup ('hibernate.id.prefer_pooling_lo_values'). -- 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

16 years

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5131) SchemaExport drop fails if constraint names change

by Strong Liu (JIRA)

SchemaExport drop fails if constraint names change -------------------------------------------------- Key: HHH-5131 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5131 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1, 3.3.2 Environment: PostgreSQL Reporter: Strong Liu Fix For: 3.3.x, 3.5.x for PostgreSQL dialect, it doesn't use cascade to drop tables, this may causes error when it drops the constraints. for example, there is a table A with a FK which name is "123456" but schemaUpdate uses a different FK name to drop it, then fails, then it tries to drop Table A, fails again :( HB-540 was reported a long ago, and Gavin added a comment "We can't apply this patch since older versions of Postgres don't support the cascade syntax." but I don't think it is still a problem( it was a comment added in 2003), as even the PostgreSQL 7.x support this syntax -- 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

16 years

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5032) Setting LockModeType.OPTIMISTIC_FORCE_INCREMENT defaults to only OPTIMISTIC

by Carlos Vara (JIRA)

Setting LockModeType.OPTIMISTIC_FORCE_INCREMENT defaults to only OPTIMISTIC --------------------------------------------------------------------------- Key: HHH-5032 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5032 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.0-CR-2 Environment: Hibernate Core 3.5.0-CR-2, Hibernate Validator 4.1 Snapshot, Spring 3.0.1, JPA2 Reporter: Carlos Vara Using EntityManager.lock(entity, LockModeType.OPTIMISTIC_FORCE_INCREMENT) doesn't change lock type, and version doesn't get updated on transaction commit. The following code: System.out.println("PRE lock mode: " + this.entityManager.getLockMode(an)); this.entityManager.lock(an, LockModeType.OPTIMISTIC_FORCE_INCREMENT); System.out.println("POST lock mode: " + this.entityManager.getLockMode(an)); Outputs: PRE lock mode: OPTIMISTIC POST lock mode: OPTIMISTIC Debugging AbstractLockUpgradeEventListener.upgradeLock, the reason is it doesn't upgrade it because previous lock mode is "READ" (whose level is 5), and OPTIMISTIC_FORCE_INCREMENT has level 4, so it doesn't trigger the update. I'm not sure about Hibernate's LockMode, but I think that OPTIMISTIC_FORCE_INCREMENT is a bit more restrictive than just OPTIMISTIC, so the locking type should be upgraded. -- 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

16 years

5
20
0 / 0

[Hibernate-JIRA] Created: (HHH-5208) Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first value of sequence is "2"

by Strong Liu (JIRA)

Oracle 11g R2 RAC - Test SequenceIdentityTest fails because first value of sequence is "2" ------------------------------------------------------------------------------------------ Key: HHH-5208 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5208 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1, 3.5.x Environment: Oracle 11g R2 (RAC) Reporter: Strong Liu Starting with Oracle 11g R2 (RAC), the behavior of the CREATE TABLE statement has changed, when creating a conventional table in a database created with the default options then the initial segment is not created until the first row is inserted into the table. see http://download.oracle.com/docs/cd/E11882_01/server.112/e10595/tables002.... for more details. We found a potential downside to this change : The sequences created as default ( start with 1 increment by 1) are not staring with '1′ when used in insert query script, Instead they are starting with 2 or 4, this can not be changed even explicitly tell Oracle that the first value is "1". In another words, when using Hibernate with Oracle 11g R2 (RAC), if the ID generator class is "sequence-identity", the first value is NOT 1. Two ways to work around this issue: 1. Using another ID generator class. 2. Disable deferred segment creation of Oracle by setting the initialization parameter DEFERRED_SEGMENT_CREATION to FALSE. The new clauses SEGMENT CREATION DEFERRED and SEGMENT CREATION IMMEDIATE are available for the CREATE TABLE statement. These clauses override the setting of the DEFERRED_SEGMENT_CREATION initialization parameter. -- 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

16 years

4
10
0 / 0

[Hibernate-JIRA] Created: (HHH-5210) Query Cache effective only after closing the session that created the cache

by Strong Liu (JIRA)

Query Cache effective only after closing the session that created the cache --------------------------------------------------------------------------- Key: HHH-5210 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5210 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1, 3.5.x Reporter: Strong Liu When using a query which is marked as cacheable, Hibernate caches both the query and the timestamp in the cache, but uses two different timestamps for that. When retrieving a query from the cache, it first compares the timestamp of the cached query with the timestamp of the current session (UpdateTimestampsCache.isUpToDate()): if ( lastUpdate.longValue() >= timestamp.longValue() ) { return false; } The problem is that the timestamp for the current session is always lower than cache's timestamp if the cache was created with the same session, causing the result of the method to be "false", discarding the cache results and hitting the database. It's not clear where the bug is, but it's worth looking at some considerations: 1) Why is it comparing the cache's timestamp with session's timestamp? The cache itself can expire the data via timeout and Hibernate should expire the data if any relevant table was changed (both are happening). Besides, I wasn't able to think of a single use case where the cached data could be considered "outdated" just because its timestamp is higher than the current session's timestamp (meaning that they are newer than the session). 2) The javadoc for the SessionImplementor.getTimestamp() says: "System time before the start of the transaction" So, someone consuming this method can assume that this timestamp is related to the transaction. If the timestamp was related to the transaction, then the cache's timestamp would never be higher than session's. Then, this comparison would make sense, to not return something which would never happen and is probably wrong. So, it's up to the developers to decide what's wrong: - JavaDoc + the logic to get a timestamp which is used when creating the query cache - getTimestamp() value + UpdateTimestampsCache.isUpToDate logic + other places relying in the wrong return value -- 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

16 years

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-5078) JPA criteria query numeric expressions produce wrong result (due to wrong bracketing)

by Christoph Gerkens (JIRA)

JPA criteria query numeric expressions produce wrong result (due to wrong bracketing) ------------------------------------------------------------------------------------- Key: HHH-5078 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5078 Project: Hibernate Core Issue Type: Bug Components: entity-manager, query-criteria Affects Versions: 3.5.0-Final Environment: Hibernate-Core 3.5.0-Final, all database platforms Reporter: Christoph Gerkens The combination of quot and diff results in wrong SQL code. E.g.: (2 - 1) / 2 should be evaluated to 0.5 not 1.5 ( which is 2 - (1 / 2). JUnit 4 Test: @Test public void testJpaCriteriaApiQuoteAndDiff() { CriteriaBuilder cb = em.getCriteriaBuilder(); CriteriaQuery<Number> query = cb.createQuery(Number.class); query.from(SystemUser.class); // entity type doesn't matter, but must contain at least one entry for this test case. query.select( // (2 - 1) / 2 cb.quot( cb.diff( cb.literal(BigDecimal.valueOf(2.0)), cb.literal(BigDecimal.valueOf(1.0))), BigDecimal.valueOf(2.0))).distinct(true); Number result = em.createQuery(query).getSingleResult(); assertEquals(0.5d, result.doubleValue(), 0.1d); // (2 - 1) / 2 = 0.5 } -- 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

16 years

4
11
0 / 0

[Hibernate-JIRA] Created: (HHH-5173) hql - average returns double but looses the decimal part

by Sébastien Peters (JIRA)

hql - average returns double but looses the decimal part -------------------------------------------------------- Key: HHH-5173 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5173 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.0-Final Environment: Database driver: hsqldb OS: Mac-Os Hibernate: 3.5.0-Final Reporter: Sébastien Peters HQL: select avg(r.rating) from Review r for the values 2,2,2,1,2 it should return 1.8 instead of 1.0 type of rating: integer -- 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

16 years

4
16
0 / 0

[Hibernate-JIRA] Created: (HHH-4966) Entity Manager bug with ParameterExpressionImpl

by jean-claude cote (JIRA)

Entity Manager bug with ParameterExpressionImpl ----------------------------------------------- Key: HHH-4966 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4966 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-CR-1 Reporter: jean-claude cote Emmanuel There seems to be a bug with the ParameterExpressionImpl class when rendering. If you create a criteria query using a ParameterExpression instance in multiple places in your query the rendering of this query will produce multiple pram0, param1, param2 for the same ParameterExpression instance. We fixed this bug by augmenting the RenderingContext interface with generateParameterName(Expression<?> exp). With this information the rendering context can give back the same jpaqlParameterName for the same ParameterExpression instance. All it has to do is do a lookup in its explicitParamtermapping map. Thanks Jean-Claude -- 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

16 years

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5217) Minimize double sequence value reads in PooledOptimizer

by Steve Ebersole (JIRA)

Minimize double sequence value reads in PooledOptimizer ------------------------------------------------------- Key: HHH-5217 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5217 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.2.6 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.2, 3.6 Splitting up HHH-3608 into its individual tasks. This part is about minimizing the double sequence value reads. Really the double read is only needed when we are initializing the optimizer *and* the first read gave us the initialValue (perhaps this should be anything less than the increment?). -- 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

16 years

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5178) Unit tests in org.hibernate.test.immutable fail on mssql and sybase due to keyword used for table and column name

by Gail Badner (JIRA)

Unit tests in org.hibernate.test.immutable fail on mssql and sybase due to keyword used for table and column name ----------------------------------------------------------------------------------------------------------------- Key: HHH-5178 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5178 Project: Hibernate Core Issue Type: Bug Components: testsuite Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.x, 3.6 Failing due to "plan" used for table and column name. -- 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

16 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5186) update db profiles id and jdbc properties' name to use dballocator

by Strong Liu (JIRA)

update db profiles id and jdbc properties' name to use dballocator ------------------------------------------------------------------ Key: HHH-5186 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5186 Project: Hibernate Core Issue Type: Task Components: build Reporter: Strong Liu Assignee: Strong Liu [dballocator|https://docspace.corp.redhat.com/docs/DOC-29725] uses different DB names with our profiles' id to use this in our hudson build, our profile id should be updated. for example, there is a DB profile with id "mssql2005", it will be changed to "mssql-2005". for full DB list, please refer to [https://svn.devel.redhat.com/repos/jboss-soa/trunk/qa/dballocator/resourc...] -- 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

16 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3377) this time its h2 : foncusion of DECIMAL and NUMERIC column types

by Jan Baumann (JIRA)

this time its h2 : foncusion of DECIMAL and NUMERIC column types ----------------------------------------------------------------- Key: HHH-3377 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3377 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: H2 1.0.72, Hibernate 3.2.6 Reporter: Jan Baumann Analogous to HHH-2582 when trying to persist a BigDecimal object, hibernate throws a org.hibernate.HibernateException stating "Wrong column type in [...]. Found: decimal, expected: numeric" I checked the H2Dialect.java file, and as had been described for the MySQLDialect.java the following line was present : registerColumnType(Types.NUMERIC, "numeric"); Since H2 doesn't have a numeric type I tried the solution found for HHH-2582 and changed the line mentioned above to registerColumnType( Types.NUMERIC, "decimal($p,$s)" ); This seems to do the trick. -- 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

16 years

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5006) hibernate.globally_quoted_identifiers=true and Annotations tests

by Stephan Palm (JIRA)

hibernate.globally_quoted_identifiers=true and Annotations tests ---------------------------------------------------------------- Key: HHH-5006 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5006 Project: Hibernate Core Issue Type: Bug Components: annotations, core Affects Versions: 3.5.0-CR-2 Environment: eclipse galileo jdk 1.6 Server library JBoss 6.0 M2 (actually I don`t think you need any of this information) Reporter: Stephan Palm If I use hibernate.globally_quoted_identifiers=true in order to quote all identifiers, then the mapping for column names breakes if I have a column with a @Column annotation but without a @Column(name=<COLUMN_NAME>). The mapping for the column name then turns out to be ``.　Which leads to problems when creating new tables. I was able to track the error back to {code} final String columnName = nameNormalizer.normalizeIdentifierQuoting( col.name() ); {code} from Ejb3Column.java. col.name() returns an empty string because the name was not explicitly set. nameNormalizer.normalizeIdentifierQuoting( col.name() ) then makes `` from the empty string. I was able to fix this problem by adding a guard to the nameNormalizer.normalizeIdentifierQuoting function: {code} if ( identifier.length() == 0) return null; {code} The function now looks like this: {code} public String normalizeIdentifierQuoting(String identifier) { if ( identifier == null ) { return null; } if ( identifier.length() == 0) return null; // Convert the JPA2 specific quoting character (double quote) to Hibernate's (back tick) if ( identifier.startsWith( "\"" ) && identifier.endsWith( "\"" ) ) { return '`' + identifier.substring( 1, identifier.length() - 1 ) + '`'; } // If the user has requested "global" use of quoted identifiers, quote this identifier (using back ticks) // if not already if ( isUseQuotedIdentifiersGlobally() && ! ( identifier.startsWith( "`" ) && identifier.endsWith( "`" ) ) ) { return '`' + identifier + '`'; } return identifier; } {code} -- 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

16 years

4
9
0 / 0

[Hibernate-JIRA] Created: (HHH-5171) Allow usage of standalone @JoinFormula annotation

by Sharath Reddy (JIRA)

Allow usage of standalone @JoinFormula annotation ------------------------------------------------- Key: HHH-5171 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5171 Project: Hibernate Core Issue Type: Improvement Components: annotations Affects Versions: 3.6 Reporter: Sharath Reddy Assignee: Sharath Reddy Fix For: 3.6 If there is a single-column join (based on formula) between 2 entities, it is overkill to wrap the @JoinFormula within a @JoinColumnsOrFormulas annotation: @ManyToOne @JoinColumnsOrFormulas( { @JoinColumnOrFormula(formula=@JoinFormula(value="SUBSTR(product_idnf, 1, 3)", referencedColumnName="product_idnf")) }) The above annotation is powerful, because it gives us the flexibility of using an arbitrary combination of columns and formulas for the join, but in this case it is redundant. If would be easier to just specify like this: @ManyToOne @JoinFormula(value="SUBSTR(product_idnf, 1, 3)", referencedColumnName="product_idnf")) }) -- 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

16 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5042) TableGenerator does not increment hibernate_sequences.next_hi_value anymore after having exhausted the current lo-range

by Guenther Demetz (JIRA)

TableGenerator does not increment hibernate_sequences.next_hi_value anymore after having exhausted the current lo-range ----------------------------------------------------------------------------------------------------------------------- Key: HHH-5042 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5042 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1 Environment: Hibernate: 3.5 , db: HSQLDB (not relevant) Reporter: Guenther Demetz Priority: Critical Attachments: TestTableGenerator.java This bug is new in 3.5 In version 3.5 class MultipleHiLoPerTableGenerator.java was modified introducing a new increment variable IntegralDataTypeHolder value; along with int lo; The problem in the new code is that only value get's incremented whilst variable lo is still used to check when a new hiVal must be obtained. if ( lo > maxLo ) { IntegralDataTypeHolder hiVal = (IntegralDataTypeHolder) doWorkInNewTransaction( session ); as lo is never incremented, MultipleHiLoPerTableGenerator continues to deliver numbers without ever update hibernate_sequences.next_hi_value on the database (only one unique update is propagates at the first insert) This lead to duplicate keys as soon another session from another sessionfactory tries to insert new objects on the concerning table. Please see attached testcase. IMPORTANT ADVICE TO RUN THE TESTCASE: as the testcase uses 2 sessionfactories hibernate.hbm2ddl.auto=create cannot be used!! Schema has to be exported separately and the testcase must run without hbm2ddl.auto property! Here the schema for HSQLDB: create table A (oid bigint not null, name varchar(255), version integer not null, primary key (oid), unique (name)) create table hibernate_sequences ( sequence_name varchar(255), sequence_next_hi_value integer ) -- 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

16 years

6
18
0 / 0

[Hibernate-JIRA] Created: (HHH-4991) ManyToMany table not joined due to max_join_depth parameter, results to SQL exceptions

by Sergii Novotarskyi (JIRA)

ManyToMany table not joined due to max_join_depth parameter, results to SQL exceptions -------------------------------------------------------------------------------------- Key: HHH-4991 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4991 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.5.0-CR-2 Environment: Hibernate 3.5.0-CR-2, MacOS X, MySQL 5.1 Reporter: Sergii Novotarskyi Attachments: Example.zip *max_join_depth* parameter prevents Hibernate from joining one end of ManyToMany relationship when using Criteria API, if the relationship is "far" enough from the root entity. {quote} Criteria c = session.createCriteria(SubEntity.class) .createAlias("entity", "e") // ManyToOne, inner join .createAlias("e.entity", "ee") // ManyToOne, inner join .createAlias("ee.sides", "s") // ManyToMany, inner join + left outer join .setProjection(Projections.count("id")) .add(Restrictions.ne("s.data", "abc")); {quote} When *max_join_depth* is set to *2* (default) the above example generates following SQL query {quote} select count(this_.sub_id) as y0_ from SubEntity this_ inner join SubMainEntity e1_ on this_.submain_id=e1_.submain_id inner join MainEntity ee2_ on e1_.main_id=ee2_.main_id inner join MainSide sides7_ on ee2_.main_id=sides7_.main_id where s3_.data<>? {quote} The query, naturally, throws the "Unknown column 's3_.data' in 'where clause'" exception. Expected query would be {quote} select count(this_.sub_id) as y0_ from SubEntity this_ inner join SubMainEntity e1_ on this_.submain_id=e1_.submain_id inner join MainEntity ee2_ on e1_.main_id=ee2_.main_id inner join MainSide sides7_ on ee2_.main_id=sides7_.main_id left outer join SideEntity s3_ on sides7_.side_id=s3_.side_id where s3_.data<>? {quote} -- 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

16 years

5
16
0 / 0

[Hibernate-JIRA] Created: (HHH-4957) Criteria Projections.countDistinct() function broken

by Lin Lai Fu (JIRA)

Criteria Projections.countDistinct() function broken ---------------------------------------------------- Key: HHH-4957 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4957 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-CR-2 Environment: Hibernate: 3.5.0-CR-2 OS: Windows XP (should be OS independent) IDE: Eclipse 3.5 Galileo Reporter: Lin Lai Fu Priority: Blocker The criteria countDistinct() does not generate the correct query: criteria.setProjection(Projections.countDistinct("id")); generates: select count(id) instead of: select count(distinct id) This used to work in version 3.3.2-GA with toSqlString(). This method is missing in 3.5.0 Working version in 3.3.2-GA: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/hibernate/core/trunk/core/src/... Broken version in 3.5.0: http://viewvc.jboss.org/cgi-bin/viewvc.cgi/hibernate/core/trunk/core/src/... See also the forum thread: http://forum.hibernate.org/viewtopic.php?f=1&t=1002910 -- 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

16 years

4
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5125) The annotations @Entity and @MappedSuperclass used in one class produce a nullpointerexception

by Simone Rodenbach (JIRA)

The annotations @Entity and @MappedSuperclass used in one class produce a nullpointerexception ---------------------------------------------------------------------------------------------- Key: HHH-5125 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5125 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.5.1 Environment: MS SQL Server Reporter: Simone Rodenbach Priority: Critical Caused by: java.lang.NullPointerException at org.hibernate.cfg.ClassPropertyHolder.addPropertyToMappedSuperclass(ClassPropertyHolder.java:133) at org.hibernate.cfg.ClassPropertyHolder.addPropertyToPersistentClass(ClassPropertyHolder.java:118) at org.hibernate.cfg.ClassPropertyHolder.addProperty(ClassPropertyHolder.java:98) at org.hibernate.cfg.ClassPropertyHolder.addProperty(ClassPropertyHolder.java:81) at org.hibernate.cfg.annotations.PropertyBinder.bind(PropertyBinder.java:246) at org.hibernate.cfg.annotations.PropertyBinder.makePropertyValueAndBind(PropertyBinder.java:200) at org.hibernate.cfg.AnnotationBinder.processElementAnnotations(AnnotationBinder.java:1979) at org.hibernate.cfg.AnnotationBinder.processIdPropertiesIfNotAlready(AnnotationBinder.java:762) at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:726) at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:636) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:359) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1377) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:954) -- 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

16 years

4
3
0 / 0

[Hibernate-JIRA] Created: (ANN-756) @Column annotation ignored when placed on entity's @Id property

by sagi mann (JIRA)

@Column annotation ignored when placed on entity's @Id property --------------------------------------------------------------- Key: ANN-756 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-756 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.GA Environment: hib core 3.2.6, my sql 5 Reporter: sagi mann Hibernate docs specify that when using a compound key class, a Hibernate optional feature is to place @Column annotations within the key class. The observed behavior is that Hibernate ignores @Column if placed ANYWHERE ELSE, for example, on the entity's ID properties. In other words, the standard JPA way of annotating ID fields is not working under Hibernate, and the "optional" feature is mandatory. Example how to reproduce (see comments inside the code regarding the inconsistency above). Accessors were omitted for clarity: // the identity class @Entity public class SecurityIdentity implements Serializable { public SecurityIdentity() {} @Id @Column(name="IDENTITY_ID") @GeneratedValue public Long getId() ... @Column(name="IDENTITY_NAME") public String getName() ... @Override public boolean equals(Object o) ... @Override public int hashCode() ... } // the domain class @Entity public class SecurityDomain implements Serializable { public SecurityDomain() {} @Id @Column(name="DOMAIN_ID") @GeneratedValue public Long getId() ... @Column(name="DOMAIN_NAME") public String getName() ... @Override public boolean equals(Object o) ... @Override public int hashCode() ... } // the domain-identity mapping class @Entity @IdClass(pu1.DomainIdentityPK.class) public class DomainIdentity implements Serializable { public DomainIdentity() {} @Id public Long getDomainId() ... @Id public String getUserAlias() ... @ManyToOne @JoinColumn(name="IDENTITY_ID") public SecurityIdentity getSecurityIdentity() ... @ManyToOne @JoinColumn(name="DOMAIN_ID", insertable=false, updatable=false) public SecurityDomain getSecurityDomain() { return securityDomain; } public void setSecurityDomain(SecurityDomain securityDomain) { this.securityDomain = securityDomain; this.domainId = (securityDomain != null ? securityDomain.getId() : null); } private SecurityDomain securityDomain; } // the map key class public class DomainIdentityPK implements Serializable { public DomainIdentityPK() { } /********* @Column inconsistency - cannot be placed inside the entity - only inside the PK class *******/ @Column(name="DOMAIN_ID") public Long getDomainId() ... [b]@Column(name="ALIAS")[/b] public String getUserAlias() ... public boolean equals(Object o) ... public int hashCode() ... } -- 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

16 years

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2608) allow delete-orphan cascade style in one-to-one mapping

by Joe Kelly (JIRA)

allow delete-orphan cascade style in one-to-one mapping ------------------------------------------------------- Key: HHH-2608 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2608 Project: Hibernate3 Issue Type: New Feature Components: core Affects Versions: 3.2.4 Environment: 3.2.4, DB2 v8 Reporter: Joe Kelly Please allow the cascade-style "delete-orphan" for one-to-one relationships. When I try to use that cascade style, I get the exception "org.hibernate.MappingException: single-valued associations do not support orphan delete". I realize that the reference manual says "Note that single valued associations (many-to-one and one-to-one associations) do not support orphan delete." But why? I can think of many cases where you WOULD want parent-child semantics in a one-to-one relationship. For example, I have encountered some legacy databases where an entity has all of its fields stored in one table EXCEPT for an optional large field (e.g. a blob field) that is stored in another table, presumably for some performance or storage optimization reason. In this case the two tables are joined with a one-to-one relationship, using a shared primary key. Here are some hypothetical tables, classes and mappings that illustrate this example: company ( company_id (PK) name ) company_extra ( company_extra_id (PK), (FK referencing company.company_id) some_extra_info ) class Company { int companyId; String name; CompanyExtra companyExtra; } class CompanyExtra { int companyExtraId; String someExtraInfo; Company company; } <class name="Company" table="company"> <id name="companyId" column="company_id"> <generator class="sequence"> <param name="sequence">COMPANY_SEQ</param> </generator> </id> <property name="name" column="name" /> <one-to-one name="companyExtra" class="CompanyExtra" cascade="all, delete-orphan" /> </class> <class name="CompanyExtra" table="company_extra"> <id name="companyExtraId" column="company_extra_id" unsaved-value="null"> <generator class="foreign"> <param name="property">company</param> </generator> </id> <property name="someExtraInfo" column="some_extra_info" /> <one-to-one name="company" class="Company" constrained="true" /> </class> For the purposes of this example, CompanyExtra is a child of Company and belongs to one and only one instance of Company. It cannot be shared between Company instances and it cannot be an orphan (i.e. it cannot exist without a parent Company). Also, CompanyExtra is optional so you can have a Company without any associated CompanyExtra during Company's lifecycle. To me, it seems natural and logical that if you set Company.companyExtra to null, and save Company, Hibernate should automatically delete the associated record in the company_extra table if the delete-orphan cascade style is configured (which, of course, it not currently allowed). This is what I want to do when editing an existing Company instance: aCompany = session.load(...); aCompany.setCompanyExtra(null); aCompany.setName("some new name"); session.save(aCompany); // automatically deletes company_extra record For now, I think the workaround is to explicitly delete the CompanyExtra instance in Java code but that just doesn't seem natural to me and it isn't transparent. I do NOT want to do this: aCompany = session.load(...); companyExtra = aCompany.getCompanyExtra(); // ***extra, unnatural method call aCompany.setCompanyExtra(null); aCompany.setName("some new name"); session.save(aCompany); session.delete(companyExtra); // ***another extra, unnatural method call -- 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

16 years

17
20
0 / 0

[Hibernate-JIRA] Created: (ANN-573) Many-to-many with Attributes (Attribute-class with two @ManyToOne mappings as @Id) not possible

by Christian Köberl (JIRA)

Many-to-many with Attributes (Attribute-class with two @ManyToOne mappings as @Id) not possible ----------------------------------------------------------------------------------------------- Key: ANN-573 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-573 Project: Hibernate Annotations Type: Bug Components: binder Versions: 3.2.1 Environment: Hibernate+Annotations 3.2.1-ga, HSQLDB 1.8.0.7 Reporter: Christian Köberl Attachments: manytomanybug.zip Im trying to map the following relation: Order 1-n OrderLine m-1 Product where the OrderLine contains an amount of the ordered product. The problem seems to be multiple @Id in combination with @ManyToOne: @Entity @Table(name = "order_line") // @IdClass(OrderLinePK.class) public class OrderLine implements Serializable { @Id @ManyToOne(targetEntity = Order.class) @JoinColumn(name = "order_id", nullable = false) private Order order; @Id @ManyToOne(targetEntity = Product.class) @JoinColumn(name = "product_id", nullable = false) ... } Hibernate maps the OrderLine class in the following way: DEBUG SchemaUpdate:149 - create table order_line (product varbinary(255) not null, order varbinary(255) not null, amount integer, primary key (order)) (maybe this relates to http://opensource.atlassian.com/projects/hibernate/browse/ANN-435) When I add an IdClass to the OrderLine, I get the following exception: Initial SessionFactory creation failed.org.hibernate.AnnotationException: mappedBy reference an unknown target entity property: model.OrderLine.order in model.Order.lineItems The example is attached as a runnable Maven2-Project, just run mvn test. The test dao.OrderDaoAnnotationTest fails. In the project I also tried to map the same classes with hbm-Files and this works (dao.OrderDaoHbmTest). -- 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

16 years

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4744) Incorrect audit entity for TABLE_PER_CLASS with abstract classes (results in query error)

by Volker Schmidt (JIRA)

Incorrect audit entity for TABLE_PER_CLASS with abstract classes (results in query error) ----------------------------------------------------------------------------------------- Key: HHH-4744 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4744 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.0-Beta-2, 3.2.0.ga Reporter: Volker Schmidt Attachments: envers-1.2.2.ga-hibernate-3.3.patch, trunk.patch The configuration code of Envers does not check the abstract flag of a PersistentClass. Thus the created audit entity is not declared as being abstract. Abstract entities do not have concrete tables. Without declaring the audit entity of a super class as being abstract, queries include a table (that does not exist) for the abstract super class. I have added a patch for the trunk and for Envers 1.2.2. -- 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

16 years

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4078) EntityMetamodel#entityNameByInheritenceClassNameMap mapping from class or class names?

by Tsering Shrestha (JIRA)

EntityMetamodel#entityNameByInheritenceClassNameMap mapping from class or class names? -------------------------------------------------------------------------------------- Key: HHH-4078 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4078 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5 Reporter: Tsering Shrestha In the constructor of EntityMetaModel (http://anonsvn.jboss.org/repos/hibernate/core/trunk/core/src/main/java/or... revision 15258) Line 314: if ( persistentClass.hasPojoRepresentation() ) { entityNameByInheritenceClassNameMap.put( persistentClass.getMappedClass(), persistentClass.getEntityName() ); However at Line 578: public String findEntityNameByEntityClass(Class inheritenceClass) { return ( String ) entityNameByInheritenceClassNameMap.get( inheritenceClass.getName() ); } Why are we using java.lang.Class as the keys when we put new entries to the map but try to read with java.lang.String keys? -- 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

16 years

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-4438) It is impossible to override RelationTargetAuditMode using AuditOverride

by Eugene Goroschenya (JIRA)

It is impossible to override RelationTargetAuditMode using AuditOverride ------------------------------------------------------------------------ Key: HHH-4438 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4438 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.0.Beta-1, 3.3.2, 3.3.x, 3.5 Reporter: Eugene Goroschenya The implementation of HHH-4010 provides great feature: support auditing of entity having reference (many-to-one relation) to not audited entity But it is still impossible to use it with @Embedded to override RelationTargetAuditMode for some reference(s) in @Embeddable class. -- 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

16 years

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4626) OneToMany cascadeType.ALL change collection and merge - does not remove entities

by Dave (JIRA)

OneToMany cascadeType.ALL change collection and merge - does not remove entities --------------------------------------------------------------------------------- Key: HHH-4626 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4626 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.3.1 Environment: JBoss 5.1.0.GA, FC 10, Java 1.6 Reporter: Dave public Class Foo { @OneToMany(fetch=FetchType.LAZY, cascade={CascadeType.ALL}, mappedBy="foo") public List<Bar> getBars() { return bars; } } // aFoo is persited Foo aFoo = ... aFoo.getBars().remove(0); // remove the first aFoo.getBars().add(aBar); // add new one em.merge(aFoo); For cascade={CascadeType.ALL}, it works for creating/deleting aFoo. For merge, the new aBar is created, but the bar that was removed from collection are not deleted from persistence. -- 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

16 years

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3940) Remove hasSelfReferentialForeignKeyBug (returning true) override from MySQL dialects

by Steve Ebersole (JIRA)

Remove hasSelfReferentialForeignKeyBug (returning true) override from MySQL dialects ------------------------------------------------------------------------------------ Key: HHH-3940 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3940 Project: Hibernate Core Issue Type: Task Components: core Affects Versions: 3.3.1, 3.2.7 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.2.x, 3.3.x, 3.5 Previous versions of MySQL had a nasty bug when using self-referential foreign keys with the innodb storage engine. This Dialect#hasSelfReferentialForeignKeyBug was originally added to account for that. Testing against the lastest (5.1) MySQL versions shows this to no longer be present. -- 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

16 years

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3995) Cleanup test data

by Steve Ebersole (JIRA)

Cleanup test data ----------------- Key: HHH-3995 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3995 Project: Hibernate Core Issue Type: Task Components: testsuite Reporter: Steve Ebersole Assignee: Steve Ebersole Priority: Minor Fix For: 3.2.x, 3.3.x, 3.5 Lots of tests are leaving test data hanging around. That works on a particular assumption wrt the execution order of tests or that only a single test method exists. That cuases problems later in many cases. All tests should clean up the test data they create. Currently on trunk I see 246 tests leaving data around. The sys prop hibernate.test.validateDataCleanup can be used to check for this; set it to true. -- 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

16 years

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2439) delay IDENTITY insertions in the case of FlushMode.MANUAL/NEVER

by Steve Ebersole (JIRA)

delay IDENTITY insertions in the case of FlushMode.MANUAL/NEVER --------------------------------------------------------------- Key: HHH-2439 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2439 Project: Hibernate3 Type: Improvement Components: core Reporter: Steve Ebersole Assigned to: Steve Ebersole Fix For: 3.2.3 Much like we do now in 3.2 for out of transaction operations, we should delay performing insertions for post-insert generators with FlushMode.isManualFlushMode -- 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

16 years

5
20
0 / 0

[Hibernate-JIRA] Created: (HHH-4706) Leverage new o.h.dialect.function.TrimFunctionTemplate and o.h.dialect.function.AnsiTrimFunction classes

by Steve Ebersole (JIRA)

Leverage new o.h.dialect.function.TrimFunctionTemplate and o.h.dialect.function.AnsiTrimFunction classes -------------------------------------------------------------------------------------------------------- Key: HHH-4706 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4706 Project: Hibernate Core Issue Type: Improvement Components: core, query-hql Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5 o.h.dialect.function.TrimFunctionTemplate defines basic support for understanding which trim options were specified. o.h.dialect.function.AnsiTrimFunction defines rendering of a trim function using the ANSI SQL defined syntax. -- 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

16 years

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3946) Test FooBarTest isn't opening transactions and contains an invalid assertion

by Juraci Paixao Krohling (JIRA)

Test FooBarTest isn't opening transactions and contains an invalid assertion ---------------------------------------------------------------------------- Key: HHH-3946 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3946 Project: Hibernate Core Issue Type: Bug Components: testsuite Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Fix For: 3.5 Attachments: FooBarTest.java.diff Test FooBarTest have three tests failing: - testDisconnect - testOrderBy - testVeto All of them are issuing commit to transactions which were not started, causing "Transaction not successfully started" error. Also, the test testOrderBy contains an invalid assertion. The code reads: assertEquals( "'b' isn't second element", "b", ( (One) results.get(2) ).getValue() ); But as the method "get" is 0-indexed, the parameter should be 1, instead of 2. The attached patch fixes those issues. -- 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

16 years

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-4035) skip org.hibernate.action.BulkOperationCleanupAction on INSERT HQL queries

by Steve Ebersole (JIRA)

skip org.hibernate.action.BulkOperationCleanupAction on INSERT HQL queries -------------------------------------------------------------------------- Key: HHH-4035 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4035 Project: Hibernate Core Issue Type: Improvement Components: caching (L2) Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3.x, 3.5 For INSERT queries it is really not needed to cleanup caches as we'd have no invalid entity/collection data to cleanup (we'd still nee to invalidate the appropriate update-timestamps regions) as a result of the query. -- 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

16 years

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4885) Use "test" durability mode for derby database in testssuites

by Steve Ebersole (JIRA)

Use "test" durability mode for derby database in testssuites ------------------------------------------------------------ Key: HHH-4885 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4885 Project: Hibernate Core Issue Type: Improvement Components: testsuite Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.0-Next Very similar to Oracle's NOLOG option. {quote} While performance is improved, note that under these conditions, a commit no longer guarantees that the transaction's modification will survive a system crash or JVM termination, the database may not recover successfully upon restart, a near-full disk at runtime may cause unexpected errors, and the database may be in an inconsistent state. {quote} http://publib.boulder.ibm.com/infocenter/cscv/v10r1/index.jsp?topic=/com.... -- 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

16 years

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5052) EventListenerConfigurator uses Ejb3Configuration but could use AnnotationConfiguration instead

by Alexandre Walter Pretyman (JIRA)

EventListenerConfigurator uses Ejb3Configuration but could use AnnotationConfiguration instead ---------------------------------------------------------------------------------------------- Key: HHH-5052 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5052 Project: Hibernate Core Issue Type: Improvement Components: annotations, entity-manager Affects Versions: 3.5.0-CR-2, 3.5.0-CR-1, 3.5.0-Beta-4, 3.5.0-Beta-3, 3.5.0-Beta-2, 3.5.0.Beta-1, 3.3.2, 3.3.1, 3.3.0.SP1, 3.3.0.GA, 3.3.0.CR2, 3.3.0.CR1, 3.2.7, 3.2.6 Environment: Tested with Hibernate 3.2.6ga, Annotations 3.2.1ga, EntityManager 3.3.2ga but seems to affect the code in the trunk. Reporter: Alexandre Walter Pretyman Priority: Trivial The class EventListenerConfigurator uses Ejb3Configuration on it's constructor, but it could use AnnotationConfiguration directly, as the methods called on the Ejb3Configuration instance by the EventListenerConfigurator, are actually delegations to the AnnotationConfiguration . -- 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

16 years

4
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2309) fetch only the lazy property needed

by German de la Cruz (JIRA)

fetch only the lazy property needed ------------------------------------ Key: HHH-2309 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2309 Project: Hibernate3 Type: New Feature Components: core Versions: 3.2.1 Reporter: German de la Cruz The method AbstractEntityPersister.initializeLazyProperty(..) load all lazy properties when it's called. It would be great if could only load the requested property. I think the only change we need is in AbstractEntityPersister.initializeLazyPropertiesFromDatastore(...) and AbstractEntityPersister.initializeLazyPropertiesFromCache(...). We must change them in a way that only the referenced property is loaded. After that, we must change AbstractFieldInterceptor.intercept(..) to update in a better way the unitializedFields collection (I mean, removing the actual property only instead of null it). Besides. Why in line 777 to 780 a query is executed? I think it isn't necessary. Thanks. -- 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

16 years

5
12
0 / 0

[Hibernate-JIRA] Created: (HHH-5123) Brazilian translations

by Steve Ebersole (JIRA)

Brazilian translations ---------------------- Key: HHH-5123 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5123 Project: Hibernate Core Issue Type: Patch Components: core, documentation Affects Versions: 3.5.0-Final Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5.x Grouping of a series of patches for the Brazilian doc translations -- 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

16 years

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5239) Criteria.setLockMode KO

by bill dupond (JIRA)

Criteria.setLockMode KO ----------------------- Key: HHH-5239 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5239 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.5.1, 3.5.0-Final Environment: MySQLDialect Reporter: bill dupond This code doesn't work : the "for update " isn't add in the SQL query. crit = HibernateUtil.currentSession().createCriteria(TIncident.class); crit.add( Restrictions.ge("incDateImportCairn", dateImportCairnMin) ); crit.setLockMode(LockMode.PESSIMISTIC_WRITE); crit.list(); the debug line : 20/05/10 03:19:11-Thread[main]-Class[SQL] | DEBUG | select this_.INC_ID as INC1_25_0_, this_.INC_ID_RATTACHEMENT as INC2_25_0_, this_.TIC_ID as TIC3_25_0_, this_.EQU_ID as EQU4_25_0_, this_.OPE_ID as OPE5_25_0_, this_.INC_DATE_IMPORT_CAIRN as INC6_25_0_, this_.INC_DATE_DEBUT as INC7_25_0_, this_.INC_DATE_FIN as INC8_25_0_, this_.INC_DUREE as INC9_25_0_, this_.INC_DATE_APPARITION_ALARME as INC10_25_0_, this_.INC_DUREE_MOIS as INC11_25_0_, this_.INC_DUREE_HEURE as INC12_25_0_, this_.INC_INSTANCE_OBJET as INC13_25_0_, this_.INC_CLASSE_OBJET as INC14_25_0_, this_.INC_NATURE_INCIDENT as INC15_25_0_, this_.INC_IMPACT_CLIENT as INC16_25_0_, this_.INC_CAUSE_INFORMATIVE as INC17_25_0_, this_.INC_PROBLEME_SPECIFIQUE as INC18_25_0_, this_.INC_INDICATION_TENDANCE as INC19_25_0_, this_.INC_TYPE_ALARME as INC20_25_0_, this_.INC_TYPE_INCIDENT as INC21_25_0_, this_.INC_CAUSE_N1 as INC22_25_0_, this_.INC_CAUSE_N2 as INC23_25_0_, this_.INC_CAUSE_N3 as INC24_25_0_, this_.INC_CAUSE_PROBABLE as INC25_25_0_, this_.INC_SEVERITE as INC26_25_0_, this_.INC_STATUT_ENREGISTREMENT as INC27_25_0_, this_.INC_COMMENTAIRE as INC28_25_0_, this_.INC_NB_CELL as INC29_25_0_, this_.INC_INDICATEUR_MISE_A_JOUR_IHM as INC30_25_0_, this_.INC_INDICATEUR_ASSOCIATION_TICKET as INC31_25_0_, this_.INC_INDICATEUR_ASSOCIATION_OPERATION as INC32_25_0_, this_.INC_INDICATEUR_PRISE_EN_COMPTE as INC33_25_0_ from pcrn01.t_incident this_ where this_.INC_DATE_IMPORT_CAIRN>=? -- 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

16 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4903) Ambiguous column in field list

by Luis Eduardo Villares Matta (JIRA)

Ambiguous column in field list ------------------------------ Key: HHH-4903 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4903 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-4 Environment: O.S.: Linux 2.6.28-18-generic #59-Ubuntu SMP Thu Jan 28 01:40:19 UTC 2010 x86_64 GNU/Linux Java.: Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode) Web server: jetty-hightide-7.0.1.v20091125 DB Server: mysql Ver 14.14 Distrib 5.1.31, for debian-linux-gnu (x86_64) using EditLine wrapper Reporter: Luis Eduardo Villares Matta Priority: Blocker When executing entityManager.find(ClassName.class, pk) caught the exception below. Entities involved in the query below do not have any inheritance relationship (just composition), but they all contain a field named "private" (column name "_private") Hibernate: select libraryite0_.id as id2_2_, libraryite0_.active as active2_2_, libraryite0_.createdDate as createdD3_2_2_, libraryite0_.deleted as deleted2_2_, libraryite0_.updatedDate as updatedD5_2_2_, libraryite0_.defaultLocale as defaultL6_2_2_, libraryite0_.name as name2_2_, libraryite0_.parentId as parentId2_2_, _private as column8_2_2_, libraryite0_.typeId as typeId2_2_, libraryite1_.id as id2_0_, libraryite1_.active as active2_0_, libraryite1_.createdDate as createdD3_2_0_, libraryite1_.deleted as deleted2_0_, libraryite1_.updatedDate as updatedD5_2_0_, libraryite1_.defaultLocale as defaultL6_2_0_, libraryite1_.name as name2_0_, libraryite1_.parentId as parentId2_0_, _private as column8_2_0_, libraryite1_.typeId as typeId2_0_, libraryite2_.id as id5_1_, libraryite2_.active as active5_1_, libraryite2_.createdDate as createdD3_5_1_, libraryite2_.deleted as deleted5_1_, libraryite2_.updatedDate as updatedD5_5_1_, libraryite2_.folderish_ as folderish6_5_1_, libraryite2_.libraryId as libraryId5_1_, libraryite2_.name as name5_1_, libraryite2_.xsd_ as xsd8_5_1_, libraryite2_.xpaths_ as xpaths9_5_1_ from TKBMLibraryItem libraryite0_ left outer join TKBMLibraryItem libraryite1_ on libraryite0_.parentId=libraryite1_.id left outer join TKBMLibraryItemType libraryite2_ on libraryite1_.typeId=libraryite2_.id where libraryite0_.id=? 174363 [qtp1469937134-21] WARN org.hibernate.util.JDBCExceptionReporter - SQL Error: 1052, SQLState: 23000 174363 [qtp1469937134-21] ERROR org.hibernate.util.JDBCExceptionReporter - Column '_private' in field list is ambiguous 174363 [qtp1469937134-21] INFO org.hibernate.event.def.DefaultLoadEventListener - Error performing load command org.hibernate.exception.ConstraintViolationException: could not load an entity: [com.totvs.kbm.model.LibraryItemModel#10128] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:95) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.loadEntity(Loader.java:1916) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:71) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:65) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3212) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:437) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:418) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:165) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:223) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:126) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:1080) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:997) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:990) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:538) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:513) at com.totvs.kbm.service.KnowledgeService.getLibraryItem(KnowledgeService.java:476) at org.apache.jsp.html.kbm.rootitemsnavigation_jsp._jspService(org.apache.jsp.html.kbm.rootitemsnavigation_jsp:179) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:389) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:530) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1216) at com.totvs.kbm.core.web.RequestPipeline.doFilter(RequestPipeline.java:132) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1187) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:425) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:457) at org.eclipse.jetty.server.session.SessionHandler.handle(SessionHandler.java:182) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:933) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:362) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:867) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:245) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113) at org.eclipse.jetty.server.Server.handle(Server.java:334) at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:559) at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:992) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:541) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:203) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:406) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:462) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436) at java.lang.Thread.run(Thread.java:619) Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Column '_private' in field list is ambiguous at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) at java.lang.reflect.Constructor.newInstance(Constructor.java:513) at com.mysql.jdbc.Util.handleNewInstance(Util.java:406) at com.mysql.jdbc.Util.getInstance(Util.java:381) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1015) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3558) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3490) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1959) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2109) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2648) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2077) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2228) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208) at org.hibernate.loader.Loader.getResultSet(Loader.java:1827) at org.hibernate.loader.Loader.doQuery(Loader.java:714) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:271) at org.hibernate.loader.Loader.loadEntity(Loader.java:1902) ... 45 more 2010-02-10 14:48:50.375:WARN::/html/kbm/rootitemsnavigation.jsp javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: could not load an entity: [com.totvs.kbm.model.LibraryItemModel#10128] at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1197) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:558) at org.hibernate.ejb.AbstractEntityManagerImpl.find(AbstractEntityManagerImpl.java:513) at com.totvs.kbm.service.KnowledgeService.getLibraryItem(KnowledgeService.java:476) at org.apache.jsp.html.kbm.rootitemsnavigation_jsp._jspService(org.apache.jsp.html.kbm.rootitemsnavigation_jsp:179) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:109) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:389) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:486) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:380) at javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:530) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1216) at com.totvs.kbm.core.web.RequestPipeline.doFilter(RequestPipeline.java:132) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1187) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:425) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:457) at org.eclipse.jetty.server.session.SessionHandler.handle(SessionHandler.java:182) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:933) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:362) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:867) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:245) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:126) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:113) at org.eclipse.jetty.server.Server.handle(Server.java:334) at org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:559) at org.eclipse.jetty.server.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:992) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:541) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:203) at org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:406) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:462) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:436) at java.lang.Thread.run(Thread.java:619) -- 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

16 years

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4624) QueryImpl.list() closes connection

by Dieter Freismuth (JIRA)

QueryImpl.list() closes connection ---------------------------------- Key: HHH-4624 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4624 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: linux, postgres 8.3 (same on oracle 11g, mssql 2005 and mysql) Reporter: Dieter Freismuth Priority: Critical if an outer query.iterate() calls within an iteration step a query.list() the connection is closed and the next outer iteration step causes: org.hibernate.exception.JDBCConnectionException: could not get next iterator result at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:97) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:52) at org.hibernate.impl.IteratorImpl.next(IteratorImpl.java:156) the exception is only thrown if there is no transaction! (works fine if done within an transaction) call hierarchy: QueryImpl.list() -> SessionImpl.list(String query, QueryParameters queryParameters) -> afterOperation(success); // within finally block -> JDBCContext.afterNontransactionalQuery( success ) -> ConnectionManager.afterTransaction() -> ConnectionManager.aggressiveRelease() // within if ( isAfterTransactionRelease() ) { -> ConnectionManager.closeConnection() -- 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

16 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3077) Move references to LRUMap and ReferenceMap

by Stephen Kestle (JIRA)

Move references to LRUMap and ReferenceMap ------------------------------------------ Key: HHH-3077 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3077 Project: Hibernate3 Issue Type: Sub-task Reporter: Stephen Kestle -- 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

16 years

2
3
0 / 0

[Hibernate-JIRA] Erstellt: (HHH-2224) executeUpdate causes coarse cache invalidation

by Stefan Fleiter (JIRA)

executeUpdate causes coarse cache invalidation ---------------------------------------------- Key: HHH-2224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2224 Project: Hibernate3 Type: Improvement Versions: 3.2.0.ga Environment: Hibernate 3.2.0.ga, Oracle 9.2 Reporter: Stefan Fleiter Attachments: bulk_testcase.zip I am developing an application and want to mix bulk-updates with normal hibernate operations. The bulk updates work fine, but invalidate the whole region and I've found no possibility to prevent this. There would be 3 options to improve: - Invalidate only the modified objects if the ids where given as Query-parameters. - Let me deactivate the invalidation so I can invalidate the affected objects myself. - Transform the DML to a select to gather the objects to invalidate before executing the DML The reference documentation does not mention caching at all: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#batch-direct The best documentation I've found is: http://blog.hibernate.org/cgi-bin/blosxom.cgi/2005/07/19#dml-basic Maybe this could be added to the reference documentation... I already posted this at the forum http://forum.hibernate.org/viewtopic.php?t=966775 but did not get a single answer. I've attached a testcase for this. -- 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

16 years

10
19
0 / 0

[Hibernate-JIRA] Created: (HHH-4832) Secondary tables do not work in JOINED or TABLE_PER_CLASS inheritance strategies

by Simon Godden (JIRA)

Secondary tables do not work in JOINED or TABLE_PER_CLASS inheritance strategies -------------------------------------------------------------------------------- Key: HHH-4832 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4832 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: Hibernate 3.3.2, Postgres 8.4.2 Reporter: Simon Godden Attachments: hibernatetest2.tgz I have a class hierarchy as follows: {noformat} Abstract RootClass (Mapped Superclass) | \ / Abstract IntermediateClass (Entity) | | \ / \ / LeafClass (Entity) LeafClass2 (Entity) {noformat} The following table shows which attributes are on each class: ||Class||Attribute||Table|| |RootClass|field1|rootclass| |IntermediateClass|field2|intermediateclass| |LeafClass|field3|leafclass| |LeafClass|field4|leafclass2| |AnotherLeafClass|field5|anotherleafclass| |AnotherLeafClass|field6|anotherleafclass2| Using {{InheritanceType.SINGLE_TABLE}}, it works. Using {{InheritanceType.JOINED}} or {{InheritanceType.TABLE_PER_CLASS}} at the {{IntermediateClass}} level causes different errors: Using {{InheritanceType.JOINED}} causes an incorrect insert statement which thinks that {{field4}} is on table {{leafclass}} rather than {{leafclass2}}: {noformat} Hibernate: insert into LeafClass (field1, field2, field3, field4, id) values (?, ?, ?, ?, ?) Exception in thread "main" [22/01/10 03:17:53:053 GMT] WARN util.JDBCExceptionReporter: SQL Error: 0, SQLState: null [22/01/10 03:17:53:053 GMT] ERROR util.JDBCExceptionReporter: Batch entry 0 insert into LeafClass (field1, field2, field3, field4, id) values (foo1, foo2, foo3, foo4, 1) was aborted. Call getNextException to see the cause. [22/01/10 03:17:53:053 GMT] WARN util.JDBCExceptionReporter: SQL Error: 0, SQLState: 42703 [22/01/10 03:17:53:053 GMT] ERROR util.JDBCExceptionReporter: ERROR: column "field4" of relation "leafclass" does not exist {noformat} Using {{InheritanceType.TABLE_PER_CLASS}} causes the following error as the session factory is built: {noformat} [22/01/10 03:06:05:005 GMT] INFO cfg.SettingsFactory: Echoing all SQL to stdout [22/01/10 03:06:05:005 GMT] INFO cfg.SettingsFactory: Statistics: disabled [22/01/10 03:06:05:005 GMT] INFO cfg.SettingsFactory: Deleted entity synthetic identifier rollback: disabled [22/01/10 03:06:05:005 GMT] INFO cfg.SettingsFactory: Default entity-mode: pojo [22/01/10 03:06:05:005 GMT] INFO cfg.SettingsFactory: Named query checking : enabled [22/01/10 03:06:05:005 GMT] INFO impl.SessionFactoryImpl: building session factory [22/01/10 03:06:06:006 GMT] ERROR hibernate.AssertionFailure: an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session) org.hibernate.AssertionFailure: Table leafclass2 not found at org.hibernate.persister.entity.JoinedSubclassEntityPersister.getTableId(JoinedSubclassEntityPersister.java:480) at org.hibernate.persister.entity.JoinedSubclassEntityPersister.<init>(JoinedSubclassEntityPersister.java:259) at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:87) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:267) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1341) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867) at tests.inheritdomain.SessionManager.initialiseSessionFactory(SessionManager.java:23) at tests.inheritdomain.SessionManager.openSession(SessionManager.java:14) at tests.inheritdomain.TestSecondaryTablesInInheritance.test(TestSecondaryTablesInInheritance.java:20) at tests.inheritdomain.TestSecondaryTablesInInheritance.main(TestSecondaryTablesInInheritance.java:44){noformat} A minimal test case is attached as an maven and eclipse project. mvn test will show the error. I have not created a test case for each inheritance type - you will have to change it in the intermediate domain class to see the other error. -- 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

16 years

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2470) Use of session.createSQLQuery causes memory leak

by Bjørn Bjerkeli (JIRA)

Use of session.createSQLQuery causes memory leak ------------------------------------------------- Key: HHH-2470 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2470 Project: Hibernate3 Type: Bug Components: query-sql Versions: 3.1.3 Environment: Win XP, Oracle 10g, Java 1.4.2 Reporter: Bjørn Bjerkeli Attachments: TestCase.zip NativeSQLQuerySpecification fails to properly implement equals and hashcode caused by lacking implementation of hashCode and equals in all SQLQueryReturn implementations and SQLQueryScalarReturn which are members of NativeSQLQuerySpecification. I can see that NativeSQLQuerySpecification has been changed in 3.2, but the problem is still there. NativeSQLQuerySpecification instances are used as keys for retrieving and caching NativeSQLQueryPlan instances. This causes the caching-mechanism to be pretty useless when Queries created by session.createSQLQuery because new entries will be added all the time in the QueryPlanCache and the SoftLimitMRUCache member. So far so good, the more serious problem that is caused by this is stems from the implementation of SoftLimitMRUCache which again uses LRUMap in commons-collection. The put - method of the cache is not treadsafe, and that causes the following fragment in LRUMap to allow the map to grow beyond its maximumSize. That is bacause the containsKey method will return an incorrect result when concurrently updating the map. public Object put( Object key, Object value ) { int mapSize = size(); Object retval = null; if ( mapSize >= maximumSize ) { // don't retire LRU if you are just // updating an existing key if (!containsKey(key)) { // lets retire the least recently used item in the cache removeLRU(); } } retval = super.put(key,value); return retval; } I have included a test-case that demonstrates: 1) Wrong implementation of equals and hashCode in NativeSQLQuerySpecification 2) Concurrent use of LRUMap causes the map to grow beyound it's max limit 3) Concurrent execution of session.createSQLQuery causes memory leak due to 1) and 2) I would be more than happy to contribute to get this fixed. Just let me know. -- 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

16 years

14
23
0 / 0

[Hibernate-JIRA] Created: (HHH-3221) Cascading performance problems when session contains many entities

by Yves Galante (JIRA)

Cascading performance problems when session contains many entities ------------------------------------------------------------------ Key: HHH-3221 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3221 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.3.0.CR1, 3.2.6, 3.2.5 Reporter: Yves Galante Attachments: patchCascading.patch, SaveTest.zip When session contains many entities, performence of cascading become very slow. For each collection element the whole persistence context is searched (by StatefulPersistenceContext#getIndexInOwner() and StatefulPersistenceContext#getOwnerId) and its even searched twice when the collection is an indexed collection. This patch optimize cascading operation by caching relation parent-child on a map. eventSource.getPersistenceContext().addChildParent(child, parent); action.cascade(eventSource, child, entityName, anything, isCascadeDeleteEnabled); eventSource.getPersistenceContext().removeChildParent(child); The test case save and flush 10 * 551 objects. Before patch save object with cascading is more slow when session size grows. After patch time of save stay same at each loop. Output of the test case before the patch : Save took 449 ms Save took 669 ms Save took 1042 ms Save took 1464 ms Save took 2481 ms Save took 2741 ms Save took 3807 ms Save took 4344 ms Save took 4975 ms Save took 5251 ms Total took 30906 ms Output after the patch Save took 445 ms Save took 144 ms Save took 164 ms Save took 108 ms Save took 93 ms Save took 93 ms Save took 93 ms Save took 94 ms Save took 91 ms Save took 89 ms Total took 4905 ms -- 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

16 years

4
10
0 / 0

[Hibernate-JIRA] Created: (HHH-5266) NullPointer in toString of PersistentBag

by Jan Stolze (JIRA)

NullPointer in toString of PersistentBag ---------------------------------------- Key: HHH-5266 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5266 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Reporter: Jan Stolze We have created an interceptor which keeps track of changes during a running transaction so in case of a rollback we can log which changes where issued before the rollback is performed. Now we sometimes see in case a rollback is issued the following stacktrace: exception in interceptor afterTransactionCompletion() java.lang.NullPointerException at org.hibernate.event.def.DefaultInitializeCollectionEventListener.initializeCollectionFromCache(DefaultInitializeCollectionEventListener.java:116) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:71) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1744) at org.hibernate.collection.AbstractPersistentCollection.initialize(AbstractPersistentCollection.java:366) at org.hibernate.collection.AbstractPersistentCollection.read(AbstractPersistentCollection.java:108) at org.hibernate.collection.PersistentBag.toString(PersistentBag.java:506) at java.lang.String.valueOf(String.java:2826) at java.lang.StringBuilder.append(StringBuilder.java:115) at gti.db.DbRollbackLogginInterceptor$LogEntry.toString(DbRollbackLogginInterceptor.java:246) at java.lang.String.valueOf(String.java:2826) at java.lang.StringBuilder.append(StringBuilder.java:115) at gti.db.DbRollbackLogginInterceptor.logRollback(DbRollbackLogginInterceptor.java:109) at gti.db.DbRollbackLogginInterceptor.afterTransactionCompletion(DbRollbackLogginInterceptor.java:70) at org.hibernate.impl.SessionImpl.afterTransactionCompletion(SessionImpl.java:455) at org.hibernate.jdbc.JDBCContext.afterTransactionCompletion(JDBCContext.java:252) at org.hibernate.transaction.JDBCTransaction.rollback(JDBCTransaction.java:208) at org.hibernate.ejb.TransactionImpl.rollback(TransactionImpl.java:85) We do not have (at this moment) a clear overview of what has happend and what the exact conditions are for this NPE to occur, but think it is still important enough to report. -- 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

16 years

3
4
0 / 0

[Hibernate-JIRA] Created: (ANN-793) @ManyToOne - @OneToMany doesn't work with @Inheritance(strategy= InheritanceType.JOINED)

by Tomaz Cerar (JIRA)

@ManyToOne - @OneToMany doesn't work with @Inheritance(strategy= InheritanceType.JOINED) ---------------------------------------------------------------------------------------- Key: ANN-793 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-793 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.4.0.GA Environment: Hibernate Core 3.3.1.GA Hibernate Annotations 3.4.0 GA Hibernate EntityManager 3.4.0 GA Jboss 4.3 EAP, DB2 9.5 Reporter: Tomaz Cerar I am trying to create bidirectional association between two entities in which one can be Inherited and it fails with table not found: 11:37:39,229 ERROR [AssertionFailure] [] an assertion failure occured (this may indicate a bug in Hibernate, but is more likely due to unsafe use of the session) org.hibernate.AssertionFailure: Table CRM.CRM_AKTIVNOST_DOGODKI not found at org.hibernate.persister.entity.JoinedSubclassEntityPersister.getTableId(JoinedSubclassEntityPersister.java:480) at org.hibernate.persister.entity.JoinedSubclassEntityPersister.<init>(JoinedSubclassEntityPersister.java:259) at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:87) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:261) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1327) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:669) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:132) at org.jboss.ejb3.entity.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:246) The code looks like this: @Entity @Table(name = "CRM_AKTIVNOST") public class Aktivnost implements Serializable { private List<Dogodek> dogodki; .... .... @OneToMany(fetch = FetchType.LAZY, cascade = CascadeType.ALL,mappedBy = "aktivnost") public List<Dogodek> getDogodki() { return dogodki; } public void setDogodki(List<Dogodek> dogodki) { this.dogodki = dogodki; } ... ... } @Entity @Table(name = "CRM_DOGODEK") @Inheritance(strategy= InheritanceType.JOINED) public class Dogodek implements Serializable { ... ... private Aktivnost aktivnost; .... .... @ManyToOne(fetch = FetchType.LAZY, cascade = CascadeType.ALL) @JoinTable(name = "CRM_AKTIVNOST_DOGODKI", joinColumns = {@JoinColumn(name = "DOGODEK_ID")}, inverseJoinColumns = {@JoinColumn(name = "AKTIVNOST_ID")}) public Aktivnost getAktivnost() { return aktivnost; } public void setAktivnost(Aktivnost aktivnost) { this.aktivnost = aktivnost; } ... } -- 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

16 years

9
12
0 / 0

[Hibernate-JIRA] Created: (HHH-4716) NotAuditedException using the entity name concept of hibernate.

by Subhan (JIRA)

NotAuditedException using the entity name concept of hibernate. ---------------------------------------------------------------- Key: HHH-4716 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4716 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.0-Beta-2 Environment: hibernate-envers-3.5.0-Beta-2 and hibernate-core-3.3.2.GA DB : Oracle XE Reporter: Subhan Priority: Blocker Attachments: SimpleHibernateEnversExample.rar I'm trying to use the entity name concept of hibernate, it saves/updates/deletes the data and audit data properly. When trying to read the audited information its getting NotAuditedException error. For reading the audited information , it would be great to have the support of entity name concepts as hibernate. Sample project is added as attachment.(Which is having sample test case). -- 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

16 years

3
5
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 May 2010