May 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3789) Allow for pluggable stats collection

by Patrick Moore (JIRA)

Allow for pluggable stats collection ------------------------------------ Key: HHH-3789 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3789 Project: Hibernate Core Issue Type: Patch Affects Versions: 3.5 Reporter: Patrick Moore Attachments: patch.txt I have a need to do more fine-grain stats collection. The current implementation does not allow for a replacement stats collection. This patch allows for the default stats code to be replaced with a custom implementation. -- 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

15 years, 8 months

2
10
0 / 0

[Hibernate-JIRA] Created: (HHH-3407) @TableGenerator does not increment pkColumnValue by allocationSize

by Dan Ciarniello (JIRA)

@TableGenerator does not increment pkColumnValue by allocationSize ------------------------------------------------------------------ Key: HHH-3407 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3407 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.6, 3.2.4 Environment: JBoss 4.2.3, RHEL4, JDK1.5 Reporter: Dan Ciarniello According to the JPA, the allocationSize attribute to @TableGenerator is "The amount to increment by when allocating id numbers from the generator" but the value is actually incremented by 1 regardless of allocationSize. The id is generated properly apparently according to the formula id = lastkeyval*allocationSize + i where 0<i<allocationSize The problems with this algorithm are: 1. One cannot tell what the next key value range is from the key table without knowing the allocationSize (minor) 2. If the allocationSize is reduced, already existing key values will be generated (major) 3. If two applications are configured with different allocation sizes, there will be an overlap in generated values (major) -- 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

15 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3709) Add StartRevision/EndRevison fileds to audit tables

by jason shi (JIRA)

Add StartRevision/EndRevison fileds to audit tables --------------------------------------------------- Key: HHH-3709 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3709 Project: Hibernate Core Issue Type: Improvement Components: envers Affects Versions: 3.4 Reporter: jason shi In Envers audit tables(eg:Person_Aud), two fields added:REV,REVTYPE When retrieve data at special REV, a sql with subselect executed: select a.id, a.REV, a.REVTYPE, a.name, a.surname, a.address_id from Person_AUD a where a.REVTYPE <> ? and a.id = ? and a.REV = (select max(b.REV) from Person_AUD b where b.REV <= ? and a.id = b.id) The sql performance is poor. I suggest adding StartRevision/EndRevison fileds to the audit tables,replace the REV field. The StartRevision equals the original REV field,EndRevision will be filledd when this record changed in next Revision. The new query sql will like this: select a.id, a.REV, a.REVTYPE, a.name, a.surname, a.address_id from Person_AUD a where a.REVTYPE <> ? and a.id = ? and a.StartRevision<=? and a.EndRevision>? -- 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

15 years, 8 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3766) Modify the queries executed to use the "end-revision" column, when available

by Adam Warski (JIRA)

Modify the queries executed to use the "end-revision" column, when available ---------------------------------------------------------------------------- Key: HHH-3766 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3766 Project: Hibernate Core Issue Type: Sub-task Reporter: Adam Warski Assignee: Adam Warski If the end-revision column is available, it should be use in queries which lookup revisions -- 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

15 years, 8 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HV-299) Annotation processor should check constraint annotation type declarations

by Gunnar Morling (JIRA)

Annotation processor should check constraint annotation type declarations ------------------------------------------------------------------------- Key: HV-299 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-299 Project: Hibernate Validator Issue Type: New Feature Components: annotation-processor Affects Versions: 4.1.0-Beta-1 Reporter: Gunnar Morling Assignee: Hardy Ferentschik When visiting a custom constraint annotation type declaration, the AP should check the following: * proper declaration of groups(), message(), payload() * retention policy is RUNTIME * array of supported types must not be empty -- 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

15 years, 8 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4769) In HQL, function ROUND always returns an Integer, it truncate the decimal part of Double number.

by Andrea Tunesi (JIRA)

In HQL, function ROUND always returns an Integer, it truncate the decimal part of Double number. ------------------------------------------------------------------------------------------------ Key: HHH-4769 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4769 Project: Hibernate Core Issue Type: Bug Components: core, entity-manager, query-hql Affects Versions: 3.3.2 Environment: hibernate 3.3.2, mysql-connector-java-5.1.7, database MYSQL 5. Reporter: Andrea Tunesi Priority: Blocker Running the query "select round(stTmpRiepCap.imponibile,1), round(stTmpRiepCap.ritImponibile,1) from StTmpRiepCap stTmpRiepCap", it always returns an Integer and it always truncate the decimal part of Double number ("stTmpRiepCap.imponibile" and "stTmpRiepCap.ritImponibile" are "java.lang.Double"). Example REAL VALUE - Imponibile: 1528.57 -- Ritenuta imponibile 266.13 VALUE RETURNED USING ROUND - Imponibile: 1528 -- Ritenuta imponibile 266 -- 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

15 years, 8 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2131) SYBASE +select for update is showing deadlock because lock is not working properly

by George Thomas (JIRA)

SYBASE +select for update is showing deadlock because lock is not working properly ---------------------------------------------------------------------------------- Key: HHH-2131 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2131 Project: Hibernate3 Type: Bug Components: core Versions: 3.1.3 Environment: sybaseASE 12.5.03 in solaris +hibernate3.1.3 Reporter: George Thomas I am connecting to Sybase database from hibernate.I tried setting locks using while selecting rows 1.session.load(class,id,LOCKMODE.UPGRADE) 2.session.lock(obj,LOCKMODE.UPGRADE) I am attaching a sample code while updating a field in table fund after selecting it. { Fund fund = null; ClientCredential credential = new ClientCredential("testDatabase", fund); org.hibernate.Session session = SessionFactoryManager.getSessionFactory(credential).getCurrentSession(); Transaction transaction = session.beginTransaction(); log.info("Run by " + Thread.currentThread().getName()); fund = (Fund) session.get(Fund.class, new Short((short)12), LockMode.UPGRADE); fund.setLegalEntityOrgId(fund.getLegalEntityOrgId()+1); transaction.commit(); } my requirement was that i wanted to do a select for update.I should acquire lock on certain rows and do a matching and if concurrent request comes ,it should wait till transaction is over that is lock is released. When I went through the hibernate code,the hibernate is making static queries in the beginning while loading session factory.Since we are appending the holdlock during execution,the sybase dialect is not appending. As a work around I tested with native sql with holdlock but when I test concurrent request using threads its bombing.Its throwing LockAcquisitionException.( Your server command (family id #0, process id #3777) encountered a deadlock situation.).can anyone give a solution to this problem??? org.hibernate.exception.LockAcquisitionException: could not update: [com.citco.aexeo.common.dataaccess.domain.Fund#12] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:84) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2223) at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2118) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2375) at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:91) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:250) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:233) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:140) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:297) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:985) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:333) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:107) at com.satyam.Testing.doTransaction(Testing.java:103) at com.satyam.MyRunnable.run(MyRunnable.java:13) at java.lang.Thread.run(Thread.java:568) Caused by: com.sybase.jdbc2.jdbc.SybSQLException: Your server command (family id #0, process id #3777) encountered a deadlock situation. Please re-run your command. at com.sybase.jdbc2.tds.Tds.processEed(Tds.java:2636) at com.sybase.jdbc2.tds.Tds.nextResult(Tds.java:1996) at com.sybase.jdbc2.jdbc.ResultGetter.nextResult(ResultGetter.java:69) at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:204) at com.sybase.jdbc2.jdbc.SybStatement.nextResult(SybStatement.java:187) at com.sybase.jdbc2.jdbc.SybStatement.updateLoop(SybStatement.java:1642) at com.sybase.jdbc2.jdbc.SybStatement.executeUpdate(SybStatement.java:1625) at com.sybase.jdbc2.jdbc.SybPreparedStatement.executeUpdate(SybPreparedStatement.java:91) at org.hibernate.jdbc.NonBatchingBatcher.addToBatch(NonBatchingBatcher.java:23) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2205) ... 14 more -- 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

15 years, 8 months

6
10
0 / 0

[Hibernate-JIRA] Created: (ANN-837) @Where clause may trigger an ambiguous column error

by Bob Harrod (JIRA)

@Where clause may trigger an ambiguous column error --------------------------------------------------- Key: ANN-837 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-837 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.1.GA Environment: Hibernate Core 3.3.1GA, Annotations 3.4.0GA, PostgreSQL 8.3 Reporter: Bob Harrod Attachments: LoginUnit.java, LoginUnitUser.java, LoginUser.java The following annotations are being used to simulate a soft delete strategy: @Entity @Table(name = "login_unit_user") @SQLDelete( sql="UPDATE login_unit_user SET _is_active = 0 WHERE id = ?") @Where(clause="_is_active <> 0") public class LoginUnitUser extends DomainObject implements Serializable{...} and @Entity @Table(name = "login_unit") @SQLDelete( sql="UPDATE login_unit SET _is_active = 0 WHERE id = ?") @Where(clause="_is_active <> 0") public class LoginUnit extends DomainObject implements Serializable{...} In the attached code, both LoginUnit and LoginUnitUser contain a system column - "_is_active". This column represents a flag which indicates whether or not the row is "active" or "deleted". When these two hibernate model objects are queried, hibernate does not properly append the table alias to this additional where clause that it uses during it's database query. The error raised is: org.hibernate.exception.SQLGrammarException: could not execute query at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:90) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.doList(Loader.java:2231) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2125) at org.hibernate.loader.Loader.list(Loader.java:2120) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:401) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:361) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1148) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102) at org.hibernate.ejb.QueryImpl.getSingleResult(QueryImpl.java:88) ... 35 more Caused by: org.postgresql.util.PSQLException: ERROR: column reference "_is_active" is ambiguous at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:1608) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1343) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:194) at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:451) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:350) at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:254) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208) at org.hibernate.loader.Loader.getResultSet(Loader.java:1808) at org.hibernate.loader.Loader.doQuery(Loader.java:697) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:259) at org.hibernate.loader.Loader.doList(Loader.java:2228) ... 43 more An example query with the hibernate generated aliases (loginuser0_, loginunitu1_, loginunit2_) is below: Hibernate: select loginuser0_.id as id21_, loginuser0_._audit_login_user_id as column7_21_, loginuser0_._created as column2_21_, loginuser0_.first_name as first3_21_, loginuser0_.last_name as last4_21_, loginuser0_._updated as column5_21_, loginuser0_.user_name as user6_21_ from login_user loginuser0_, login_unit_user loginunitu1_, login_unit loginunit2_ where ( _is_active <> 0 ) and ( _is_active <> 0 ) and loginuser0_.id=loginunitu1_.login_user_id and loginunitu1_.login_unit_id=loginunit2_.id and loginuser0_.user_name=? and loginunit2_.id=? limit ? -- 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

15 years, 8 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5020) java.sql.SQLException: ORA-00904: "Y6_": invalid identifier when performing search by criteria with columns aliases defined and with restriction defined

by Alexander (JIRA)

java.sql.SQLException: ORA-00904: "Y6_": invalid identifier when performing search by criteria with columns aliases defined and with restriction defined -------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-5020 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5020 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.2.5 Environment: Oracle 10g Reporter: Alexander Attachments: stacktrace.JPG The exception is occured when I performs search by criteria like this DetachedCriteria headerCrit = DetachedCriteria.forClass(LOSHeader.class); ProjectionList prjList = Projections.projectionList(); prjList.add(Projections.groupProperty("channelId"),"channelId"); prjList.add(Projections.groupProperty("channel"),"channel"); prjList.add(Projections.groupProperty("subCategoryId"),"subCategoryId"); prjList.add(Projections.groupProperty("subCategory"),"subCategory"); prjList.add(Projections.groupProperty("bevCategoryId"),"bevCategoryId"); prjList.add(Projections.groupProperty("bevCategory"),"bevCategory"); prjList.add(Projections.groupProperty("accessFilter"),"accessFilter"); headerCrit.setProjection(prjList); headerCrit.add(Restrictions.like("accessFilter","%,INTERNAL;%")); headerCrit.setResultTransformer(Transformers.aliasToBean(LOSHeader.class)); List result = pipelineDAO.loadByCriteria(headerCrit, LOSHeader.class); Criteria string: DetachableCriteria(CriteriaImpl(com.ko.cokechannel.los.impl.entity.LOSHeader:this[][accessFilter like %,INTERNAL;%][channelId as channelId, channel as channel, subCategoryId as subCategoryId, subCategory as subCategory, bevCategoryId as bevCategoryId, bevCategory as bevCategory, accessFilter as accessFilter])) The is list of projections: [channelId as channelId, channel as channel, subCategoryId as subCategoryId, subCategory as subCategory, bevCategoryId as bevCategoryId, bevCategory as bevCategory, accessFilter as accessFilter] Method execution stack trace (also the screenshot of stack trace is attached) : CriteriaQueryTranslator.getWhereCondition()-> String sqlString = entry.getCriterion().toSqlString( entry.getCriteria(), this ); SimpleExpression.toSqlString() -> CriteriaQueryTranslator.getColumnsUsingProjection(criteria, propertyName); // propertyName is "accessFilter" ProjectionList.getColumnAliases(String alias, int loc){ // alias = "accessFilter" .... String[] result = getProjection(i).getColumnAliases(alias, loc); if (result!=null) return result; ..... result is: [y6_] // Restriction for accessFilter property is mathced with the value from projection aliases, so [y6_] is returned for the WHERE condition WHERE clause sql: y6_ like ? The final sql looks like: select this_.CHANNEL_ID as y0_, this_.CHANNEL_NM as y1_, this_.SUB_CATEGORY_ID as y2_, this_.SUB_CATEGORY_NM as y3_, this_.BEV_CATEGORY_ID as y4_, this_.BEV_CATEGORY_NM as y5_, this_.ACCESS_FILTER as y6_ from V_LOS_LIST this_ WHERE y6_ like ? <<<<<<< ---- THIS IS WRONG - group by this_.CHANNEL_ID, this_.CHANNEL_NM, this_.SUB_CATEGORY_ID, this_.SUB_CATEGORY_NM, this_.BEV_CATEGORY_ID, this_.BEV_CATEGORY_NM, this_.ACCESS_FILTER I think that the cause of this issue is the same as was mentioned in http://opensource.atlassian.com/projects/hibernate/browse/HHH-2847 To easy reproduce this issue just try to search by a criteria like this: DetachedCriteria criteria = DetachedCriteria.forClass(Entity.class); criteria.setProjection(Projections.groupProperty("propertyA"),"propertyA"); criteria.add(Restrictions.like("propertyA", "%")); criteria.setResultTransformer(Transformers.aliasToBean(Entity.class)); Thank you, Alex -- 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

15 years, 8 months

7
20
0 / 0

[Hibernate-JIRA] Created: (HHH-2691) Insert Into Select command outputs incorrect exception

by John Aylward (JIRA)

Insert Into Select command outputs incorrect exception ------------------------------------------------------ Key: HHH-2691 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2691 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.4.sp1 Environment: Hibernate 3.2.4.sp1 with Annotations 3.3.0 And Validator 3.0.0 MySQL 5.0.42 Reporter: John Aylward receive following exception: org.hibernate.QueryException: number of select types did not match those for insert [INSERT INTO ProviderInvoiceLineItem (amount,billingAccount,circuit,description,invoice,type) SELECT pili.amount,pili.billingAccount,pili.circuit,pili.description,:newInvoice,pili.type) FROM com.cicat.bedrock.billing.model.ProviderInvoiceLineItem pili WHERE pili.invoice = :oldInvoice] exception should be that token ')' is not excepected near "pili.type" Should not have gotten as far as it did, should have blown up on parsing the HQL -- 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

15 years, 8 months

5
16
0 / 0

[Hibernate-JIRA] Created: (HHH-4085) Specifying a select clause triggers the "query specified join fetching, but the owner..." exception

by Kent Tong (JIRA)

Specifying a select clause triggers the "query specified join fetching, but the owner..." exception --------------------------------------------------------------------------------------------------- Key: HHH-4085 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4085 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.2 Environment: Kubuntu 9.04 Reporter: Kent Tong An Order contains some OrderItem's. Each OrderItem contains a Product and a quantity. To retrieve the Orders, The following HQL works: Code: from Order o left join fetch o.items i join fetch i.product However, if I specify the select clause: Code: select o from Order o left join fetch o.items i join fetch i.product Then Hibernate will return an error: Code: Exception in thread "main" org.hibernate.QueryException: query specified join fetching, but the owner of the fetched association was not present in the select list [FromElement{explicit,not a collection join,fetch join,fetch non-lazy properties,classAlias=null,role=null,tableName=Product,tableAlias=product2_,origin=items items1_,colums={items1_.p_id ,className=lab3.Product}}] [select o from lab3.Order o left join fetch o.items i join fetch i.product] at org.hibernate.hql.ast.tree.SelectClause.initializeExplicitSelectClause(SelectClause.java:217) at org.hibernate.hql.ast.HqlSqlWalker.useSelectClause(HqlSqlWalker.java:727) at org.hibernate.hql.ast.HqlSqlWalker.processQuery(HqlSqlWalker.java:551) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:645) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:251) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:183) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:134) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:101) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:94) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1650) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.hibernate.context.ThreadLocalSessionContext$TransactionProtectionWrapper.invoke(ThreadLocalSessionContext.java:342) at $Proxy0.createQuery(Unknown Source) at lab3.OnlineStoreApp.run(OnlineStoreApp.java:32) at lab3.OnlineStoreApp.main(OnlineStoreApp.java:14) The test code is shown below: Code: package lab3; import java.util.List; import org.hibernate.Session; import org.hibernate.SessionFactory; import org.hibernate.cfg.Configuration; public class OnlineStoreApp { private SessionFactory factory; private Session session; public static void main(String[] args) { new OnlineStoreApp().run(); } public OnlineStoreApp() { Configuration cfg = new Configuration(); cfg.configure(); factory = cfg.buildSessionFactory(); } @SuppressWarnings("unchecked") private void run() { session = factory.getCurrentSession(); session.beginTransaction(); Order o = new Order(); o.getItems().add(new OrderItem(new Product("p1"), 10)); o.getItems().add(new OrderItem(new Product("p2"), 20)); session.save(o); List<Order> orders = session .createQuery( "select o from Order o left join fetch o.items i join fetch i.product") .list(); System.out.println(orders.size()); session.getTransaction().commit(); } } package lab3; import java.util.ArrayList; import java.util.List; public class Order { private Long internalId; private List<OrderItem> items; public Order() { items = new ArrayList<OrderItem>(); } public Long getInternalId() { return internalId; } public void setInternalId(Long internalId) { this.internalId = internalId; } public List<OrderItem> getItems() { return items; } public void setItems(List<OrderItem> items) { this.items = items; } } package lab3; public class OrderItem { private Product product; private int qty; public OrderItem() { } public OrderItem(Product product, int qty) { this(); this.product = product; this.qty = qty; } public Product getProduct() { return product; } public void setProduct(Product product) { this.product = product; } public int getQty() { return qty; } public void setQty(int qty) { this.qty = qty; } } package lab3; public class Product { private Long internalId; private String name; public Product() { } public Product(String name) { this(); this.name = name; } public Long getInternalId() { return internalId; } public void setInternalId(Long internalId) { this.internalId = internalId; } public String getName() { return name; } public void setName(String name) { this.name = name; } } <?xml version="1.0"?> <!DOCTYPE hibernate-configuration PUBLIC "-//Hibernate/Hibernate Configuration DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-configuration-3.0.dtd"> <hibernate-configuration> <session-factory> <property name="hibernate.connection.url">jdbc:h2:tcp://localhost/~/test</property> <property name="hibernate.connection.driver_class">org.h2.Driver</property> <property name="hibernate.connection.username">sa</property> <property name="hibernate.connection.password"></property> <property name="hibernate.hbm2ddl.auto">update</property> <property name="hibernate.dialect">org.hibernate.dialect.H2Dialect</property> <property name="hibernate.current_session_context_class">thread</property> <property name="hibernate.show_sql">false</property> <mapping resource="Product.hbm.xml"/> <mapping resource="Order.hbm.xml"/> </session-factory> </hibernate-configuration> <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping> <class name="lab3.Order" table="orders"> <id name="internalId"> <generator class="sequence"></generator> </id> <list name="items" cascade="save-update"> <key column="o_id"></key> <list-index column="idx"></list-index> <composite-element class="lab3.OrderItem"> <many-to-one name="product" column="p_id" cascade="save-update"></many-to-one> <property name="qty"></property> </composite-element> </list> </class> </hibernate-mapping> <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping> <class name="lab3.Product"> <id name="internalId"> <generator class="sequence"></generator> </id> <property name="name"></property> </class> </hibernate-mapping> -- 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

15 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2374) setFetchMode() ignore incorect path

by Baptiste MATHUS (JIRA)

setFetchMode() ignore incorect path ----------------------------------- Key: HHH-2374 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2374 Project: Hibernate3 Type: Bug Versions: 3.2.0.ga Environment: All DB I guess Reporter: Baptiste MATHUS This bug report is in fact a copy of the one that was already present in H2 : http://opensource.atlassian.com/projects/hibernate/browse/HB-763 . It does not seem to have changed in H3. When calling setFetchMode("path", FetchMode.JOIN) on a criteria, even if the path is not correct, Hibernate does not complain. Its behaviour seems to be to simply ignore this bad path. I guess this should throw an exception. In fact, the bad thing of ignoring bad path is that if the developer was wrong specifying the path (typo, for example), then the join simply won't happen :-/. I wrote a very simple testcase : public void testFindClients() { Session session = HibernateUtil.currentSession(); session.beginTransaction(); Client c = (Client)session.createCriteria(Client.class).setFetchMode("foo", FetchMode.JOIN) .setFetchMode("foo.bar", FetchMode.JOIN).uniqueResult(); session.getTransaction().commit(); } My Client class has some relationships with other classes, but obviously none named "foo". The code above just issue the following select : select this_.ID as ID0_0_, this_.nom as nom0_0_, this_.prenom as prenom0_0_, this_.age as age0_0_ from Client this_ Thanks again for your great work, guys! -- 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

15 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2344) Persistent collection queued operation ignored with lazy inverse one-to-many collection.

by Sebastien Robert (JIRA)

Persistent collection queued operation ignored with lazy inverse one-to-many collection. ---------------------------------------------------------------------------------------- Key: HHH-2344 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2344 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: Hibernate 3.2.1 Reporter: Sebastien Robert I load an Object that contains a lazy inverse collection (one-to-many). Hibernate wrap my collection with a PersistentMap There is objects in the collection in the database but in my case the PersistentMap is not yet initialized. I perform a remove operation on the persistentMap with a known key of one of the objects. The map is not initialized (and the relation is an inverse one-to-many) so the map queue the removeOperation. I perform a get operation with the same key and the value is still returned. If we look closer at what happened in the PersistentMap, it's look like this. //***** public Object remove(Object key) { if ( isPutQueueEnabled() ) { // This returned true, the // map is not yet // initialized Object old = readElementByIndex( key ); // This method triggered // an initialization of the // map. // Queued operation are // processed in the after // init method queueOperation( new Remove( key, old ) ); // The remove operation // is queued. return old; } .... //******* When i perform the get operation on the map the map is now initialized. The get is processed by the underlying map and the value is returned. The queued operation is completely ignored. Currently i fixed my code by performing a containsKey before the remove . The containsKey initialize the map and then the remove do not queue the operation. But by looking at all the PersistentCollection it seem that i may have the same problem using put and remove with other persistentCollection. -- 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

15 years, 8 months

7
10
0 / 0

[Hibernate-JIRA] Created: (HHH-5017) "SettingsFactory" no longer checks for presence of "supportsGetGeneratedKeys" before calling it

by Steve Perkins (JIRA)

"SettingsFactory" no longer checks for presence of "supportsGetGeneratedKeys" before calling it ----------------------------------------------------------------------------------------------- Key: HHH-5017 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5017 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Reporter: Steve Perkins A number of users are experiencing Hibernate failures when using various combinations of Oracle JDBC driver versions and JDK versions. A sample stacktrace is below: Initial SessionFactory Creaion Failed.java.lang.AbstractMethodError: oracle.jdbc.driver.OracleDatabaseMetaData.supportsGetGeneratedKeys()Z Exception in thread "main" java.lang.ExceptionInInitializerError at HibernateUtil.buildSessionFactory(HibernateUtil.java:27) at HibernateUtil.<clinit>(HibernateUtil.java:17) at EvenManager.createAndStoreEvent(EvenManager.java:33) at EvenManager.main(EvenManager.java:26) Caused by: java.lang.AbstractMethodError: oracle.jdbc.driver.OracleDatabaseMetaData.supportsGetGeneratedKeys()Z at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:123) at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2119) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2115) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1339) at HibernateUtil.buildSessionFactory(HibernateUtil.java:23) ... 3 more The basic issue is that the "supportsGetGeneratedKeys" method does not exist on the "oracle.jdbc.driver.OracleDatabaseMetaData" JDBC driver class for many versions of Oracle. Even if you use the "hibernate.jdbc.use_get_generated_keys" config property, Hibernate still makes a call to that method and execution still fails. Up until version 3.2.7.GA of Hibernate, the code checked for the presence of "supportsGetGeneratedKeys" prior to calling it. The problem emerged with version 3.3.2.GA, where now Hibernate just calls the method without first verifying that it exists. If there was no functional reason for removing this safety-check, can we please re-insert it to prevent such failures? A discussion of this issue can be found on the forums at: https://forum.hibernate.org/viewtopic.php?f=1&t=1002210&p=2427193#p2427193 -- 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

15 years, 8 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-135) Create a RAMDirectoryProvider from an existing Lucene file index

by Hardy Ferentschik (JIRA)

Create a RAMDirectoryProvider from an existing Lucene file index ---------------------------------------------------------------- Key: HSEARCH-135 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-135 Project: Hibernate Search Issue Type: New Feature Components: directory provider Reporter: Hardy Ferentschik It would be nice to have the ability to use a Lucene RAM index which gets constucted from an existing Lucene file based indexed. For example in an JMS setup the master could create a file based Lucene index, share it out to the slaves which in turn use this file based index to populate a RAM index. This would give you the best of two worlds. Not sure how hard it would be to implement this in an unclustered environment. -- 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

15 years, 8 months

3
19
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-278) Create a Search Statistic JMX Bean

by Hardy Ferentschik (JIRA)

Create a Search Statistic JMX Bean ---------------------------------- Key: HSEARCH-278 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-278 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Provide access to some statistical data like number of documents, etc via JMX Bean similar to the one in Hibernate Core. Maybe also allow to trigger reindexing and purging. The interface could even allow for query execution ?! -- 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

15 years, 8 months

3
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3627) String Scalar Function CONCAT and operator || in HQL not working correctly with numeric values

by Eric Belanger (JIRA)

String Scalar Function CONCAT and operator || in HQL not working correctly with numeric values ---------------------------------------------------------------------------------------------- Key: HHH-3627 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3627 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.1 Environment: MS SQL 2005 Reporter: Eric Belanger Priority: Minor Since HQL translate the CONCAT and || to + in SQL, numeric values get added together instead of being converted to String and concanated. Also causes problems when concatenating a numeric with a string. SELECT CONCAT(1, 2) FROM... Returns 3 instead of '12' SELECT CONCAT('TWO', 2) FROM ... java.sql.SQLException: Conversion failed when converting the varchar value 'TWO' to data type int. java.sql.SQLException: Conversion failed when converting the varchar value 'TWO' to data type int. at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:365) at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2781) at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2224) at net.sourceforge.jtds.jdbc.TdsCore.isDataInResultSet(TdsCore.java:792) at net.sourceforge.jtds.jdbc.JtdsResultSet.<init>(JtdsResultSet.java:146) at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQLQuery(JtdsStatement.java:424) at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeQuery(JtdsPreparedStatement.java:693) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:186) at org.hibernate.loader.Loader.getResultSet(Loader.java:1787) at org.hibernate.loader.Loader.doQuery(Loader.java:674) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader.Loader.doList(Loader.java:2220) at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2104) at org.hibernate.loader.Loader.list(Loader.java:2099) at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:378) at org.hibernate.hql.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:338) at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:172) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1121) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:79) at org.hibernate.console.HQLQueryPage.getList(HQLQueryPage.java:50) at org.hibernate.eclipse.console.views.QueryPageViewer$ContentProviderImpl.getElements(QueryPageViewer.java:114) at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:937) at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:693) at org.eclipse.jface.viewers.AbstractTableViewer.getRawChildren(AbstractTableViewer.java:1071) at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:871) at org.eclipse.jface.viewers.StructuredViewer.getSortedChildren(StructuredViewer.java:994) at org.eclipse.jface.viewers.AbstractTableViewer.internalRefreshAll(AbstractTableViewer.java:685) at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:633) at org.eclipse.jface.viewers.AbstractTableViewer.internalRefresh(AbstractTableViewer.java:620) at org.eclipse.jface.viewers.AbstractTableViewer$2.run(AbstractTableViewer.java:576) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1368) at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1330) at org.eclipse.jface.viewers.AbstractTableViewer.inputChanged(AbstractTableViewer.java:574) at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:251) at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1606) at org.hibernate.eclipse.console.views.QueryPageViewer.createTable(QueryPageViewer.java:218) at org.hibernate.eclipse.console.views.QueryPageViewer.createControl(QueryPageViewer.java:197) at org.hibernate.eclipse.console.views.QueryPageViewer.<init>(QueryPageViewer.java:154) at org.hibernate.eclipse.console.views.QueryPageTabView.rebuild(QueryPageTabView.java:114) at org.hibernate.eclipse.console.views.QueryPageTabView$1.contentsChanged(QueryPageTabView.java:78) at org.hibernate.eclipse.console.views.QueryPageTabView$1.intervalAdded(QueryPageTabView.java:88) at javax.swing.AbstractListModel.fireIntervalAdded(AbstractListModel.java:130) at org.hibernate.console.QueryPageModel.add(QueryPageModel.java:67) at org.hibernate.console.KnownConfigurations$1.queryPageCreated(KnownConfigurations.java:90) at org.hibernate.console.ConsoleConfiguration.fireQueryPageCreated(ConsoleConfiguration.java:419) at org.hibernate.console.ConsoleConfiguration.access$5(ConsoleConfiguration.java:415) at org.hibernate.console.ConsoleConfiguration$4.execute(ConsoleConfiguration.java:391) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:65) at org.hibernate.console.ConsoleConfiguration.executeHQLQuery(ConsoleConfiguration.java:383) at org.hibernate.eclipse.hqleditor.HQLEditor.executeQuery(HQLEditor.java:406) at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:72) at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:52) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:56) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:546) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:490) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:443) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1101) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3319) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2389) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2353) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2219) at org.eclipse.ui.internal.Workbench$4.run(Workbench.java:466) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:289) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:461) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:106) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:169) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:106) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:76) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:363) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:176) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:508) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:447) at org.eclipse.equinox.launcher.Main.run(Main.java:1173) -- 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

15 years, 8 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2068) TransientObjectException : object references an unsaved transient instance ...

by Ales PROCHAZKA (JIRA)

TransientObjectException : object references an unsaved transient instance ... ------------------------------------------------------------------------------ Key: HHH-2068 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2068 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr4 Environment: Windows, Hibernate 3.2.0.cr4, Oracle 9.2.0.1 Reporter: Ales PROCHAZKA Attachments: XTest.zip I found this problem: If I create new object 'o1', which associate another persistent object 'o2' and by calling saveOrUpdate Hibernate throws PropertyValueException, then when I corresct this property and try call saveOrUpdate in another session (in which 'o2' was not saved or loaded) Hibernate throws TransientObjectException. Please see attached code :-) This is a log : Hibernate: select hibernate_sequence.nextval from dual Hibernate: insert into T_TEST (A_POKUS, A_POKUS_LONG, CID, PK) values (?, ?, 3, ?) Hibernate: insert into T_TEST3 (PK) values (?) Hibernate: select hibernate_sequence.nextval from dual Hibernate: select hibernate_sequence.nextval from dual org.hibernate.PropertyValueException: not-null property references a null or transient value: persistent.Test5.pokus at org.hibernate.engine.Nullability.checkNullability(Nullability.java:72) at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:284) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:180) at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:121) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:186) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:175) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:98) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSaveOrUpdate(SessionImpl.java:509) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:501) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:497) at test.MainTest.test(MainTest.java:71) at test.MainTest.main(MainTest.java:42) org.hibernate.TransientObjectException: persistent.Test3 at org.hibernate.engine.ForeignKeys.getEntityIdentifierIfNotUnsaved(ForeignKeys.java:216) at org.hibernate.type.EntityType.getIdentifier(EntityType.java:108) at org.hibernate.type.ManyToOneType.isDirty(ManyToOneType.java:221) at org.hibernate.type.TypeFactory.findDirty(TypeFactory.java:476) at org.hibernate.persister.entity.AbstractEntityPersister.findDirty(AbstractEntityPersister.java:2900) at org.hibernate.event.def.DefaultFlushEntityEventListener.dirtyCheck(DefaultFlushEntityEventListener.java:474) at org.hibernate.event.def.DefaultFlushEntityEventListener.isUpdateNecessary(DefaultFlushEntityEventListener.java:197) at org.hibernate.event.def.DefaultFlushEntityEventListener.onFlushEntity(DefaultFlushEntityEventListener.java:120) at org.hibernate.event.def.AbstractFlushingEventListener.flushEntities(AbstractFlushingEventListener.java:195) at org.hibernate.event.def.AbstractFlushingEventListener.flushEverythingToExecutions(AbstractFlushingEventListener.java:76) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:26) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:993) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:340) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at test.MainTest.test(MainTest.java:87) at test.MainTest.main(MainTest.java:42) Thanx -- 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

15 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-755) Cascade operations don't take affect through a @CollectionOfElements

by Chris L (JIRA)

Cascade operations don't take affect through a @CollectionOfElements -------------------------------------------------------------------- Key: ANN-755 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-755 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Environment: Hibernate 3.2.5 Reporter: Chris L Consider having three classes. The first is an @Entity called a View, which has a collection of @Embeddable Column objects. Column objects have an @ManyToOne relationship to a @Entity called Filter. The three classes have a very straightforward mapping: @javax.persistence.Entity() @Entity(dynamicUpdate=true) @Table(name="PORTFOLIO_VIEW") class View { .... @JoinTable(name="PORTFOLIO_VIEW_COLUMN",joinColumns={@JoinColumn(name="VIEW_ID")}) @IndexColumn(name="COLUMN_INDEX") @Cascade(CascadeType.ALL) @LazyCollection(LazyCollectionOption.FALSE) @CollectionOfElements private List<Column> columns; .... } @Embeddable class Column { .... @ManyToOne(fetch=FetchType.EAGER) @Cascade(CascadeType.ALL) @JoinColumn(name="FILTER") @Target(FilterImpl.class) private Filter filter; .... } @javax.persistence.Entity @Entity(dynamicUpdate=true) @Table(name="FILTER") @DiscriminatorColumn(name="CLASS_NAME",length=255) abstract class FilterImpl { .... } When I create a new view, with a new column and filter object, I should be able to save the view and have the @Cascade settings on the @CollectionOfElements and the @ManyToOne inside of Column take affect, and save the Filter. Instead, I get a TransientObjectException because the Filter hasn't been saved yet. I know I could work around this by either making Column an Entity, or by adding code to save the Filter before saving the View. But it seems to me this is reasonable usage of an Embeddable. This issue was originally part of a forum post http://forum.hibernate.org/viewtopic.php?t=987977 -- 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

15 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5142) Exception when initializing lazy @ManyToMany indexed collection containing not audited entities

by Vladimir Klyushnikov (JIRA)

Exception when initializing lazy @ManyToMany indexed collection containing not audited entities ----------------------------------------------------------------------------------------------- Key: HHH-5142 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5142 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.1 Environment: Hibernate Core 3.5.1 Reporter: Vladimir Klyushnikov Priority: Blocker Attachments: testcase.zip Hi, I am getting exception when executing following code: {code} @Entity @Audited public class M2MIndexedListEntity { ... @ManyToMany(cascade = CascadeType.ALL) @OrderColumn(name="sortOrder") @Audited(targetAuditMode = RelationTargetAuditMode.NOT_AUDITED) private List<NotAuditedEntity> list = new ArrayList<NotAuditedEntity>(); } @Entity public class NotAuditedEntity { ... } ... M2MIndexedListEntity entity = (M2MIndexedListEntity) auditReader.createQuery() .forRevisionsOfEntity(M2MIndexedListEntity.class, true, false) .getSingleResult(); assertEquals(1,entity.getList().size()); {code} Stack trace is the following: {code} java.lang.ClassCastException: testapp.NotAuditedEntity cannot be cast to java.util.Map at org.hibernate.envers.entities.mapper.relation.lazy.initializor.ListCollectionInitializor.addToCollection(ListCollectionInitializor.java:67) at org.hibernate.envers.entities.mapper.relation.lazy.initializor.ListCollectionInitializor.addToCollection(ListCollectionInitializor.java:39) at org.hibernate.envers.entities.mapper.relation.lazy.initializor.AbstractCollectionInitializor.initialize(AbstractCollectionInitializor.java:67) at org.hibernate.envers.entities.mapper.relation.lazy.proxy.CollectionProxy.checkInit(CollectionProxy.java:50) at org.hibernate.envers.entities.mapper.relation.lazy.proxy.CollectionProxy.size(CollectionProxy.java:55) {code} I've attached a full test case. Unzip it, run *mvn test* and see test failing -- 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

15 years, 8 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3334) Cascading breaks if parent table doesn't have Auto-inc

by Wallace Wadge (JIRA)

Cascading breaks if parent table doesn't have Auto-inc ------------------------------------------------------ Key: HHH-3334 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3334 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.3.0.CR1, 3.2.6, 3.2.5, 3.2.4.sp1 Environment: tested on MySql, and hibernate versions (with annotations) v3.2.4 to 3.3.0CR1 Reporter: Wallace Wadge (reposting here from forum) Consider: - a table with an assigned PK (i.e. not auto-increment), let's call this "A" - Another table ("B") linked to the table listed above but with it's PK set to auto-increment. Now if you try to save B with cascading switched on, it will break. From the little debugging I've done it looks like: a) hibernate detects that A needs to be saved first, but puts it into some sort of queue. b) when it hits B, it short-circuits this save queue and tries to save B immediately so as to obtain a PK reference for B. This fails since A hasn't been yet been saved so it's link is still null. Schema used is listed below (MySQL): ---- CREATE DATABASE `jira` /*!40100 DEFAULT CHARACTER SET latin1 */; DROP TABLE IF EXISTS `jira`.`parent`; CREATE TABLE `jira`.`parent` ( `parent_id` int(10) unsigned NOT NULL, PRIMARY KEY (`parent_id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; DROP TABLE IF EXISTS `jira`.`child`; CREATE TABLE `jira`.`child` ( `child_id` int(10) unsigned NOT NULL auto_increment, `parent_id` int(10) unsigned NOT NULL, PRIMARY KEY (`child_id`), KEY `FK_child_1` (`parent_id`), CONSTRAINT `FK_child_1` FOREIGN KEY (`parent_id`) REFERENCES `parent` (`parent_id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; -- 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

15 years, 8 months

4
22
0 / 0

[Hibernate-JIRA] Created: (HHH-5197) Envers documentation doesn't include the correct configuration when using Hibernate directly

by Miguel Almeida (JIRA)

Envers documentation doesn't include the correct configuration when using Hibernate directly -------------------------------------------------------------------------------------------- Key: HHH-5197 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5197 Project: Hibernate Core Issue Type: Patch Reporter: Miguel Almeida Attachments: quickstart.xml.diff In Envers' Documentation, the quickstart section refers that one should add some properties: <property name="hibernate.ejb.event.post-insert"... However, in my Test Case, using Hibernate directly, this configuration didn't work. What worked was the configuration in https://forum.hibernate.org/viewtopic.php?p=2420963&sid=f4687909b0137dfc1... - adding the listeners. I propose the attached diff to the quickstart.xml documentation section to include this configuration. -- 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

15 years, 8 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5224) Hibernate ENVERS Doest Work on MERGE Entity

by Dyego Souza do Carmo (JIRA)

Hibernate ENVERS Doest Work on MERGE Entity ------------------------------------------- Key: HHH-5224 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5224 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.5.1 Environment: Windows, Glassfish V3 , MySQL 5.0 , Connector/J 5.x , Hibernate 3.5.1-Final Reporter: Dyego Souza do Carmo Priority: Critical Attachments: EnversHibernate3.5Bug.rar I'm created a simple project to example this... One method CALL .persist , and a REVISION is "saved" in _version table (ohhh , thats WORK !!!) But on other method, call .MERGE , and ENVERS ignore the merge... and not "save" a revision on _version table... This is a BIG problem , because the UPDATE REVISION is crucial... Please SAVE ME !!!!!! -- 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

15 years, 8 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5048) @Type ignored by envers?, whole transaction rollbacked, but applcation continues, without warning

by Donovan (JIRA)

@Type ignored by envers?,whole transaction rollbacked, but applcation continues, without warning ------------------------------------------------------------------------------------------------ Key: HHH-5048 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5048 Project: Hibernate Core Issue Type: Bug Components: envers Reporter: Donovan Priority: Blocker Attachments: EuroTypeTest_for_envers.patch Following problem occurs when i audited my entity with a custom type: Testcase included, as a svn-patch on the current envers - trunk. Envers does not use my @Type to save the revision, because it is not a org.hibernate.usertype.UserType, but a extension of org.hibernate.type.DoubleType. This give me a readable exception, i can live with that, but still a bug. Implementing my EuroType as a org.hibernate.usertype.UserType resolves my immediate problem. The worst is that a exception is thrown, transaction is rollbacked, but the exception does not reach my application. As in the testcase, the problem is detected(too late) by query on the entity and you get NULL; Thats why i gave it the prio blocker. Adding @NotAudited on "Euro component" gives you a green test, Envers SHOULD NOT influent this, or at least throw a exception, so i get notified that my entity is not saved or created. -- 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

15 years, 8 months

2
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-207) Hibernate 3.5.1-Final cannot parse order-by fragment

by Vladimir Kobetic (JIRA)

Hibernate 3.5.1-Final cannot parse order-by fragment ---------------------------------------------------- Key: BVAL-207 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-207 Project: Bean Validation Issue Type: Bug Environment: Hibernate 3.5.1-Final MySQL 5.0 Spring 2.5 Reporter: Vladimir Kobetic Priority: Critical When upgrading from Hibernate 3.2.5.ga to the newest Hibernate 3.5.1-Final with the newest build-with dependent libraries an error occurs during initial phase of launching application. I tried to build and run with all libraries from lib directory from Hibernate zip download. The order-by clause is configured in hbm.xml: <hibernate-mapping> <class name="com.test.Object" table="err"> <id name="id" type="java.lang.Long"> <generator class="native" /> </id> <set name="history" table="history" lazy="true" order-by="timestamp desc" cascade="all-delete-orphan"> <key column="object_id" /> <one-to-many class="com.test.Event" /> </set> </class> </hibernate-mapping> The exception is: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in class path resource [applicationContext-dao-hibernate.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Unable to parse order-by fragment Caused by: org.hibernate.HibernateException: Unable to parse order-by fragment at org.hibernate.sql.ordering.antlr.OrderByFragmentTranslator.render(OrderByFragmentTranslator.java:66) at org.hibernate.sql.Template.renderOrderByStringTemplate(Template.java:310) at org.hibernate.persister.collection.AbstractCollectionPersister.<init>(AbstractCollectionPersister.java:557) at org.hibernate.persister.collection.OneToManyPersister.<init>(OneToManyPersister.java:84) at org.hibernate.persister.PersisterFactory.createCollectionPersister(PersisterFactory.java:104) and more... Caused by: java.lang.NullPointerException at org.hibernate.sql.ordering.antlr.OrderByFragmentParser.resolveFunction(OrderByFragmentParser.java:115) at org.hibernate.sql.ordering.antlr.GeneratedOrderByFragmentParser.expression(GeneratedOrderByFragmentParser.java:619) at org.hibernate.sql.ordering.antlr.GeneratedOrderByFragmentParser.sortKey(GeneratedOrderByFragmentParser.java:337) at org.hibernate.sql.ordering.antlr.GeneratedOrderByFragmentParser.sortSpecification(GeneratedOrderByFragmentParser.java:248) at org.hibernate.sql.ordering.antlr.GeneratedOrderByFragmentParser.orderByFragment(GeneratedOrderByFragmentParser.java:192) at org.hibernate.sql.ordering.antlr.OrderByFragmentTranslator.render(OrderByFragmentTranslator.java:60) ... 38 more -- 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

15 years, 9 months

7
15
0 / 0

[Hibernate-JIRA] Created: (HHH-5151) Update tutorial section of Hibernate Core to use Annotations

by Emmanuel Bernard (JIRA)

Update tutorial section of Hibernate Core to use Annotations ------------------------------------------------------------ Key: HHH-5151 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5151 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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

15 years, 9 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5152) Update Configuration section to reflect Hibernate Annotations and Core documentation

by Emmanuel Bernard (JIRA)

Update Configuration section to reflect Hibernate Annotations and Core documentation ------------------------------------------------------------------------------------ Key: HHH-5152 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5152 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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

15 years, 9 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4441) SessionImpl serialization violates java serialization spec

by Paul Ferraro (JIRA)

SessionImpl serialization violates java serialization spec ---------------------------------------------------------- Key: HHH-4441 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4441 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0.Beta-1, 3.3.2 Reporter: Paul Ferraro Attachments: patch.txt The private serialization methods of org.hibernate.impl.SessionImpl must call default[Read|Write]Object() on the object input/output stream before any custom de/serialization logic. According to the Java serialization spec: http://java.sun.com/javase/6/docs/platform/serialization/spec/output.html... "The class's writeObject method, if implemented, is responsible for saving the state of the class. Either ObjectOutputStream's defaultWriteObject or writeFields method must be called once (and only once) before writing any optional data that will be needed by the corresponding readObject method to restore the state of the object; even if no optional data is written, defaultWriteObject or writeFields must still be invoked once. If defaultWriteObject or writeFields is not invoked once prior to the writing of optional data (if any), then the behavior of instance deserialization is undefined in cases where the ObjectInputStream cannot resolve the class which defined the writeObject method in question." http://java.sun.com/javase/6/docs/platform/serialization/spec/input.html#... "The readObject method of the class, if implemented, is responsible for restoring the state of the class. The values of every field of the object whether transient or not, static or not are set to the default value for the fields type. Either ObjectInputStream's defaultReadObject or readFields method must be called once (and only once) before reading any optional data written by the corresponding writeObject method; even if no optional data is read, defaultReadObject or readFields must still be invoked once." One consequence of this spec violation is that you cannot use JBoss Marshalling to serialize a session. For details, see: https://jira.jboss.org/jira/browse/JBMAR-67 Patch attached. -- 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

15 years, 9 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-4443) Allow generic handling of any Hibernate type for post-insert generated identifiers

by Steve Ebersole (JIRA)

Allow generic handling of any Hibernate type for post-insert generated identifiers ---------------------------------------------------------------------------------- Key: HHH-4443 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4443 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.5 See HB-92 for the original request. Much of the discussion unfortunately occurred in a private email thread with the original requester, but here is the proposed solution: Steve Ebersole <steve(a)hibernate.org> wrote: The "more correct" solution is along the lines a contract to allow the type to handle this like you said. I'm thinking something like an optional interface for the type to publish that fact: public interface ResultSetIdentifierConsumer { public Serializable consumeIdentifier(ResultSet resultSet); } then IdentifierGeneratorFactory (called IdentifierGeneratorHelper now btw) can say: public static Serializable get(ResultSet rs, Type type) ... { if ( type instanceof ResultSetIdentifierConsumer ) { return ( ( ResultSetIdentifierConsumer ) type ).consumeIdentifier( rs ); } Class clazz = type.getReturnedClass(); if ( clazz == Long.class ) { return new Long( rs.getLong( 1 ) ); } else if ( clazz == Integer.class ) { return new Integer( rs.getInt( 1 ) ); } else if ( clazz == Short.class ) { return new Short( rs.getShort( 1 ) ); } else if ( clazz == String.class ) { return rs.getString( 1 ); } else { throw ... } } and you can define a type : public class MyCustomLongIdType ... implements ResultSetIdentifierConsumer ... { public Serializable consumeIdentifier(ResultSet resultSet) { return new MyCustomLongId( resultSet.getLong( 1 ) ); } ... } -- 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

15 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5264) withClause doesn't take into account parent classes

by Douglas Ferguson (JIRA)

withClause doesn't take into account parent classes --------------------------------------------------- Key: HHH-5264 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5264 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.5.1 Reporter: Douglas Ferguson withClause will create and ON clause in the SQL that uses and alias that isn't available, i.e. it is referenced 1 line before it is defined. Consider the following classes A, B, C C is a sub class of B. If I create a criteria on A. Then use critera.createAlias("a.c", "c", LEFT_JOIN, Restrictions.in(c.id, 123)); Then I get the following in my query left outer join C c on ... and b.id = 123 < alias b used before it is defined. left outer join B b on ... -- 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

15 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3006) ConcurrentModificationException in AbstractBatcher results in infinite loop

by Stefan Hauk (JIRA)

ConcurrentModificationException in AbstractBatcher results in infinite loop --------------------------------------------------------------------------- Key: HHH-3006 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3006 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5, 3.2.4.sp1, 3.2.4, 3.2.3 Environment: Hibernate 3.2.5.ga MySQL 5.0.42 Reporter: Stefan Hauk Priority: Minor Here is a piece of code from org.hibernate.jdbc.AbstractBatcher's closeStatements() method: Iterator iter = resultSetsToClose.iterator(); while ( iter.hasNext() ) { try { logCloseResults(); ( (ResultSet) iter.next() ).close(); } catch (SQLException e) { // no big deal log.warn("Could not close a JDBC result set", e); } catch (Throwable e) { // sybase driver (jConnect) throwing NPE here in certain cases log.warn("Could not close a JDBC result set", e); } } resultSetsToClose.clear(); In case there is a ConcurrentModificationException thrown when iterating over the resultSetsToClose HashSet the exception will be caught by the catch(Throwable) clause. However, the iteration may continue infinitely because of the corrupted HashSet. This pegs one CPU and logs the following stack trace over and over again: 28/11 20:16:50 WARN AbstractBatcher [resin-tcp-connection-myserver:6001-15] Could not close a JDBC result set java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(HashMap.java:841) at java.util.HashMap$KeyIterator.next(HashMap.java:877) at org.hibernate.jdbc.AbstractBatcher.closeStatements(AbstractBatcher.java:314) at org.hibernate.jdbc.ConnectionManager.cleanup(ConnectionManager.java:382) at org.hibernate.jdbc.ConnectionManager.close(ConnectionManager.java:324) at org.hibernate.impl.SessionImpl.close(SessionImpl.java:298) at org.springframework.orm.hibernate3.SessionFactoryUtils.closeSession(SessionFactoryUtils.java:774) at org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.closeSession(OpenSessionInViewFilter.java:252) at org.springframework.orm.hibernate3.support.OpenSessionInViewFilter.doFilterInternal(OpenSessionInViewFilter.java:183) at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:75) at com.caucho.server.dispatch.FilterFilterChain.doFilter(FilterFilterChain.java:70) at com.caucho.server.cache.CacheFilterChain.doFilter(CacheFilterChain.java:188) at com.caucho.server.webapp.WebAppFilterChain.doFilter(WebAppFilterChain.java:178) at com.caucho.server.dispatch.ServletInvocation.service(ServletInvocation.java:229) at com.caucho.server.hmux.HmuxRequest.handleRequest(HmuxRequest.java:419) at com.caucho.server.port.TcpConnection.run(TcpConnection.java:389) at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:492) at com.caucho.util.ThreadPool.run(ThreadPool.java:425) at java.lang.Thread.run(Thread.java:595) The catch(Throwable) block was added in Hibernate 3.2.3 if I saw that correctly. Apparently the reason was to catch a NPE thrown by a sybase driver here, but catching Throwable catches more than that and produces this side-effect. Now I do realize that the ConcurrentModificationException might be caused by not using Hibernate in a correct way, but I haven't determined the cause for it yet. However, I do think that Hibernate should fail more gracefully than it currently does. -- 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

15 years, 9 months

14
20
0 / 0

[Hibernate-JIRA] Created: (HHH-2708) attribute order-by don't devlared on hibernate-mapping-3.0.dtd

by Sunteya (JIRA)

attribute order-by don't devlared on hibernate-mapping-3.0.dtd -------------------------------------------------------------- Key: HHH-2708 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2708 Project: Hibernate3 Issue Type: Bug Affects Versions: 3.2.4.sp1 Reporter: Sunteya HHH-1414 bug already fixed order-by attribute on the <many-to-many/> element but the dtd file don't allow use order-by attribute. -- 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

15 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-719) Upload Hibernate-Annotations 3.3.1.GA to central maven repository

by Andreas Schildbach (JIRA)

Upload Hibernate-Annotations 3.3.1.GA to central maven repository ----------------------------------------------------------------- Key: ANN-719 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-719 Project: Hibernate Annotations Issue Type: Improvement Affects Versions: 3.3.1.GA Reporter: Andreas Schildbach Could you upload Hibernate-Annotations 3.3.1.GA to the central maven repository? Would you also add the sources? -- 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

15 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5180) StandardQueryCache.get() does not handle EntityNotFoundException for natural key lookups

by Gail Badner (JIRA)

StandardQueryCache.get() does not handle EntityNotFoundException for natural key lookups ---------------------------------------------------------------------------------------- Key: HHH-5180 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5180 Project: Hibernate Core Issue Type: Bug Components: caching (L2), core Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.6 This is the same as HHH-3478, except it's for 3.6. In 3.6 we can use JPA exceptions, so the fix will be different. -- 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

15 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2980) Error "org.hibernate.HibernateException: cannot simultaneously fetch multiple bags" not specific enough

by Dobes Vandermeer (JIRA)

Error "org.hibernate.HibernateException: cannot simultaneously fetch multiple bags" not specific enough ------------------------------------------------------------------------------------------------------- Key: HHH-2980 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2980 Project: Hibernate3 Issue Type: Improvement Affects Versions: 3.2.5 Reporter: Dobes Vandermeer When I get this exception: org.hibernate.HibernateException: cannot simultaneously fetch multiple bags I don't know what to do except google. Why not spruce it up a little to say something like: For class X, multiple collection fields are marked for eager fetching: a, b, c; this is not supported by Hibernate in releases after 3.2.x -- 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

15 years, 9 months

6
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3191) QueryPlanCache cache size

by Julien Kirch (JIRA)

QueryPlanCache cache size ------------------------- Key: HHH-3191 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3191 Project: Hibernate3 Issue Type: Improvement Components: query-hql Affects Versions: 3.2.6 Environment: Hibernate 3.2.6, all platform Reporter: Julien Kirch On a large application with many (currently 696) named queries in hbm files we have a performance issue with the QueryPlanCache cache size: The SoftLimitMRUCache used in the QueryPlanCache use 128 hard references, the other being soft references, and this number is hardcoded. As we have much more querries in the application, we spend much time in recompiling the same queries when they are evicted from the cache. As the QueryPlanCache has a SessionFactoryImplementor as parameter, adding a new parameter to define the query cache plan size would be trivial; what's your opinion about 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

15 years, 9 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4627) Configurable Query Plan Cache

by Frank Daspro (JIRA)

Configurable Query Plan Cache ----------------------------- Key: HHH-4627 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4627 Project: Hibernate Core Issue Type: New Feature Components: query-hql Affects Versions: 3.2.2 Environment: Hibernate 3.22 GA, Oracle 10G database Reporter: Frank Daspro Our application heavily uses dynamic sql some of which are highly parameterised and with many permutations. Out of neccessity we also have a very large JVM heap space (12GB). As a result we end up with a very large memory utilisation for the Query Plan cache. From a recent memory dump it was noted the QueryPlanCache had 25000 entries and consuming 2.5GB of heap space. Our full Garbage collections end up taking longer than it would normally take with a smaller QueryPlanCache. I understand via a related issue (http://opensource.atlassian.com/projects/hibernate/browse/HHH-3191) there is a hard limit of 128 entries, and an endless soft limit which is only garbage collected during a full garbage collection. It would be nice if the following features could be added: 1) Configuration options to specify the hard and soft limits (with a 0 to disable or similar). 2) Configurable at the query level such that specific queries can be excluded from the the QueryPlanCache. eg. something like hibernateQuery.setParsedHQLCacheable(false). -- 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

15 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2431) QueryPlanCache grows without bound. Eventually gets OutOfMemoryException

by Eric Goff (JIRA)

QueryPlanCache grows without bound. Eventually gets OutOfMemoryException -------------------------------------------------------------------------- Key: HHH-2431 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2431 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.2 Environment: all versions, all platforms Reporter: Eric Goff Every time you execute a query, and that query does not match any existing queries in the QueryPlanCache, that query is *always* added to the Query Plan Cache, along with a lot of various antlr stuff. There seems to be no way to control it. Minimally, there should be some sort of heap of query plans where the least used query plan is ejected when the cache reaches it max size. The cache size should, of course, be user configurable. -- 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

15 years, 9 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HBX-1000) Problem with PostgreSQL using uppercase letters in tables

by Ruediger Engelberger (JIRA)

Problem with PostgreSQL using uppercase letters in tables --------------------------------------------------------- Key: HBX-1000 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1000 Project: Hibernate Tools Issue Type: Bug Components: reverse-engineer Affects Versions: 3.2.beta11 Environment: Hibernate 3.2.5.ga, Hibernate Tools 3.2.0 beta9a, PostgreSql 8.2, postgresql-8.2-506.jdbc3.jar, Eclipse 3.3.0, all running on Windows XP at the moment (including PostgreSql) Reporter: Ruediger Engelberger I have problems using Hibernate tools when using upper case letters in a PostgreSQL database. I can configure Hibernate Tools for my local PostgreSql installation without any problems. I can access the table structure in the view Hibernate Configurations and do reverse engineering by creating XML mappings and beans. No problem. But when I'm using upper case characters in table names Hibernate Tools can't access the table structures any more. Hibernate Configuration shows the tables, but when I want to see the columns, it doesn't show anything. Reverse engineering also doesn't work any more. So, the following works: TABLE cms_clusterMessage pk_clustermessageid fk_clusternodeid messagetype messagedetail The following doesn't work: TABLE cms_clusterMessage PK_ClusterMessageId FK_ClusterNodeId MessageType MessageDetail I tried to use different JDBC drivers because I thought it could be a bug of the driver. But it wasn't. -- 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

15 years, 9 months

5
10
0 / 0

[Hibernate-JIRA] Created: (HHH-4904) result of 'join fetch' query is incorrectly cached

by Geoff Crain (JIRA)

result of 'join fetch' query is incorrectly cached -------------------------------------------------- Key: HHH-4904 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4904 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.3.2 Environment: hibernate 3.3.2, EhCache 1.2.3, postgresql, mysql and hsql Reporter: Geoff Crain Im not sure if this is either a bug, a missing option, or just an option that i can't find. Im using hibernate 3.3.2, and EhCache 1.2.3. I recently had an issue where objects in collections were getting dropped from the cache. After a long investigation, I found that it was because a "join fetch" query was being made on the parent object. http://docs.jboss.org/hibernate/core/3. ... ryhql.html This meant that only a subset of the child elements were selected. If the collection was not already in the cache, the "incomplete" result of this query is put into it. Every subsequent call to the parent element (wanting the "full" set of children) would only get this incomplete version. When the incomplete version drops out of the cache (after 24 hours) everything goes back to normal. So, is it a bug? Should hibernate (or ehcache) not be caching this "incomplete" collection? Or is there some way to tell hibernate that it is an incomplete collection _so_ that it doesnt get cached? * If you believe this to be a bug, I will provide a working example. * If you think this is actually an EhCache bug, tell me and Ill raise it there -- 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

15 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5091) Unidirectional One-To-Many relationship with foreign key mapping doesn't work

by Juergen Zimmermann (JIRA)

Unidirectional One-To-Many relationship with foreign key mapping doesn't work ----------------------------------------------------------------------------- Key: HHH-5091 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5091 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.0-Final Reporter: Juergen Zimmermann I've the following 2 tables (in PostgreSQL) in a one-to-many relationship with foreign key mapping: CREATE TABLE bestellung( b_id BIGSERIAL NOT NULL PRIMARY KEY, version INTEGER DEFAULT 0, kunde_fk BIGINT NOT NULL REFERENCES kunde(k_id) ); CREATE TABLE bestellposition( bp_id BIGSERIAL NOT NULL PRIMARY KEY, version INTEGER DEFAULT 0, artikel_fk BIGINT NOT NULL REFERENCES artikel(a_id), anzahl SMALLINT NOT NULL, bestellung_fk BIGINT NOT NULL REFERENCES bestellung(b_id) ); Now the 2 JPA entity classes: // owner class @Entity @Table(name="bestellung") public class Bestellung implements java.io.Serializable { @Id @GeneratedValue(generator="bestellung_sequence_name") @SequenceGenerator(name="bestellung_sequence_name", sequenceName="bestellung_b_id_seq", allocationSize=1) @Column(name="b_id", nullable=false) private Long id = null; @Version private int version = 0; // bidirectional @ManyToOne(optional=false) @JoinColumn(name="kunde_fk") @NotNull(message="{bestellverwaltung.bestellung.kunde.notNull}") private Kunde kunde; // unidirectional and cascading persist @OneToMany(fetch=EAGER, cascade={PERSIST, REMOVE}, orphanRemoval=true) @JoinColumn(name="bestellung_fk") @OrderBy("id ASC") @NotEmpty(message="{bestellverwaltung.bestellung.bestellpositionen.notEmpty}") private List<Bestellposition> bestellpositionen; } // dependant class @Entity @Table(name="bestellposition") public class Bestellposition implements java.io.Serializable { @Id @GeneratedValue(generator="bestellposition_sequence_name") @SequenceGenerator(name="bestellposition_sequence_name", sequenceName="bestellposition_bp_id_seq", allocationSize=1) @Column(name="bp_id", nullable=false) private Long id = null; @Version private int version = 0; @Column(nullable=false) @Min(value=ANZAHL_MIN, message="{bestellverwaltung.bestellposition.anzahl.min}") private short anzahl = 1; @ManyToOne(optional=false) @JoinColumn(name="artikel_fk") @NotNull(message="{bestellverwaltung.bestellposition.artikel.notNull}") private Artikel artikel; } Inside the owner class the dependent class is declared with cascade=PERSIST (see above). When I try to create a persistent entity of class Bestellung (owner class) then the generated SQL statement is wrong because the foreign key ("bestellung_fk") for the owner record is missing. insert into bestellposition(anzahl, artikel_fk, version, bp_id) 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

15 years, 9 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3478) @NaturalId queries not flushed from cache using EntityManager.remove(); exception results from query

by Elias Ross (JIRA)

@NaturalId queries not flushed from cache using EntityManager.remove(); exception results from query ---------------------------------------------------------------------------------------------------- Key: HHH-3478 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3478 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.0.SP1 Environment: Java 1.5, Maven dependencies: [INFO] (root) [INFO] | \- org.hibernate:hibernate-validator:jar:3.1.0.GA:compile [INFO] +- commons-codec:commons-codec:jar:1.3:compile [INFO] +- javax.persistence:persistence-api:jar:1.0:compile [INFO] +- org.hibernate:hibernate-core:jar:3.3.0.SP1:compile [INFO] | +- antlr:antlr:jar:2.7.6:compile [INFO] | +- commons-collections:commons-collections:jar:3.1:compile [INFO] | \- dom4j:dom4j:jar:1.6.1:compile [INFO] | \- xml-apis:xml-apis:jar:1.0.b2:compile [INFO] +- org.hibernate:hibernate-annotations:jar:3.4.0.GA:compile [INFO] | \- org.hibernate:ejb3-persistence:jar:1.0.2.GA:compile [INFO] +- org.hibernate:hibernate-commons-annotations:jar:3.3.0.ga:compile [INFO] | \- org.hibernate:hibernate:jar:3.2.1.ga:compile [INFO] | +- net.sf.ehcache:ehcache:jar:1.2.3:compile [INFO] | +- asm:asm-attrs:jar:1.5.3:compile [INFO] | +- cglib:cglib:jar:2.1_3:compile [INFO] | \- asm:asm:jar:1.5.3:compile [INFO] +- org.hibernate:hibernate-entitymanager:jar:3.4.0.GA:compile [INFO] | \- javassist:javassist:jar:3.4.GA:compile [INFO] +- javax.transaction:jta:jar:1.0.1B:compile [INFO] +- org.slf4j:slf4j-api:jar:1.5.2:compile [INFO] +- org.slf4j:slf4j-log4j12:jar:1.5.2:compile [INFO] +- hsqldb:hsqldb:jar:1.8.0.10:test [INFO] \- junit:junit:jar:4.4:test Reporter: Elias Ross Attachments: Dummy.java, DummyTest.java, persistence.xml See attached test case and entity. Current Result: javax.persistence.EntityNotFoundException: Unable to find com.autodesk.lbs.cs.Dummy with id 1 at org.hibernate.ejb.Ejb3Configuration$Ejb3EntityNotFoundDelegate.handleEntityNotFound(Ejb3Configuration.java:113) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:171) 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:905) at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:873) at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:590) at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:219) at org.hibernate.cache.StandardQueryCache.get(StandardQueryCache.java:155) at org.hibernate.loader.Loader.getResultFromQueryCache(Loader.java:2184) at org.hibernate.loader.Loader.listUsingQueryCache(Loader.java:2147) at org.hibernate.loader.Loader.list(Loader.java:2117) at org.hibernate.loader.criteria.CriteriaLoader.list(CriteriaLoader.java:118) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1596) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:306) at org.hibernate.impl.CriteriaImpl.uniqueResult(CriteriaImpl.java:328) at com.autodesk.lbs.cs.DummyTest.naturalKeyCachedQuery(DummyTest.java:69) at com.autodesk.lbs.cs.DummyTest.naturalKeyCachedQuery(DummyTest.java:61) at com.autodesk.lbs.cs.DummyTest.testQuery(DummyTest.java:49) It's expected that a cache invalidation occurs with an entity's natural key when it is removed. I'll investigate a solution. -- 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

15 years, 9 months

4
14
0 / 0

[Hibernate-JIRA] Created: (HHH-4798) Add Envers manual to Hibernate core documentation

by Erik-Berndt Scheper (JIRA)

Add Envers manual to Hibernate core documentation ------------------------------------------------- Key: HHH-4798 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4798 Project: Hibernate Core Issue Type: Improvement Components: envers Affects Versions: 3.5.0-Beta-3 Reporter: Erik-Berndt Scheper Now that Envers has been added to hibernate core, the Envers manual should be integrated into the Hibernate reference documentation. The Table of Contents of the latest version (3.5.0 Beta 3) does not even mention the Envers module. -- 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

15 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5259) Invalid reflection optimization configuration property name in Hibernate documentation.

by Kirill Klenski (JIRA)

Invalid reflection optimization configuration property name in Hibernate documentation. --------------------------------------------------------------------------------------- Key: HHH-5259 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5259 Project: Hibernate Core Issue Type: Task Components: documentation Reporter: Kirill Klenski Priority: Minor I think this was already pointed out, but Hibernate documentation still misguides people to use the no-longer supported hibernate.cglib.use_reflection_optimizer property in Table 3.7. Miscellaneous Properties (http://docs.jboss.org/hibernate/core/3.5/reference/en/html/session-config...). The real name for the property is: hibernate.bytecode.use_reflection_optimizer. -- 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

15 years, 9 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2510) override equals()/hashCode() in AliasToBeanResultTransformer

by Maxim Gordienko (JIRA)

override equals()/hashCode() in AliasToBeanResultTransformer ------------------------------------------------------------ Key: HHH-2510 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2510 Project: Hibernate3 Type: Improvement Versions: 3.2.2 Reporter: Maxim Gordienko AliasToBeanResultTransformer whould override equals()/hashCode() to allow convenient second level query caching. Now the only way is to maintain single transformer instance per bean class to allow query cache hit. -- 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

15 years, 9 months

3
9
0 / 0

[Hibernate-JIRA] Created: (ANN-663) @JoinColumn must be set for @AssociationOverride to work

by Bas van den Berg (JIRA)

@JoinColumn must be set for @AssociationOverride to work -------------------------------------------------------- Key: ANN-663 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-663 Project: Hibernate Annotations Issue Type: Improvement Components: binder Affects Versions: 3.3.0.ga Environment: Hibernate 3.2 , MySQL Reporter: Bas van den Berg Priority: Minor The following error is given when overiding the joincolumn which has not been set explicitly: Illegal attempt to define a @JoinColumn with a mappedBy association see http://forum.hibernate.org/viewtopic.php?t=960621&highlight= -- 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

15 years, 9 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HHH-5212) Alter SQLFunction contract to be more flexible

by Steve Ebersole (JIRA)

Alter SQLFunction contract to be more flexible ---------------------------------------------- Key: HHH-5212 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5212 Project: Hibernate Core Issue Type: Improvement Components: core, query-criteria, query-hql Reporter: Steve Ebersole The SQLFunction contract currently combines contextual information (render/getReturnType) and non-contextual (aka non-changing) information (hasArguments/hasParenthesesIfNoArguments). An example I just ran into where separating these would have been nice is in HHH-5173. Some dialects return the argument data type when applying the AVG() function. That is problematic for INTEGER values because the decimal portion gets dropped. On those databases one would need to CAST() the argument to get the correct behavior. However, again, this is only necessary based on the argument type. If the argument type is already a non-integer the cast is uneeded. Proposal (as always name subject to change/suggestion): {code} interface SQLFunction { public boolean hasArguments(); public boolean hasParenthesesIfNoArguments(); public RenderingContext getRenderingContext(Type columnType, SessionFactoryImplementor factory); public static interface RenderingContext { public Type getReturnType(); public String render(List args); } } {code} I used SessionFactoryImplementor as the argument to getRenderingContext, but the current getReturnType accepts a Mapping. Is there really ever a time when we call that method when we do not have a SessionFactory? My usage search shows no usages of this method passing in a Configuration (which is the other Mapping implementor aside from SessionFactory). -- 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

15 years, 9 months

3
14
0 / 0

[Hibernate-JIRA] Created: (HHH-4011) ChainedPropertyAccessor is not serializable, which breaks caching to disk and replicated caches.

by Ryan Dearing (JIRA)

ChainedPropertyAccessor is not serializable, which breaks caching to disk and replicated caches. ------------------------------------------------------------------------------------------------ Key: HHH-4011 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4011 Project: Hibernate Core Issue Type: Bug Components: caching (L2), core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1 (not checked on 3.3.2) Reporter: Ryan Dearing ChainedPropertyAccessor is used by AliasToBeanResultTransformer. Since ChainedPropertyAccessor is not serializable any cacheable queries using AliasToBeanResultTransformer break during cache replication. For example, this query cannot be replicated or cached to disk: session.createQuery("select foo").setResultTransformer(new AliasToBeanResultTransformer(SimpleCount.class)).setCacheable(true).list(); A workaround is to make these queries not cacheable for now. -- 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

15 years, 9 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-3526) hbm2ddl.auto validate error on sequences in different schema

by Andres Galeano (JIRA)

hbm2ddl.auto validate error on sequences in different schema ------------------------------------------------------------ Key: HHH-3526 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3526 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1 GA & Oracle 9i Database Reporter: Andres Galeano Hello, My situation is that I have an persistent object and matching hbm that reference a table and sequence in a different oracle schema. When I set the "hibernate.hbm2ddl.auto" property to "validate", a hibernate error message claims that the sequence does not exist, although it does and is accessible. >From stepping through the code in class: org.hibernate.tool.hbm2ddl.DatabaseMetadata in method: public boolean isSequence(Object key) This code parses the 'key', in this case sequence name, by '.' and searches to see if the last element is contained in the list of sequences. So if I prefix my sequence name with the schema name it belongs to, it's ignored. This doesn't seem right to me. The code also seems to ignore the "schema" attribute of the "hibernate-mapping/class" element when validating sequence generators. To me this seems wrong as well. Since the 'list of sequences' is only for the current schema, at least in the case of Oracle9Dialect, the validate fails, even though the sequence does exist and seems to be properly specified to me. ------------------------------------------------------------ Excerpt from my hbm.xml file: ------------------------------------------------------------ ... ... <hibernate-mapping> <class name="bus.Accesspurpose" table="ACCESSPURPOSE" schema="WISH"> <id name="id" type="int"> <column name="ACCESSPURPOSEID" /> <generator class="sequence">  <param name="sequence">WISH.SEQ_ACCESSPURPOSEID</param> </generator> </id> ... ... ------------------------------------------------------------ Full stack trace. ------------------------------------------------------------ 2008-10-08 10:47:15,375 ERROR Thread-1 org.springframework.web.context.ContextLoader - Context initialization failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'SecurityManager' defined in class path resource [bus/wishdb-service-context.xml]: Cannot resolve reference to bean 'SecurityManagerDao' while setting bean property 'securityManagerDao'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'SecurityManagerDao' defined in class path resource [db/wishdb-data-context.xml]: Cannot resolve reference to bean 'mySessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mySessionFactory' defined in class path resource [db/pp-app-data-context.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Missing sequence or table: WISH.SEQ_ACCESSPURPOSEID at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1172) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:940) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:437) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164) at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:400) at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:736) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:369) at org.springframework.web.context.ContextLoader.createWebApplicationContext(ContextLoader.java:261) at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:199) at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:45) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4216) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:760) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:740) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:544) at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:825) at org.apache.catalina.startup.HostConfig.deployWARs(HostConfig.java:714) at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:490) at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1138) at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311) at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:120) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1022) at org.apache.catalina.core.StandardHost.start(StandardHost.java:736) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:448) at org.apache.catalina.core.StandardServer.start(StandardServer.java:700) at org.apache.catalina.startup.Catalina.start(Catalina.java:552) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433) Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'SecurityManagerDao' defined in class path resource [db/wishdb-data-context.xml]: Cannot resolve reference to bean 'mySessionFactory' while setting bean property 'sessionFactory'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mySessionFactory' defined in class path resource [db/pp-app-data-context.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Missing sequence or table: WISH.SEQ_ACCESSPURPOSEID at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:275) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:104) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1172) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:940) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:437) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:269) ... 41 more Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'mySessionFactory' defined in class path resource [db/pp-app-data-context.xml]: Invocation of init method failed; nested exception is org.hibernate.HibernateException: Missing sequence or table: WISH.SEQ_ACCESSPURPOSEID at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1260) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:438) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory$1.run(AbstractAutowireCapableBeanFactory.java:383) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:353) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:245) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:169) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:242) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:164) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:269) ... 53 more Caused by: org.hibernate.HibernateException: Missing sequence or table: WISH.SEQ_ACCESSPURPOSEID at org.hibernate.cfg.Configuration.validateSchema(Configuration.java:1127) at org.hibernate.tool.hbm2ddl.SchemaValidator.validate(SchemaValidator.java:139) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:349) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1327) at org.springframework.orm.hibernate3.LocalSessionFactoryBean.newSessionFactory(LocalSessionFactoryBean.java:799) at org.springframework.orm.hibernate3.LocalSessionFactoryBean.buildSessionFactory(LocalSessionFactoryBean.java:733) at org.springframework.orm.hibernate3.AbstractSessionFactoryBean.afterPropertiesSet(AbstractSessionFactoryBean.java:211) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1288) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1257) ... 62 more ----------------------------------------------------------- _________________ Thanks, - Andy See also the forums post: http://forum.hibernate.org/viewtopic.php?t=991326 -- 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

15 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-604) There is no annotation to specify default value for a column

by Nicolae Bucalaete (JIRA)

There is no annotation to specify default value for a column ------------------------------------------------------------ Key: ANN-604 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-604 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Reporter: Nicolae Bucalaete Priority: Critical In hibernate annotation you can't specify default value for a column. If you use xml files for mapping then you have this feature. I consider that this is a major problem with annotation. -- 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

15 years, 9 months

15
17
0 / 0

[Hibernate-JIRA] Created: (HHH-3231) org.hibernate.id.enhanced.TableGenerator throws "IllegalArgumentException: alias not found: tbl" under Oracle

by Király Attila (JIRA)

org.hibernate.id.enhanced.TableGenerator throws "IllegalArgumentException: alias not found: tbl" under Oracle ------------------------------------------------------------------------------------------------------------- Key: HHH-3231 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3231 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Hibernate 3.2.6GA, Oracle 10g Reporter: Király Attila Attachments: hibernate_etg_ora.zip org.hibernate.id.enhanced.TableGenerator always throws the following exception if I want to save a new object to Oracle: java.lang.IllegalArgumentException: alias not found: tbl at org.hibernate.sql.ForUpdateFragment.<init>(ForUpdateFragment.java:36) at org.hibernate.dialect.Dialect.applyLocksToSql(Dialect.java:970) at org.hibernate.id.enhanced.TableGenerator.configure(TableGenerator.java:194) at org.hibernate.id.IdentifierGeneratorFactory.create(IdentifierGeneratorFactory.java:104) I attach an example to this case. The example is loosely based on the tutorial example, that comes with Hibernate. It contains a Person object that is saved to db using the enhanced.TableGenerator as id generator. To keep the zip small only the jars of jdbc driver are included, the jars needed from hibernate distribution are listed in lib/readme.txt. The zip also contains a modified TableGenerator that works with Oracle. This version was made by forum user stomp and more information about it can be read here: http://forum.hibernate.org/viewtopic.php?t=980933 It changes the 194th row of TableGenerator from this.query = dialect.applyLocksToSql( query, lockMap, CollectionHelper.EMPTY_MAP ); to this.query = dialect.applyLocksToSql( query, lockMap, Collections.singletonMap("tbl", new String[] {valueColumnName}) ); -- 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

15 years, 9 months

5
11
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-533) Use Hibernate Search bridge system to convert input

by Emmanuel Bernard (JIRA)

Use Hibernate Search bridge system to convert input --------------------------------------------------- Key: HSEARCH-533 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-533 Project: Hibernate Search Issue Type: Sub-task Environment: Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard -- 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

15 years, 9 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-530) Entity analyzers (aka scoped analyzers) improperly return random analyzers on field not marked as TOKENIZED

by Emmanuel Bernard (JIRA)

Entity analyzers (aka scoped analyzers) improperly return random analyzers on field not marked as TOKENIZED ----------------------------------------------------------------------------------------------------------- Key: HSEARCH-530 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-530 Project: Hibernate Search Issue Type: Bug Components: analyzer Affects Versions: 3.2.0.Final Reporter: Emmanuel Bernard Fix For: 3.3.0 A field not marked as TOKENIZED should return a pass through analyzer instance. -- 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

15 years, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-534) circular graphs of IndexedEmbedded might break MassIndexer

by Sanne Grinovero (JIRA)

circular graphs of IndexedEmbedded might break MassIndexer ---------------------------------------------------------- Key: HSEARCH-534 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-534 Project: Hibernate Search Issue Type: Bug Components: massindexer Affects Versions: 3.2.0.Final, 3.2.0.CR1, 3.2.0.Beta1 Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.3.0 I could reproduce the following forum post: https://forum.hibernate.org/viewtopic.php?f=9&t=1004813 It appears that if two root entities which are sequentially indexed by the MassIndexer are sharing pointers to a same EntityKey but where loaded from different threads, they will attempt to add to the same session different instances for the same identifier. -- 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

15 years, 9 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-508) Support query on multiple fields

by Emmanuel Bernard (JIRA)

Support query on multiple fields -------------------------------- Key: HSEARCH-508 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-508 Project: Hibernate Search Issue Type: Sub-task Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard -- 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

15 years, 9 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-509) Add support for all() query and all except ones

by Emmanuel Bernard (JIRA)

Add support for all() query and all except ones ----------------------------------------------- Key: HSEARCH-509 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-509 Project: Hibernate Search Issue Type: Sub-task Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard -- 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

15 years, 9 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-414) Add support for a Lucene query builder using a fluent API

by Emmanuel Bernard (JIRA)

Add support for a Lucene query builder using a fluent API --------------------------------------------------------- Key: HSEARCH-414 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-414 Project: Hibernate Search Issue Type: New Feature Components: query Reporter: Emmanuel Bernard Fix For: 3.2.0.Beta3 -- 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

15 years, 9 months

2
10
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-397) Allow classes to be lazily added to the configuration

by Emmanuel Bernard (JIRA)

Allow classes to be lazily added to the configuration ----------------------------------------------------- Key: HSEARCH-397 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-397 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard Assignee: Sanne Grinovero Assigning Sanne to pick his interest ;) Infinispan needs a way to add new classes lazily, ie after the SearchFactory initialization. Today's initialization cannot ensure that because we assume a single thread inits everything before freezing the state and then support multiple thread. We need to explore the idea of making the configuration mutable but not suffering too much of the thread-safety implications. We also should allow to remove a class from the configuration. -- 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

15 years, 9 months

3
16
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-487) Find why the zh-CN translation fails

by Emmanuel Bernard (JIRA)

Find why the zh-CN translation fails ------------------------------------ Key: HSEARCH-487 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-487 Project: Hibernate Search Issue Type: Bug Components: documentation Affects Versions: 3.2.0.Beta1 Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik -- 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

15 years, 9 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-507) Rename exact() to keywords() and move fuzzy() and wildcard() back as suboperations of keywords()

by Emmanuel Bernard (JIRA)

Rename exact() to keywords() and move fuzzy() and wildcard() back as suboperations of keywords() ------------------------------------------------------------------------------------------------ Key: HSEARCH-507 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-507 Project: Hibernate Search Issue Type: Sub-task Components: query Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard http://pastebin.com/u7ucjRDR -- 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

15 years, 9 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-523) Build the distribution package with the docs in the same directory structure as on the docs server

by Hardy Ferentschik (JIRA)

Build the distribution package with the docs in the same directory structure as on the docs server -------------------------------------------------------------------------------------------------- Key: HSEARCH-523 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-523 Project: Hibernate Search Issue Type: Task Components: build Affects Versions: 3.2.0.Final Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.3.0 The distribution contains the documentation under {{docs/api}} and {{docs/manual}}. On the documentation server we have {{reference/en}}. This should be aligned which will help for example to just use rsync to update the online docs. At the same time we have to investigate why the docs don't get automatically built via {{release:perform}}. -- 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

15 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3771) Best pactice for equals implementation?

by Samppa Saarela (JIRA)

Best pactice for equals implementation? --------------------------------------- Key: HHH-3771 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3771 Project: Hibernate Core Issue Type: New Feature Components: core, documentation Reporter: Samppa Saarela When domain model contains even one lazy reference to an object, default equals fails when it's compared to a) the actual implementation returned by Session.get/load or b) other proxies (at least of different supertype). Overriding equals on a class that uses surrogate id is not that simple. However there is a simple solution to this problem: In domain class, override equals like this: public boolean equals(Object obj) { return this == getImplementation(obj); } public static Object getImplementation(Object obj) { if (obj instanceof HibernateProxy) { return ((HibernateProxy) obj).getHibernateLazyInitializer().getImplementation(); } else { return obj; } } This should result always in comparing object references of actual instances and thus preserve symmetry. It's understandable that you don't wan to publish that kind of getImplementation utility e.g. in Hibernate, but maybe you could support this more directly by implementing Hibernate.equals(Object o1, Object o2) -- 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

15 years, 9 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5246) Addition of withClause for DetachedCriteria

by Shawn Clowater (JIRA)

Addition of withClause for DetachedCriteria ------------------------------------------- Key: HHH-5246 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5246 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.5.2 Reporter: Shawn Clowater Priority: Minor Attachments: hhh-5246.patch HHH-2308 added the ability to specify a withClause to the createCriteria and createAlias methods but were never added to the DetachedCriteria API. I can see that being handy for us in the future so voila, patch. -- 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

15 years, 9 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5097) Bug in ParameterizedFunctionExpression with two or more parameters: IllegalArgumentException

by Max Hartmann (JIRA)

Bug in ParameterizedFunctionExpression with two or more parameters: IllegalArgumentException -------------------------------------------------------------------------------------------- Key: HHH-5097 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5097 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Final Environment: oracle 10g, hibernate 3.5 Reporter: Max Hartmann If you call CriteriaBuilder.function() respectively "ParameterizedFunctionExpression" with two or more arguments you get an IllegalArgumentException. I think the bug is here: protected void renderArguments(StringBuilder buffer, CriteriaQueryCompiler.RenderingContext renderingContext) { for ( Expression argument : argumentExpressions ) { buffer.append( ( (Renderable) argument ).render( renderingContext ) ); } } The arguments are not seperated by comma. Exception: Exception in thread "main" java.lang.IllegalArgumentException: org.hibernate.hql.ast.QuerySyntaxException: unexpected token: : near line 1, column 37 [select TO_CHAR(generatedAlias0.date1:param0) from test.server.TestBean as generatedAlias0] at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1166) at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1112) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:315) at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:154) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:432) at test.server.TestApp.main(TestApp.java:28) Caused by: org.hibernate.hql.ast.QuerySyntaxException: unexpected token: : near line 1, column 37 [select TO_CHAR(generatedAlias0.date1:param0) from test.server.TestBean as generatedAlias0] at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:54) at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:47) at org.hibernate.hql.ast.ErrorCounter.throwQueryException(ErrorCounter.java:82) at org.hibernate.hql.ast.QueryTranslatorImpl.parse(QueryTranslatorImpl.java:284) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:182) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:136) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:101) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:98) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1760) at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:297) ... 3 more Code: EntityManagerFactory factory = Persistence.createEntityManagerFactory("userDatabase"); EntityManager em = factory.createEntityManager(); CriteriaBuilder cb = em.getCriteriaBuilder(); CriteriaQuery<String> createQuery = cb.createQuery(String.class); Root<TestBean> from = createQuery.from(TestBean.class); Expression<String> param = cb.literal("DD.MM.YYYY"); createQuery.select(cb.function("TO_CHAR", String.class, from.get(TestBean_.date1), param)); List<String> resultList = em.createQuery(createQuery).getResultList(); -- 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

15 years, 10 months

3
13
0 / 0

[Hibernate-JIRA] Created: (HHH-3908) Expose way to fully control fetching in native-sql queries in API

by Steve Ebersole (JIRA)

Expose way to fully control fetching in native-sql queries in API ----------------------------------------------------------------- Key: HHH-3908 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3908 Project: Hibernate Core Issue Type: New Feature Components: core Reporter: Steve Ebersole Fix For: 3.5 Currently, in order to fully control fetching in native-sql queries, users must revert to using a named sql query (at least the xml, not sure if the annotations variety supports as well). We alreasy have all the objects/contracts in place to handle this for the named queries, just need to clean-up and properly document them. The current API calls to deal with this are the overloaded SQLQuery#addJoin methods. Ideally I'd see these changed to return the representation of the join-fetch to be configured; but addJoin already defines a return : the query itself :( So probably we will need new methods like addFetch: 1) public JoinFetch addFetch(String alias, String ownerAlias, String ownerProperty) 2) public JoinFetch addFetch(String alias, String ownerAlias, String ownerProperty, LockMode lockMode) interface JoinFetch { public void addPropertyMapping(String propertyName, String sqlAlias); } This can be expanded to the "root returns" as well (currently the overloaded #addEntity methods): public RootReturn addRoot(String alias, Class entityClass) etc... ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Example ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SQLQuery query = session.createSQLQuery( "select c.cust_id as cid, " + " c.cust_name as cname, " + " o.order_id as oid, " + " o.order_num as onum " + " from customer c " + " inner join orders o " + " on c.cust_id = o.cust_id" ); query.addRoot( "c", Customer.class ) .addPropertyMapping( "id", "cid" ) .addPropertyMapping( "name", "cname" ); query.addFetch( "o", "c", "orders" ) .addPropertyMapping( "id", "oid" ) .addPropertyMapping( "orderNumber", "onum" ); ... -- 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

15 years, 10 months

2
11
0 / 0

[Hibernate-JIRA] Created: (HHH-2350) 2nd level cache broken for inverse bidirectional one-to-many relation

by Burkhard Graves (JIRA)

2nd level cache broken for inverse bidirectional one-to-many relation --------------------------------------------------------------------- Key: HHH-2350 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2350 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: Database: MySQL, HSQL, ... (seems not to be important) Reporter: Burkhard Graves Attachments: testcase.tgz When using "inverse" one-to-many relations as described in "2.4.6.2.3. Bidirectional association with indexed collections" (http://www.hibernate.org/hib_docs/annotations/reference/en/html/entity.ht...) hibernate is wrong when activating 2nd level cache. See the attached example (unzip in /usr/local/hibernate-annotations-3.2.1.GA, testname=org.hibernate.test.annotations.invonetomany.InverseOneToManyTest). More details can be found here: http://forum.hibernate.org/viewtopic.php?t=969456 (and also in InverseOneToManyTest.java). -- 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

15 years, 10 months

3
12
0 / 0

[Hibernate-JIRA] Created: (HHH-3001) The NoopOptimizer needs to be synchronized

by Maciej Baranowski (JIRA)

The NoopOptimizer needs to be synchronized ------------------------------------------ Key: HHH-3001 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3001 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1, 3.2.6 Environment: 3.2.6, 3.2.4sp1, Oracle Reporter: Maciej Baranowski When SequenceStyleGenerator is used with Oracle it uses by default NoopOptimizer. The optimizer is not thread-safe and causes constraint violation errors while inserting data into the database. -- 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

15 years, 10 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HHH-5181) Merge hibernate-annotations module code into hibernate-core

by Steve Ebersole (JIRA)

Merge hibernate-annotations module code into hibernate-core ----------------------------------------------------------- Key: HHH-5181 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5181 Project: Hibernate Core Issue Type: Task Components: annotations, core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6 Well technically pieces of it need to go different places. src/main/java -> hibernate-core src/main/test (all?) -> hibernate-testsuite src/main/docbook -> already being merged into main reference manual (emmanuel) -- 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

15 years, 10 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5254) Present document on Types as a separate chapter

by Steve Ebersole (JIRA)

Present document on Types as a separate chapter ----------------------------------------------- Key: HHH-5254 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5254 Project: Hibernate Core Issue Type: Task Components: core, documentation Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6 # general discussion of Types # standard "resolution" of Type to use # common Types scenarios; be sure to cover large character and binary data scenarios # providing custom types -- 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

15 years, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3279) create series of maven plugins offering functionality of the ant tools

by Steve Ebersole (JIRA)

create series of maven plugins offering functionality of the ant tools ---------------------------------------------------------------------- Key: HHH-3279 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3279 Project: Hibernate3 Issue Type: New Feature Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.3.0.CR2 -- 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

15 years, 10 months

3
14
0 / 0

[Hibernate-JIRA] Created: (HHH-3609) Invalid list re-ordering with IndexColumn and OneToMany association

by Martin Kovacik (JIRA)

Invalid list re-ordering with IndexColumn and OneToMany association ------------------------------------------------------------------- Key: HHH-3609 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3609 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: Hibernate 3.3.1, Hibernate Tools 3.2.0, H2 database 1.0.69 Reporter: Martin Kovacik I want to map unidirectional OneToMany ordered list using annotations. My mapping is: public class Invoice { // ... @OneToMany(cascade = CascadeType.ALL) @JoinTable( name = "INVOICE_ITEM", joinColumns = {@JoinColumn(name = "invoice_id")}, inverseJoinColumns = {@JoinColumn(name = "item_id")} ) @Cascade(value = org.hibernate.annotations.CascadeType.DELETE_ORPHAN) @IndexColumn(name = "item_order") private List<Item> items = new ArrayList<Item>(); } The mapping of Item is not important here because I just want the association from Invoice to collection of Items to be unidirectional. The problem what hbm2ddl generates: create table INVOICE_ITEM ( invoice_id int8 not null, item_id int8 not null, item_order int4 not null, primary key (invoice_id, item_order), unique (item_id) ); alter table INVOICE_ITEM add constraint FK89837AD3EDA329D foreign key (item_id) references ITEM; alter table INVOICE_ITEM add constraint FK89837AD76A8E2D7 foreign key (invoice_id) references INVOICE; Another problem is how hibernate handles list re-ordering. If I want to change the item order (by manipulating invoice.items list) and then persist the changes hibernate tries to execute following sql: update INVOICE_ITEM set item_id=2 where invoice_id=1 and item_order=0 update INVOICE_ITEM set item_id=1 where invoice_id=1 and item_order=1 However this causes DB to complain about unique item_id constraint (which was generated by hibernate). IMHO hibernate should update just the item_order column. I think that this bug is related to ANN-679 (http://opensource.atlassian.com/projects/hibernate/browse/ANN-679). -- 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

15 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2269) Many-to-one cascade fails with TransientObjectException if the inverse collection is marked CascadeType.DELETE_ORPHAN

by Edward Costello (JIRA)

Many-to-one cascade fails with TransientObjectException if the inverse collection is marked CascadeType.DELETE_ORPHAN --------------------------------------------------------------------------------------------------------------------- Key: HHH-2269 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2269 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2, 3.2.1 Environment: Using hibernate annotations. Reporter: Edward Costello Attachments: TestBidirectionalCascade.java When both a many-to-one (child) and it's inverse one-to-many collection (on parent) are cascading. Attempting to save a child directly and cascade the save to the parent throws a TransientObjectException if the parent's collection is mapped CascadeType.DELETE_ORPHAN. For Example, with the classes below: @Entity public class Parent { @OneToMany(mappedBy = "parent") @Cascade(value = {CascadeType.ALL, CascadeType.DELETE_ORPHAN}) Set<DeleteOrphanChild> deleteOrphanChildren; } @Entity public class DeleteOrphanChild { @ManyToOne @Cascade(value = CascadeType.ALL) Parent parent; } Calling session.save() with an instance of the parent will cascade the save to the child as expected. However, calling save on an instance of the child will throw the TransientObjectException below while attempting to cascade the save to the parent. org.hibernate.TransientObjectException: cascade.test.TestBidirectionalCascade$DeleteOrphanChild at org.hibernate.engine.ForeignKeys.getEntityIdentifierIfNotUnsaved(ForeignKeys.java:216) at org.hibernate.collection.AbstractPersistentCollection.getOrphans(AbstractPersistentCollection.java:889) at org.hibernate.collection.PersistentSet.getOrphans(PersistentSet.java:51) at org.hibernate.engine.CollectionEntry.getOrphans(CollectionEntry.java:350) at org.hibernate.engine.Cascade.deleteOrphans(Cascade.java:336) at org.hibernate.engine.Cascade.cascadeCollectionElements(Cascade.java:318) at org.hibernate.engine.Cascade.cascadeCollection(Cascade.java:185) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:160) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:108) at org.hibernate.engine.Cascade.cascade(Cascade.java:248) at org.hibernate.event.def.AbstractSaveEventListener.cascadeAfterSave(AbstractSaveEventListener.java:437) at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:326) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:180) at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:108) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:186) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:175) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:98) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSaveOrUpdate(SessionImpl.java:509) at org.hibernate.impl.SessionImpl.saveOrUpdate(SessionImpl.java:501) at org.hibernate.engine.CascadingAction$1.cascade(CascadingAction.java:134) at org.hibernate.engine.Cascade.cascadeToOne(Cascade.java:213) at org.hibernate.engine.Cascade.cascadeAssociation(Cascade.java:157) at org.hibernate.engine.Cascade.cascadeProperty(Cascade.java:108) at org.hibernate.engine.Cascade.cascade(Cascade.java:248) at org.hibernate.event.def.AbstractSaveEventListener.cascadeBeforeSave(AbstractSaveEventListener.java:412) at org.hibernate.event.def.AbstractSaveEventListener.performSaveOrReplicate(AbstractSaveEventListener.java:261) at org.hibernate.event.def.AbstractSaveEventListener.performSave(AbstractSaveEventListener.java:180) at org.hibernate.event.def.AbstractSaveEventListener.saveWithGeneratedId(AbstractSaveEventListener.java:108) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(DefaultSaveOrUpdateEventListener.java:186) at org.hibernate.event.def.DefaultSaveEventListener.saveWithGeneratedOrRequestedId(DefaultSaveEventListener.java:33) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.entityIsTransient(DefaultSaveOrUpdateEventListener.java:175) at org.hibernate.event.def.DefaultSaveEventListener.performSaveOrUpdate(DefaultSaveEventListener.java:27) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.onSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:70) at org.hibernate.impl.SessionImpl.fireSave(SessionImpl.java:537) at org.hibernate.impl.SessionImpl.save(SessionImpl.java:525) at org.hibernate.impl.SessionImpl.save(SessionImpl.java:521) If the DELETE_ORPHAN cascade is removed the save works fine. The attached test case runs against an in memory HSQLDB database. It contains 4 tests, the second test (testSaveChildDeleteOrphan) fails showing the above exception. The other three pass showing that cascading from the parent works and that cascading in both directions remove if the DELETE_ORPHAN cascade is removed. We've only tested this with annotations, we haven't tried to reproduce it using hibernate mapping files. -- 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

15 years, 10 months

4
9
0 / 0

[Hibernate-JIRA] Created: (HHH-4718) Select with subselect operands to a division gives NullPointerException on BinaryArithmeticOperatorNode

by Bruno Medeiros (JIRA)

Select with subselect operands to a division gives NullPointerException on BinaryArithmeticOperatorNode ------------------------------------------------------------------------------------------------------- Key: HHH-4718 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4718 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.2, 3.2.7 Environment: Any Reporter: Bruno Medeiros I tried to perform the following query: --------------------------------------------------------------- select new map( e as estacao, ( ( select count(c) from Chamada c where 1 = 1 and c.estacao = e and c.data >= :dataInicial and c.data <= :dataFinal ) / ( select count(c2) from Chamada c2 where 1 = 1 and c.data >= :dataInicial and c.data <= :dataFinal ) ) as quantidade ) from Estacao e -------------------------------------------------------------- That gives the following atack trace: -------------------------------------------------------------- Exception in thread "main" java.lang.NullPointerException at org.hibernate.hql.ast.tree.BinaryArithmeticOperatorNode.getRightHandOperand(BinaryArithmeticOperatorNode.java:185) at org.hibernate.hql.ast.tree.BinaryArithmeticOperatorNode.initialize(BinaryArithmeticOperatorNode.java:20) at org.hibernate.hql.ast.HqlSqlWalker.prepareArithmeticOperator(HqlSqlWalker.java:1011) at org.hibernate.hql.antlr.HqlSqlBaseWalker.arithmeticExpr(HqlSqlBaseWalker.java:2783) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectExpr(HqlSqlBaseWalker.java:2006) at org.hibernate.hql.antlr.HqlSqlBaseWalker.aliasedSelectExpr(HqlSqlBaseWalker.java:2057) at org.hibernate.hql.antlr.HqlSqlBaseWalker.constructor(HqlSqlBaseWalker.java:2226) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectExpr(HqlSqlBaseWalker.java:1952) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectExprList(HqlSqlBaseWalker.java:1825) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectClause(HqlSqlBaseWalker.java:1394) at org.hibernate.hql.antlr.HqlSqlBaseWalker.query(HqlSqlBaseWalker.java:553) at org.hibernate.hql.antlr.HqlSqlBaseWalker.selectStatement(HqlSqlBaseWalker.java:281) at org.hibernate.hql.antlr.HqlSqlBaseWalker.statement(HqlSqlBaseWalker.java:229) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:228) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:160) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:111) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:77) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:56) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:72) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:133) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:112) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1623) ------------------------------------------------------------------ If I select the operands separately and do the division in Java code the query works perfectly. -- 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

15 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5256) Update of Many-to-Many relationships not allways working (deletes records but doesn't insert them)

by Ignacio Larrañaga (JIRA)

Update of Many-to-Many relationships not allways working (deletes records but doesn't insert them) -------------------------------------------------------------------------------------------------- Key: HHH-5256 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5256 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.3.2 Environment: JBoss 5.1.0.GA / MySql 5.1 Reporter: Ignacio Larrañaga Priority: Critical Attachments: bug_test.jar I'm executing an update of the User entity and it deletes a relationship that must not change as it is not modified. It works well when new registers are added to the practicedSports relationship as well that when this relationship is updated, but when I update another field of the User entity, without changing practicedSports Hibernates only executes the delete so the entities disapears after the update. Also I verify that the user entity has something in the collection to be updated. This is the declaration of the User object, and particularly the relationship: @Entity @Name(User.SEAM_CONTEXT_NAME) @Scope(ScopeType.CONVERSATION) @Table(name="users", uniqueConstraints = { @UniqueConstraint(columnNames={"country_id", "citizen_id"}) }) @NamedQueries({ @NamedQuery(name = User.FIND_BY_NAME, query = "from User where name = :name"), @NamedQuery(name = User.FIND_BY_EMAIL, query = "from User where email = :email"), @NamedQuery(name = User.FIND_BY_MOBILE_PHONE, query = "from User where mobilePhone = :mobilePhone") }) public class User extends AuditableBaseObject implements IdentifiableObject, AddressableObject, CarrierableObject { .... @ManyToMany(cascade = CascadeType.ALL) @Cascade(org.hibernate.annotations.CascadeType.ALL) @JoinTable(name="user_practiced_sports", joinColumns = @JoinColumn(name = "user_id", referencedColumnName = "id"), inverseJoinColumns=@JoinColumn(name="sport_id", referencedColumnName="id")) @ForeignKey(name = "users_to_sports_fk", inverseName = "sports_to_users_fk") private Collection<Sport> practicedSports; This is the code I'm executing into the session bean: public void modifyUser(User user) { entityManager.persist(userLogger.info(user, interpolator.interpolate("#{messages['User.log.modify_data']}"))); log.debug(interpolator.interpolate("User #{user.name} (#{user.firstName} #{user.lastName}), modify his registration data.")); entityManager.merge(user); } I'm also attaching the model and a TestNG test case: UserMergeTest -- 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

15 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5148) Merge Hibernate Annotations reference documentation into Core

by Emmanuel Bernard (JIRA)

Merge Hibernate Annotations reference documentation into Core ------------------------------------------------------------- Key: HHH-5148 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5148 Project: Hibernate Core Issue Type: Task Components: documentation Reporter: Emmanuel Bernard 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

15 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5153) Convert non mapping sections form XML to Annotations or at least provide both solutions

by Emmanuel Bernard (JIRA)

Convert non mapping sections form XML to Annotations or at least provide both solutions --------------------------------------------------------------------------------------- Key: HHH-5153 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5153 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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

15 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5064) OrderBy string getting dumped to console on session factory creation

by Shawn Clowater (JIRA)

OrderBy string getting dumped to console on session factory creation -------------------------------------------------------------------- Key: HHH-5064 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5064 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Final Reporter: Shawn Clowater Priority: Trivial I noticed the following when firing our app up the first time after updating to 3.5 final {code} > orderByFragment(order-by) > sortSpecification({sort specification}) > sortKeySpecification(sort key) > sortKey($PlaceHolder$.DISPLAY_ORDER) < sortKey(null) < sortKeySpecification(asc) > orderingSpecification(asc) < orderingSpecification(null) < sortSpecification(null) < orderByFragment(null) {code} Tracing through the debugger leads me to the AbstractCollectionPersister {code} if ( hasOrder ) { ColumnMapper mapper = new ColumnMapper() { public String[] map(String reference) { return elementPropertyMapping.toColumns( reference ); } }; sqlOrderByStringTemplate = Template.renderOrderByStringTemplate( collection.getOrderBy(), mapper, factory, dialect, factory.getSqlFunctionRegistry() ); } {code} the Template.renderOrder call eventually creates an OrderByFragmentTranslator which calls {code} GeneratedOrderByFragmentRenderer renderer = new GeneratedOrderByFragmentRenderer(); try { renderer.orderByFragment( parser.getAST() ); } {code} The GeneratedOrderByFragmentRenderer makes a call to the traceIn and traceOut methods of the antlr.TreeParser which seem to be dumping these values to System.out.println() I do notice that there is an OrderByFragmentRenderer that isn't used by the core code that seems to override these methods and log the output to log.trace(). Should the GeneratedOrderByFragmentRenderer be using that class instead? It's not that big of a deal but it is rather ugly at startup. -- 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

15 years, 10 months

7
11
0 / 0

[Hibernate-JIRA] Created: (HHH-5272) Typo in tutorial at web site

by Slava Semushin (JIRA)

Typo in tutorial at web site ---------------------------- Key: HHH-5272 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5272 Project: Hibernate Core Issue Type: Bug Components: documentation Reporter: Slava Semushin Priority: Trivial Hello! I've started to read tutorial and found one typo at page http://docs.jboss.org/hibernate/stable/core/reference/en/html/tutorial.ht... in sentence "If you wish to use something else to build this tutoial (such as Ant), the layout will remain the same." There should be "tutorial", not "tutoial". I don't known where to report about it, so I'm reporting about it here. -- 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

15 years, 10 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5162) Deprecate @Entity.mutable in favor of @Immutable

by Emmanuel Bernard (JIRA)

Deprecate @Entity.mutable in favor of @Immutable ------------------------------------------------ Key: HHH-5162 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5162 Project: Hibernate Core Issue Type: Improvement Components: annotations Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Priority: Trivial 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

15 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5155) Move Additional modules chapter from Annotations to Core probably in Appendix

by Emmanuel Bernard (JIRA)

Move Additional modules chapter from Annotations to Core probably in Appendix ----------------------------------------------------------------------------- Key: HHH-5155 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5155 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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

15 years, 10 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5145) Update pom to use the new distributationManagement information

by Strong Liu (JIRA)

Update pom to use the new distributationManagement information -------------------------------------------------------------- Key: HHH-5145 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5145 Project: Hibernate Core Issue Type: Task Components: build Reporter: Strong Liu Assignee: Strong Liu Priority: Minor Fix For: 3.5.x http://community.jboss.org/wiki/MavenGettingStarted-Developers -- 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

15 years, 10 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5115) Migrate Annotations and EntityManager documentation system to jdocbook's maven plugin (like core)

by Emmanuel Bernard (JIRA)

Migrate Annotations and EntityManager documentation system to jdocbook's maven plugin (like core) ------------------------------------------------------------------------------------------------- Key: HHH-5115 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5115 Project: Hibernate Core Issue Type: Task Components: annotations, entity-manager Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik -- 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

15 years, 10 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5149) Move mapping documentation from Annotations to Core

by Emmanuel Bernard (JIRA)

Move mapping documentation from Annotations to Core --------------------------------------------------- Key: HHH-5149 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5149 Project: Hibernate Core Issue Type: Sub-task Components: documentation Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard 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

15 years, 10 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5150) Update settings section to reflect merge from Annotations and Core documentation

by Emmanuel Bernard (JIRA)

Update settings section to reflect merge from Annotations and Core documentation -------------------------------------------------------------------------------- Key: HHH-5150 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5150 Project: Hibernate Core Issue Type: Sub-task Reporter: Emmanuel Bernard -- 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

15 years, 10 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5094) PersistenceUtilHelper cannot access non-public fields/methods (it should be able to)

by Philip Clay (JIRA)

PersistenceUtilHelper cannot access non-public fields/methods (it should be able to) ------------------------------------------------------------------------------------ Key: HHH-5094 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5094 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Final Environment: 3.5.0-Final. Any environment Reporter: Philip Clay Attachments: hibernate-entitymanager-bugreproduction.tgz PersistenceUtilHelper is only able to access public fields and public methods. As it is written, it cannot access non-public members. Internally, it incorrectly uses Class.getField(...) and Class.getMethod(...). It should use Class.getDeclaredField(...) and Class.getDeclaredMethod(...), so that it can see non-public members. I believe the use of getField and getMethod is not indented, because setAccessibility is the next call after that. Here is the code... {code} private static Object get(Object proxy, String property) { final Class<?> clazz = proxy.getClass(); try { try { final Field field = clazz.getField( property ); // only retrieves public fields!!! setAccessibility( field ); // if you really only wanted public fields, this call is unnecessary! return field.get( proxy ); } catch ( NoSuchFieldException e ) { final Method method = getMethod( clazz, property ); if (method != null) { setAccessibility( method ); // if you really only wanted public methods, this call is unnecessary! return method.invoke( proxy ); } ... } private static Method getMethod(Class<?> clazz, String methodName) { try { char string[] = methodName.toCharArray(); string[0] = Character.toUpperCase( string[0] ); methodName = new String( string ); try { return clazz.getMethod( "get" + methodName ); // only retrieves public methods!!! } catch ( NoSuchMethodException e ) { return clazz.getMethod( "is" + methodName ); // only retrieves public methods!!! } ... } private static void setAccessibility(Member member) { if ( !Modifier.isPublic( member.getModifiers() ) ) { //Sun's ease of use, sigh... ( ( AccessibleObject ) member ).setAccessible( true ); // This is dead code! The input member will always be public } } {code} Notice the call to setAccessibility. The call to setAccessibility shows that one assumes that the field retrieved from getField() (or method from getMethod()) could be non-public, which in fact it can't. All fields returned from getField will always be public (same for getMethod()). So, essentially the code inside the if statement in setAccessibility is dead code. I have attached a tarball containing a failing testcase that shows the incorrect behavior. Explode the tarball and run "mvn test" to reproduce the incorrect behavior. Also, within the tarball, I have included an svn diff for a proposed patch. See the README.txt file within the tarball for more info. I first noticed this problem when using hibernate validator to validate some protected members, but I narrowed it down to a problem in PersistenceUtilHelper. -- 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

15 years, 10 months

5
9
0 / 0

[Hibernate-JIRA] Created: (HHH-4945) Replace all usages of EJB3TestCase with org.hibernate.ejb.test.TestCase

by Hardy Ferentschik (JIRA)

Replace all usages of EJB3TestCase with org.hibernate.ejb.test.TestCase ----------------------------------------------------------------------- Key: HHH-4945 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4945 Project: Hibernate Core Issue Type: Improvement Components: entity-manager Affects Versions: 3.5.0-CR-1 Reporter: Hardy Ferentschik Fix For: 3.5.x The setup in EJB3TestCase is really strange and we really want to have as many test as possible to derive from your main test base 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

15 years, 10 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3765) Fill the "end revision" column with appropriate data in add/mod/del/collection work units

by Adam Warski (JIRA)

Fill the "end revision" column with appropriate data in add/mod/del/collection work units ----------------------------------------------------------------------------------------- Key: HHH-3765 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3765 Project: Hibernate Core Issue Type: Sub-task Components: envers Reporter: Adam Warski Assignee: Adam Warski In case of modifications, not only the "end revision" column should be set on new data, but also modified on existing data. -- 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

15 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3764) Add the "end-revision" column when generating metadata

by Adam Warski (JIRA)

Add the "end-revision" column when generating metadata ------------------------------------------------------ Key: HHH-3764 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3764 Project: Hibernate Core Issue Type: Sub-task Components: envers Reporter: Adam Warski Assignee: Adam Warski The column would only be added if the necessary setting is set to true. The column will have the same type as the revision number, but will be nullable. -- 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

15 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5260) Tweak for query-cache via hibernate.hbm.xml needed

by Galder Zamarreno (JIRA)

Tweak for query-cache via hibernate.hbm.xml needed -------------------------------------------------- Key: HHH-5260 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5260 Project: Hibernate Core Issue Type: New Feature Components: caching (L2) Reporter: Galder Zamarreno Assignee: Galder Zamarreno >From Niktia Koksharov in https://jira.jboss.org/browse/ISPN-458: "In current implementation of hibernate-infinispan we can tune only entity and collection settings via hibernate.xml.cfg. But tuning in same way for queries needed too. In current version there are always the same cache region for all queries (look at org.hibernate.cache.infinispan.InfinispanRegionFactory.buildQueryResultsRegion) and it's incorrect. In org.hibernate.cache.infinispan.InfinispanRegionFactory.buildQueryResultsRegion Replace those lines: String cacheName = typeOverrides.get(QUERY_KEY).getCacheName(); CacheAdapter cacheAdapter = CacheAdapterImpl.newInstance(manager.getCache(cacheName)); To: Cache cache = getCache(regionName, QUERY_KEY, properties); CacheAdapter cacheAdapter = CacheAdapterImpl.newInstance(cache); " -- 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

15 years, 10 months

3
13
0 / 0

[Hibernate-JIRA] Created: (HHH-4568) Sybase - Test "BatchTest" fails due to "unexpected row count from update"

by Strong Liu (JIRA)

Sybase - Test "BatchTest" fails due to "unexpected row count from update" ------------------------------------------------------------------------- Key: HHH-4568 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4568 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0-Beta-2, 3.5.0.Beta-1, 3.3.2, 3.2.4.sp1 Environment: Sybase Reporter: Strong Liu Assignee: Strong Liu Fix For: 3.2.x, 3.3.x, 3.5, 3.3.0.GA, 3.2.4.sp1 The test "BatchTest" fails due to "org.hibernate.StaleStateException: Batch update returned unexpected row count from update [0]; actual row count: 0; expected: 1". The database server seems configured properly, as the "BatchUpdates" sample from jConnect 6 works correctly. The problem specifically occurs with a table that has a numeric column with precision (e.g. numeric(10,4)) Sybase does not thrown any SQLException when you try and persist a numeric value whose scale exceeds that defined on the column. Instead, it returns an updateCount of zero -- 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

15 years, 10 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HHH-5213) Add native SQL Boolean type to Ingres10Dialect

by Ray Fan (JIRA)

Add native SQL Boolean type to Ingres10Dialect ---------------------------------------------- Key: HHH-5213 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5213 Project: Hibernate Core Issue Type: Patch Components: core Affects Versions: 3.5.1 Environment: Hibernate 3.5.1 trunk rev 19194, Ingres 10.0.0 (a64.lnx/123) Reporter: Ray Fan Attachments: Ingres10Dialect.java.svn.diff Ingres 10 now supports a native boolean column data type. This patch enables support within the dialect. An instance of the DBMS has been made available on the machine at 80.241.73.38 with a connection URL of jdbc:ingres://80.241.73.38:X07/hibernate. Contact me for credentials. -- 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

15 years, 10 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3579) Support for PostgreSQL UUID data type

by Olivier Van Acker (JIRA)

Support for PostgreSQL UUID data type ------------------------------------- Key: HHH-3579 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3579 Project: Hibernate Core Issue Type: New Feature Components: core Affects Versions: 3.3.1 Reporter: Olivier Van Acker PostgreSQL has since version 8.3 UUID as data type nativly supported in the database. The only way to get this to work in Hibernate is to add <column name="id" sql-type="uuid"/> to your mappings file (or @columnDefinition via annotations) and create your own custom usertype (e.g. public class UUIDUserType implements UserType, Serializable {..} ) and map this to java.util.UUID worth mentioning is that java.util.UUID is only introduced in java 1.5 so there might be a backwards compatibility problem -- 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

15 years, 10 months

5
22
0 / 0

[Hibernate-JIRA] Created: (HHH-5204) Introduce @RequiresDialectFeature annotation

by Hardy Ferentschik (JIRA)

Introduce @RequiresDialectFeature annotation -------------------------------------------- Key: HHH-5204 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5204 Project: Hibernate Core Issue Type: Bug Components: testsuite Affects Versions: 3.5.1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.5.2 This will allow us to: * get rid of {{HibernateTestCase.runForCurrentDialect}} * handle skipping of tests more consistently At the same time we have to fix an issue {{HibernateTestCase.determineSkipByDialect}}. The logic in the if statement should be inverted. Last but not least we can get rid of some unused member variables -- 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

15 years, 10 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5231) Unit test failures lock up when they run on DB2 and PostgreSQL

by Gail Badner (JIRA)

Unit test failures lock up when they run on DB2 and PostgreSQL -------------------------------------------------------------- Key: HHH-5231 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5231 Project: Hibernate Core Issue Type: Bug Components: testsuite Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.x, 3.6 Unit test failures lock up when they run on DB2 and PostgreSQL. -- 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

15 years, 10 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5251) NativeSQLQueryReturn impls pre-cache a final hashcode based on non-final fields

by Steve Ebersole (JIRA)

NativeSQLQueryReturn impls pre-cache a final hashcode based on non-final fields -------------------------------------------------------------------------------- Key: HHH-5251 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5251 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6, 3.5.x For example, code such as {code} public class NativeSQLQueryScalarReturn implements NativeSQLQueryReturn { private Type type; private String columnAlias; private final int hashCode; public NativeSQLQueryScalarReturn(String alias, Type type) { this.type = type; this.columnAlias = alias; this.hashCode = determineHashCode(); } ... private int determineHashCode() { int result = type != null ? type.hashCode() : 0; result = 31 * result + ( getClass().getName().hashCode() ); result = 31 * result + ( columnAlias != null ? columnAlias.hashCode() : 0 ); return result; } public int hashCode() { return hashCode; } } {code} should really read as such (for correctness): {code} public class NativeSQLQueryScalarReturn implements NativeSQLQueryReturn { private final Type type; private final String columnAlias; private final int hashCode; public NativeSQLQueryScalarReturn(String alias, Type type) { this.type = type; this.columnAlias = alias; this.hashCode = determineHashCode(); } ... private int determineHashCode() { int result = type != null ? type.hashCode() : 0; result = 31 * result + ( getClass().getName().hashCode() ); result = 31 * result + ( columnAlias != null ? columnAlias.hashCode() : 0 ); return result; } public int hashCode() { return hashCode; } } {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

15 years, 10 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5220) Unit tests related to HHH-5063 and HHH-5135 fail on some dialects

by Gail Badner (JIRA)

Unit tests related to HHH-5063 and HHH-5135 fail on some dialects ----------------------------------------------------------------- Key: HHH-5220 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5220 Project: Hibernate Core Issue Type: Bug Components: testsuite Affects Versions: 3.5.2 Reporter: Gail Badner Assignee: Gail Badner Fix For: 3.5.x, 3.6 The fixes for HHH-5063 and HHH-5135 are OK, but there are problems when using particular dialects. For example: http://hudson.qa.jboss.com/hudson/job/hibernate-core-branch35-testsuite/1... http://hudson.qa.jboss.com/hudson/job/hibernate-core-branch35-testsuite/1... There may be other dialects that are affected as well. -- 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

15 years, 10 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2277) bidirectional <key-many-to-one> both lazy=false fetch=join lead to infinite loop

by Emmanuel Bernard (JIRA)

bidirectional <key-many-to-one> both lazy=false fetch=join lead to infinite loop -------------------------------------------------------------------------------- Key: HHH-2277 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2277 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Reporter: Emmanuel Bernard -- 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

15 years, 10 months

2
14
0 / 0

[Hibernate-JIRA] Created: (HHH-2268) JDK Bug 5062759 Breaks Hibernate Introspection

by James Olsen (JIRA)

JDK Bug 5062759 Breaks Hibernate Introspection ---------------------------------------------- Key: HHH-2268 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2268 Project: Hibernate3 Type: Patch Components: core Versions: 3.2.0.ga Environment: n/a Reporter: James Olsen Priority: Blocker Attachments: patch.txt Class#getDeclaredMethods() returns inherited methods - see http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5062759 This can result in Hibernate failing to determine the correct return type for a method that overrides an inherited method and further constrains the return type. Behaviour is nondeterministic as it depends on the order of the returned array, e.g. public volatile java.lang.Object com.xxx.impl.CPMImpl.getId() // from interface implemented by superclass public volatile com.xxx.api.CPMId com.xxx.impl.CPMImpl.getId() // from superclass implementation public com.xxx.impl.CPMIdImpl com.xxx.impl.CPMImpl.getId() // local The patch checks if the method is 'volatile' and ignores it if it is. -- 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

15 years, 10 months

5
14
0 / 0

[Hibernate-JIRA] Created: (EJB-225) EntityManager.find infinite loop related to ANN-381

by John Schneider (JIRA)

EntityManager.find infinite loop related to ANN-381 --------------------------------------------------- Key: EJB-225 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-225 Project: Hibernate Entity Manager Type: Bug Environment: Hibernate Annotations 3.2.0.cr2 Hibernate EntityManager 3.2.0.cr2 Hibernate Core 3.2.0.cr4 Reporter: John Schneider Attachments: Test.zip I've tested the fix for ANN-381 and found that the improvement is not working correctly with the Entity Manager, specifically the find method. When calling the find method on a OneToMany collection mapped by a field in a primary key class, the Entity manager goes into an infinite loop of selecting records. Please note that a workaround is to replace the entity managers find method with a query, such as this: Query query = entityManager.createQuery("select c from Card c where c.id = :id"); query.setParameter("id", id); return (Card) query.getSingleResult(); However, this workaround doesn't work if you have other entities that relate to something like the Card entity, shown below. I'll expand on the example code from ANN-381 to show the problem of infinite looping when trying to load the related collection. @Entity public class Card implements Serializable { @Id private String id; @OneToMany(cascade = CascadeType.ALL, fetch = FetchType.EAGER, mappedBy = "primaryKey.card") private Set<CardField> fields; public Card(String id) { this(); this.id = id; } Card() { fields = new HashSet<CardField>(); } public String getId() { return id; } public void setId(String id) { this.id = id; } public void addField(Card card, Key key) { fields.add(new CardField(card, key)); } } @Entity public class CardField implements Serializable { @EmbeddedId private PrimaryKey primaryKey; CardField(Card card, Key key) { this.primaryKey = new PrimaryKey(card, key); } CardField() { } } @Embeddable public class PrimaryKey implements Serializable { @ManyToOne(optional = false) private Card card; @ManyToOne(optional = false) private Key key; public PrimaryKey(Card card, Key key) { this.card = card; this.key = key; } PrimaryKey() {} } @Entity public class Key implements Serializable { @Id private String id; public Key(String id) { this.id = id; } Key() { } } >From what I can tell, this maps fine with the correct Hibernate libs and JBoss EJB Embeddable Alpha 9. However, the Entity Manager must be creating bad query code or something with similar results to having bad queries. I've testing with the following DAO: @Stateless public class CardDAOBean implements CardDAOLocal { @PersistenceContext private EntityManager entityManager; public void createCard(Card card) { entityManager.persist(card); } public Card findCard(String id) { return entityManager.find(Card.class, id); } public void createKey(Key key) { entityManager.persist(key); } } The Test class: public class EJBTest { private Card card; private Key key; public static void main(String[] args) { TestRunner.run(suite()); } public static junit.framework.Test suite() { TestSuite suite = new TestSuite("Test for ANN-381"); suite.addTest(new JUnit4TestAdapter(EJBTest.class)); // setup test so that embedded JBoss is started/stopped once for all // tests here. TestSetup wrapper = new TestSetup(suite) { protected void setUp() { startupEmbeddedJboss(); } protected void tearDown() { shutdownEmbeddedJboss(); } }; return wrapper; } @Before public void setup() { card = new Card("cardId"); key = new Key("keyId"); card.addField(card, key); } @Test public void persist() throws Exception { InitialContext ctx = getInitialContext(); CardDAOLocal CardDAOLocal = (CardDAOLocal) ctx.lookup("CardDAOBean/local"); CardDAOLocal.createKey(key); CardDAOLocal.createCard(card); Card card = CardDAOLocal.findCard(this.card.getId()); assertNotNull(card); } private static void startupEmbeddedJboss() { EJB3StandaloneBootstrap.boot(null); EJB3StandaloneBootstrap.scanClasspath(); } private static void shutdownEmbeddedJboss() { EJB3StandaloneBootstrap.shutdown(); } public static InitialContext getInitialContext() throws Exception { Hashtable properties = getInitialContextProperties(); return new InitialContext(properties); } private static Hashtable getInitialContextProperties() { Hashtable<String, String> props = new Hashtable<String, String>(); props.put("java.naming.factory.initial", "org.jnp.interfaces.LocalOnlyContextFactory"); props.put("java.naming.factory.url.pkgs", "org.jboss.naming:org.jnp.interfaces"); return props; } } Here's some relevant debugging output: Row insert: update CardField set card_id=? where card_id=? and key_id=? Row delete: update CardField set card_id=null where card_id=? and card_id=? and key_id=? One-shot delete: update CardField set card_id=null where card_id=? Static select for entity entity.CardField: select cardfield0_.card_id as card2_1_0_, cardfield0_.key_id as key1_1_0_ from CardField cardfield0_ where cardfield0_.card_id=? and cardfield0_.key_id=? Static select for action ACTION_MERGE on entity entity.CardField: select cardfield0_.card_id as card2_1_0_, cardfield0_.key_id as key1_1_0_ from CardField cardfield0_ where cardfield0_.card_id=? and cardfield0_.key_id=? Static select for action ACTION_REFRESH on entity entity.CardField: select cardfield0_.card_id as card2_1_0_, cardfield0_.key_id as key1_1_0_ from CardField cardfield0_ where cardfield0_.card_id=? and cardfield0_.key_id=? Static select for entity entity.Card: select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? Static select for entity entity.Card: select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? Static select for entity entity.Card: select card0_.id as id0_0_ from Card card0_ where card0_.id=? Static select for entity entity.Card: select card0_.id as id0_0_ from Card card0_ where card0_.id=? Static select for entity entity.Card: select card0_.id as id0_0_ from Card card0_ where card0_.id=? Static select for action ACTION_MERGE on entity entity.Card: select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? Static select for action ACTION_REFRESH on entity entity.Card: select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? Static select for entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for action ACTION_MERGE on entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for action ACTION_REFRESH on entity entity.Key: select key0_.id as id2_0_ from Key key0_ where key0_.id=? Static select for one-to-many entity.Card.fields: select fields0_.card_id as card2_1_, fields0_.key_id as key1_1_, fields0_.card_id as card2_1_0_, fields0_.key_id as key1_1_0_ from CardField fields0_ where fields0_.card_id=? When I call the findCard method in my EJB, the entity manager keeps looping through the select process several hundred times, and then dies from a stack overflow. Here's a sample of looping: DEBUG 17-09 21:17:18,328 (Log4JLogger.java:debug:84) -select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? DEBUG 17-09 21:17:18,343 (Log4JLogger.java:debug:84) -about to open ResultSet (open ResultSets: 0, globally: 0) DEBUG 17-09 21:17:18,343 (Log4JLogger.java:debug:84) -loading entity: [entity.Card#cardId] DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -about to open PreparedStatement (open PreparedStatements: 1, globally: 1) DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -about to open ResultSet (open ResultSets: 1, globally: 1) DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -loading entity: [entity.Card#cardId] DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -about to open PreparedStatement (open PreparedStatements: 2, globally: 2) DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -about to open ResultSet (open ResultSets: 2, globally: 2) DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -loading entity: [entity.Card#cardId] DEBUG 17-09 21:17:18,359 (Log4JLogger.java:debug:84) -about to open PreparedStatement (open PreparedStatements: 3, globally: 3) DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -about to open ResultSet (open ResultSets: 3, globally: 3) DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -loading entity: [entity.Card#cardId] DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -about to open PreparedStatement (open PreparedStatements: 4, globally: 4) DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -select card0_.id as id0_1_, fields1_.card_id as card2_3_, fields1_.key_id as key1_3_, fields1_.card_id as card2_1_0_, fields1_.key_id as key1_1_0_ from Card card0_ left outer join CardField fields1_ on card0_.id=fields1_.card_id where card0_.id=? DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -about to open ResultSet (open ResultSets: 4, globally: 4) DEBUG 17-09 21:17:18,375 (Log4JLogger.java:debug:84) -loading entity: [entity.Card#cardId] -- 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

15 years, 10 months

8
23
0 / 0

[Hibernate-JIRA] Created: (HHH-5253) TableHiLoGenerator does not increment hi-value any more when lo-range es exhausted

by Martin Gubser (JIRA)

TableHiLoGenerator does not increment hi-value any more when lo-range es exhausted ---------------------------------------------------------------------------------- Key: HHH-5253 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5253 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2, 3.5.1 Environment: Hibernate 3.5.2, DB2 v9.7 Reporter: Martin Gubser Attachments: A.java, HiLoTest.java The {{TableHiLoGenerator}} increments the lo value when it first gets a lo-range but not any more when it grabs further lo-ranges. The first run of the attached program leaves the hi-value=1. Consequently on the second run it uses an id that has already been assigned to. -- 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

15 years, 10 months

2
3
0 / 0

[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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

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

15 years, 10 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-4647) Problems with @JoinColumn referencedColumnName and quoted column and table names

by Peter Brant (JIRA)

Problems with @JoinColumn referencedColumnName and quoted column and table names -------------------------------------------------------------------------------- Key: HHH-4647 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4647 Project: Hibernate Core Issue Type: Bug Components: annotations, core Affects Versions: 3.5.0-Beta-2 Environment: current CVS, not database platform dependent Reporter: Peter Brant Attachments: hibernate-annotations.patch, hibernate-core.patch, test-case.zip There are really two separate issues here, but the test case reduction and patches are so small (and involve related functionality) they are combined. #1: A referencedColumnName that references a quoted target column cannot be found. The test case is app.TestReferencedColumnName#testQuotedReferencedColumnName(). The patch is hibernate-annotations.patch. #2: An invalid referencedColumnName (including the unquoted version of a valid column) results in an infinite loop in o.h.c.Configuration$MappingsImpl#getPhysicalColumnName(). The test case is app.TestReferencedColumnName#testInvalidReferencedColumnNameOnQuotedTable. The patch is hibernate-core.patch. It looks like the same issue exists with getLogicalColumnName(), but I'm not sure where this is used (i.e. how to test it) so I left it alone. -- 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

15 years, 10 months

3
10
0 / 0

[Hibernate-JIRA] Created: (HHH-3694) ResultTransformer not used when scroll() is used on a named SQLQuery

by Oscar Pearce (JIRA)

ResultTransformer not used when scroll() is used on a named SQLQuery -------------------------------------------------------------------- Key: HHH-3694 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3694 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: Hibernate Core 3.3.1, PostgreSQL 8.1, HSQLDB 1.8 Reporter: Oscar Pearce Priority: Minor Attachments: sqlqueryrestrans.zip If a ResultTransformer is set on a named SQLQuery, and then scroll() is used on the query, the ResultTransformer is never used. The unit test in the attached Maven project shows this. The fix seems simple - a one-line change in org.hibernate.loader.custom.CustomLoader#getHolderInstantiator(ResultTransformer resultTransformer, String[] queryReturnAliases). The sense of the test of resultTransformer against null should be reversed. -- 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

15 years, 10 months

5
16
0 / 0

[Hibernate-JIRA] Created: (HHH-5109) @OneToOne - too many joins

by Marek Romanowski (JIRA)

@OneToOne - too many joins -------------------------- Key: HHH-5109 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5109 Project: Hibernate Core Issue Type: Bug Components: annotations, core Affects Versions: 3.5.0-Final Reporter: Marek Romanowski Attachments: hibernate-one-to-one.zip With classes like this: @Entity @Proxy(lazy=false) class Owner { @javax.persistence.Id @javax.persistence.Column(name = "ID", columnDefinition = "BIGINT") public java.lang.Long getId() { return this.id; } public void setId(java.lang.Long newValue) { this.id = newValue; } private java.lang.Long id; @javax.persistence.OneToOne(targetEntity = Owned.class) @org.hibernate.annotations.Cascade( { org.hibernate.annotations.CascadeType.ALL }) @javax.persistence.PrimaryKeyJoinColumn public Owned getOwned() { return this.owned; } public void setOwned(Owned owned) { this.owned = owned; if (owned != null) { owned.setOwner(this); } } private Owned owned; } @Entity @Proxy(lazy=false) class Owned { private java.lang.Long id; @javax.persistence.Id @javax.persistence.GeneratedValue(generator = "foreign") @org.hibernate.annotations.GenericGenerator( name = "foreign", strategy = "foreign", parameters = { @org.hibernate.annotations.Parameter(name = "property", value = "owner") }) @javax.persistence.Column(name = "ID", columnDefinition = "BIGINT") public java.lang.Long getId() { return this.id; } public void setId(java.lang.Long newValue) { this.id = newValue; } @javax.persistence.OneToOne(targetEntity = Owner.class, mappedBy = "owned") @javax.persistence.PrimaryKeyJoinColumn public Owner getOwner() { return this.owner; } public void setOwner(Owner owner) { this.owner = owner; } private Owner owner; } Idea is to have one to one relation between Owner and Owned mapped by "id" properties in both entities. So for each pair owner.id == owned.id. code: session.load(Owner.class, 1L) turns into SQL: select owner0_.ID as ID0_2_, owned1_.ID as ID1_0_, owner2_.ID as ID0_1_ from Owner owner0_ left outer join Owned owned1_ on owner0_.ID=owned1_.ID left outer join Owner owner2_ on owned1_.ID=owner2_.ID where owner0_.ID=? Isn't it wrong? @OneToOne annotation on getOwner() has mappedBy="owned" property, so I would expect this code to generate SQL with only one join (only "owner join owned"). If this is correct H3 behaviour in this case, then write what should I change in annotations to get described behaviour, please. I've attached maven project with one test encapsulating this issue. -- 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

15 years, 10 months

3
11
0 / 0

[Hibernate-JIRA] Created: (HHH-4440) Support for column-level read/write fragments (Rob Hasselbaum)

by Steve Ebersole (JIRA)

Support for column-level read/write fragments (Rob Hasselbaum) -------------------------------------------------------------- Key: HHH-4440 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4440 Project: Hibernate Core Issue Type: Patch Components: core, metamodel Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.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

15 years, 10 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HHH-3768) Modify the revision entity to include the end-revision number when available

by Adam Warski (JIRA)

Modify the revision entity to include the end-revision number when available ---------------------------------------------------------------------------- Key: HHH-3768 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3768 Project: Hibernate Core Issue Type: Sub-task Components: envers Reporter: Adam Warski Assignee: Adam Warski This includes adding a new annotation and modifying the default revision entity -- 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

15 years, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4086) improving the performance of the object loading in hibernate

by shubha (JIRA)

improving the performance of the object loading in hibernate ------------------------------------------------------------ Key: HHH-4086 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4086 Project: Hibernate Core Issue Type: Task Components: query-hql Affects Versions: 3.2.3 Environment: hibernate 3.2.3 ga, oracle Reporter: shubha Priority: Critical _sessions = SessionFactoryUtil.getSessionFactory(); session = _sessions.openSession(); Query query = session.getNamedQuery(queryName); tx = session.beginTransaction(); results = query.list(); System.out.println(results.size()); tx.commit(); i am trying to get a collection of objects from query.list(). Even though the SQL generated from hibernate runs very fast in oracle, the O/R mapping in case of hibernate is taking lot of time. To fetch around 15 thousand records it takes 8 to 12 minutes. I am using left join fetch on 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

15 years, 10 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3909) Improve Performance of FieldInterceptionHandler (and thus of flushing)

by Ovidio Mallo (JIRA)

Improve Performance of FieldInterceptionHandler (and thus of flushing) ---------------------------------------------------------------------- Key: HHH-3909 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3909 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.3.1 Reporter: Ovidio Mallo Attachments: patch.txt In the FieldInterceptionHelper class, the method Class#getInterfaces() is used in conjunction with a subsequent loop over all interfaces of an entity class in order to check whether a bytecode instrumentation interface of CGlib or Javassist is found. This is done that way since CGlib and Javassist are both optional so they should only be accessed at runtime if available on the classpath. Attached you can find a simple patch which only once checks whether CGlib and/or Javassist is available and then uses the more performant "instanceof" operator in order to check whether an entity has an interceptor. The new code still guarantees that no CGlib or Javassist class is accessed if it is not on the classpath. The patch helps making the FieldInterceptionHelper methods more performant which can e.g. be noticed during a session flush, especially if bytecode instrumentation is used. In order to measure the performance impact of the patch I've written a simple program which does the following: 1. insert 100 thousand entities into a simple table with 6 numeric attributes 2. do an initial flush on the session in order to execute all the insert statements 3. loop 300 times and do a flush on the session (only a dirty check is performed, no database operation) I've time the flushes under point 3 above with and without bytecode instrumentation for the used entity. Here are the results: USING BYTECODE INSTRUMENTATION ============================= * SUN JVM 1.6.0_05: - without patch: 25734ms - with patch: 11015ms * IBM JVM 1.4.2: - without patch: 20672ms - with patch: 11140ms WITHOUT BYTECODE INSTRUMENTATION ================================ * SUN JVM 1.6.0_05: - without patch: 73328ms - with patch: 62015ms * IBM JVM 1.4.2: - without patch: 70344ms - with patch: 61125ms Using bytecode instrumentation, the performance improvement is about of a factor of 2-2.5. When not using bytecode instrumentation, the overall impact is of course less relevant since the rest of the work done during flush is more expensive anyway. In any case, IMHO the impact when using bytecode instrumentation is relevant. The patch is very simple and only touches the FieldInterceptionHelper 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

15 years, 10 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5185) Columns in Formulas not always rewritten, triggers ambiguous column SQL error

by Chris Wilson (JIRA)

Columns in Formulas not always rewritten, triggers ambiguous column SQL error ----------------------------------------------------------------------------- Key: HHH-5185 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5185 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1 Environment: MySQL Server version: 5.0.51a-3ubuntu5.5 (Ubuntu) Hibernate version 3.5.1-Final Reporter: Chris Wilson Attachments: HibernateJoinFormulaAliasTest.java The attached test case joins an entity with two @Formulas twice. The first @Formula is the algebraic expression "(kittens * 4) + 3", the second is a SQL function "EXTRACT(MONTH FROM birthday)". kittens is rewritten but birthday is not. Because the table is joined twice, MySQL reports the error: {code} com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Column 'birthday' in field list is ambiguous {code} which shows up as: {code} org.hibernate.exception.ConstraintViolationException: could not load an entity: [org.aptivate.hibernate.test.HibernateJoinFormulaAliasTest$House#1] at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:96) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.loadEntity(Loader.java:1937) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:86) at org.hibernate.loader.entity.AbstractEntityLoader.load(AbstractEntityLoader.java:76) at org.hibernate.persister.entity.AbstractEntityPersister.load(AbstractEntityPersister.java:3270) at org.hibernate.event.def.DefaultLoadEventListener.loadFromDatasource(DefaultLoadEventListener.java:496) at org.hibernate.event.def.DefaultLoadEventListener.doLoad(DefaultLoadEventListener.java:477) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:227) at org.hibernate.event.def.DefaultLoadEventListener.lockAndLoad(DefaultLoadEventListener.java:403) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:155) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:1080) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:1065) at org.hibernate.impl.SessionImpl.get(SessionImpl.java:1056) at org.aptivate.hibernate.test.HibernateJoinFormulaAliasTest.testFailing(HibernateJoinFormulaAliasTest.java:97) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.aptivate.hibernate.test.base.HibernateTestBase.runTestMethod(HibernateTestBase.java:204) at org.aptivate.hibernate.test.base.HibernateTestBase.runTest(HibernateTestBase.java:117) at junit.framework.TestCase.runBare(TestCase.java:130) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.jdt.internal.junit.runner.junit3.JUnit3TestReference.run(JUnit3TestReference.java:130) at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197) Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Column 'birthday' 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:409) at com.mysql.jdbc.Util.getInstance(Util.java:384) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1041) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3562) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3494) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1960) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2114) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2696) at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2105) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:2264) at org.hibernate.jdbc.AbstractBatcher.getResultSet(AbstractBatcher.java:208) at org.hibernate.loader.Loader.getResultSet(Loader.java:1849) at org.hibernate.loader.Loader.doQuery(Loader.java:718) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:270) at org.hibernate.loader.Loader.loadEntity(Loader.java:1933) ... 31 more {code} The rewritten SQL is: {code} select hibernatej0_.id as id0_2_, cats1x1_.firstHome_id as firstHome4_0_4_, cats1x1_.id as id4_, cats1x1_.id as id1_0_, cats1x1_.birthday as birthday1_0_, cats1x1_.firstHome_id as firstHome4_1_0_, cats1x1_.kittens as kittens1_0_, cats1x1_.secondHome_id as secondHome5_1_0_, EXTRACT(MONTH FROM birthday) as formula0_0_, (cats1x1_.kittens * 4) + 3 as formula1_0_, cats2x2_.secondHome_id as secondHome5_0_5_, cats2x2_.id as id5_, cats2x2_.id as id1_1_, cats2x2_.birthday as birthday1_1_, cats2x2_.firstHome_id as firstHome4_1_1_, cats2x2_.kittens as kittens1_1_, cats2x2_.secondHome_id as secondHome5_1_1_, EXTRACT(MONTH FROM birthday) as formula0_1_, (cats2x2_.kittens * 4) + 3 as formula1_1_ from houses hibernatej0_ left outer join cats cats1x1_ on hibernatej0_.id=cats1x1_.firstHome_id left outer join cats cats2x2_ on hibernatej0_.id=cats2x2_.secondHome_id where hibernatej0_.id=? {code} There's no apparent workaround that lets us reference the same column in a formula in a table that's joined twice. -- 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

15 years, 10 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2339) merge instumented class fails

by Alexey Romanchuk (JIRA)

merge instumented class fails ----------------------------- Key: HHH-2339 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2339 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1, 3.2.0.ga Environment: Hibernate 3.2.1 (tested with 3.2.0 too) Postgresql 8.1.4 Reporter: Alexey Romanchuk Priority: Blocker When we try to merge instrumented detached entity with lazy no-proxy many-to-one association we have org.hibernate.LazyInitializationException. It occurs because cascade try to process all associations in Cascade class, but object disconected from session and can not obtaion lazy property. If classes are not instrumented all works ok. Why merge action does not have overrided performOnLazyProperty mathod to prevent fetching lazy properties? Here it is small example that illustates problem. ===MAPPING=== <hibernate-mapping> <class name="Client" table="test_client"> <id name="id" column="id" type="long"> <generator class="sequence"> <param name="sequence">test_seq</param> </generator> </id> <property name="name" column="name"/> <many-to-one name="info" class="LoginInfo" lazy="no-proxy" column="info_id" cascade="merge,evict"/> </class> <class name="LoginInfo" table="test_login_info"> <id name="id" column="id" type="long"> <generator class="sequence"> <param name="sequence">test_seq</param> </generator> </id> <property name="login" column="login"/> <property name="pass" column="pass"/> </class> </hibernate-mapping> ===JAVA=== ===DOMAIN=== public class Client { private long id; private String name; private LoginInfo info; //getters and setters } public class LoginInfo { private long id; private String login; private String pass; //getters and setters } ===USAGE=== public class Main { public static void main( String[] args ) { Session s1 = sf.openSession(); s1.beginTransaction(); Client c = ( Client ) s1.get( Client.class, 2l ); s1.flush(); s1.getTransaction().commit(); s1.close(); Session s2 = sf.openSession(); s2.beginTransaction(); c = ( Client ) s2.merge( c ); s2.flush(); s2.getTransaction().commit(); s2.close(); } } ==STACKTRACE=== org.hibernate.LazyInitializationException: session is not connected at org.hibernate.intercept.AbstractFieldInterceptor.intercept(AbstractFieldInterceptor.java:67) at org.hibernate.intercept.cglib.FieldInterceptorImpl.readObject(FieldInterceptorImpl.java:75) at Client.$cglib_read_info(Client.java) at Client.getInfo(Client.java:12) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.hibernate.property.BasicPropertyAccessor$BasicGetter.get(BasicPropertyAccessor.java:145) at org.hibernate.tuple.entity.AbstractEntityTuplizer.getPropertyValue(AbstractEntityTuplizer.java:277) at org.hibernate.persister.entity.AbstractEntityPersister.getPropertyValue(AbstractEntityPersister.java:3529) at org.hibernate.engine.Cascade.cascade(Cascade.java:130) at org.hibernate.event.def.DefaultMergeEventListener.cascadeOnMerge(DefaultMergeEventListener.java:407) at org.hibernate.event.def.DefaultMergeEventListener.entityIsDetached(DefaultMergeEventListener.java:266) at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:120) at org.hibernate.event.def.DefaultMergeEventListener.onMerge(DefaultMergeEventListener.java:53) at org.hibernate.impl.SessionImpl.fireMerge(SessionImpl.java:677) at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:661) at org.hibernate.impl.SessionImpl.merge(SessionImpl.java:665) at Main.main(Main.java:56) -- 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

15 years, 10 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2388) Insert w/ identity column fails on Sybase but no exception occurs

by Tim Morrow (JIRA)

Insert w/ identity column fails on Sybase but no exception occurs ----------------------------------------------------------------- Key: HHH-2388 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2388 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Environment: Hibernate 3.2.1.GA with annotations Sybase jConnect 6.05 JDBC driver Sybase ASE 15 database Reporter: Tim Morrow I have a scenario where storing a new entity fails (i.e. the row is not inserted) but Hibernate does not realize this. No exceptions are thrown. Later, this leads to AssertionFailures (if two such entities fail in the same session - they both have the same PK). The problem specifically occurs with a table that has a numeric column with precision (e.g. numeric(10,4)) and an identity column when using Sybase ASE. ========== To reproduce: 1. Use Sybase jConnect 6.05 JDBC driver with Sybase ASE 15 database. 2. Define an Entity with a long ID and BigDecimal numeric column. 3. Create a corresponding table with an identity column and numeric(10, 4) column. For example: hibernate.MyEntity.java: ----------------------------------------- package hibernate; import java.math.BigDecimal; import javax.persistence.Column; import javax.persistence.Entity; import javax.persistence.GeneratedValue; import javax.persistence.GenerationType; import javax.persistence.Id; import javax.persistence.Table; import org.hibernate.validator.NotNull; @Entity @Table(name = "z_tim_test") public class MyEntity { private BigDecimal cost; private long id; public MyEntity() {} @Column(columnDefinition = "numeric(10,4)") @NotNull public final BigDecimal getCost() { return cost; } @GeneratedValue(strategy = GenerationType.AUTO) @Id public final long getId() { return id; } public final void setCost(BigDecimal cost) { this.cost = cost; } public final void setId(long id) { this.id = id; } } Table: ----------------------------------------- CREATE TABLE z_tim_test ( id numeric(19) PRIMARY KEY not null, cost numeric(10,4) not null ); 4. Write some code that stores a new entity and tries to load it: MyEntity myEntity = new MyEntity(); myEntity.setCost(new BigDecimal("123.12345")); session.save(myEntity); session.flush(); session.clear(); List<MyEntity> results = session.createCriteria(MyEntity.class).list(); if (results.size() != 1) { throw new IllegalStateException("Expected 1 result"); } This test will throw the IllegalStateException because the row was not persisted and no errors occurred. Reason: * Sybase does not thrown any SQLException when you try and persist a numeric value whose scale exceeds that defined on the column. Instead, it returns an updateCount of zero and an identity column value of zero. * Hibernate does not check the updateCount after executing the statement when using an Identity column. The offending code is in: org.hibernate.id.IdentityGenerator$InsertSelectDelegate public Serializable executeAndExtract(PreparedStatement insert) throws SQLException { if ( !insert.execute() ) { while ( !insert.getMoreResults() && insert.getUpdateCount() != -1 ) { // do nothing until we hit the rsult set containing the generated id } } ResultSet rs = insert.getResultSet(); try { return IdentifierGeneratorFactory.getGeneratedIdentity( rs, persister.getIdentifierType() ); } finally { rs.close(); } } It ignores the updateCount. The net result is that the object is assigned a PK value of zero. Hibernate continues. My applicaiton is unaware that the row failed to insert. Solution: It would seem to me replacing the above code with: if (!insert.execute()) { if (insert.getUpdateCount() < 1) { throw new HibernateException("No update occurred"); } while (!insert.getMoreResults()) { // do nothing until we hit the rsult set containing the generated id } } Would take care of the problem? -- 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

15 years, 10 months

8
19
0 / 0

[Hibernate-JIRA] Created: (HHH-5229) org.hibernate.test.hql.ScrollableCollectionFetchingTest.testScrollingJoinFetchesEmptyResultSet() fails on sybase

by Strong Liu (JIRA)

org.hibernate.test.hql.ScrollableCollectionFetchingTest.testScrollingJoinFetchesEmptyResultSet() fails on sybase ---------------------------------------------------------------------------------------------------------------- Key: HHH-5229 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5229 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2, 3.5.1 Reporter: Strong Liu Assignee: Strong Liu Fix For: 3.5.x, 3.6 {quote} Result set is IDLE as you are not currently accessing a row. Description: The application has called one of the ResultSet.getXXX column-data retrieval methods, but there is no current row; the application has not called ResultSet.next(), or ResultSet.next() returned "false" to indicate that there is no data. Action: Check that rs.next() is set to "true" before calling rs.getXXX. {quote} org.hibernate.exception.GenericJDBCException: could not perform sequential read of results (forward) at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:126) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:114) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) at org.hibernate.loader.Loader.loadSequentialRowsForward(Loader.java:420) at org.hibernate.impl.FetchingScrollableResultsImpl.next(FetchingScrollableResultsImpl.java:83) at org.hibernate.test.hql.ScrollableCollectionFetchingTest.testScrollingJoinFetchesEmptyResultSet(ScrollableCollectionFetchingTest.java:67) Caused by: java.sql.SQLException: JZ0R1: Result set is IDLE as you are not currently accessing a row. at com.sybase.jdbc3.jdbc.ErrorMessage.raiseError(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.checkIfReadableRow(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.getColumn(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.getLong(Unknown Source) at com.sybase.jdbc3.jdbc.SybResultSet.getLong(Unknown Source) at org.hibernate.type.LongType.get(LongType.java:51) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:184) at org.hibernate.type.NullableType.nullSafeGet(NullableType.java:173) at org.hibernate.loader.Loader.getKeyFromResultSet(Loader.java:1120) at org.hibernate.loader.Loader.loadSequentialRowsForward(Loader.java:409) ... 31 more -- 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

15 years, 10 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-3624) DialectFactory needs DB2/NT64 adding to the MAPPERS Map

by mike wray (JIRA)

DialectFactory needs DB2/NT64 adding to the MAPPERS Map ------------------------------------------------------- Key: HHH-3624 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3624 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Reporter: mike wray Priority: Minor DialectFactory needs DB2/NT64 adding to the MAPPERS Map. ie MAPPERS.put( "DB2/NT64", new VersionInsensitiveMapper( "org.hibernate.dialect.DB2Dialect" ) ); -- 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

15 years, 10 months

5
6
0 / 0

[Hibernate-JIRA] Created: (HBX-1119) Hibernate tools tasks(hbm2java) generates info logs as standard error logs (shows red in eclipse) instead of standard out

by vivek meghanathan (JIRA)

Hibernate tools tasks(hbm2java) generates info logs as standard error logs (shows red in eclipse) instead of standard out ------------------------------------------------------------------------------------------------------------------------- Key: HBX-1119 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1119 Project: Hibernate Tools Issue Type: Bug Components: hbm2java Affects Versions: 3.2.0.GA Environment: Hibernate 3.2.0 GA Reporter: vivek meghanathan Hibernate tools tasks(hbm2java) generates info logs as standard error logs (shows red in eclipse) instead of standard out. Please have a look. -- 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

15 years, 10 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3475) Support not-found="ignore" for <any> mappings

by Felix Gnass (JIRA)

Support not-found="ignore" for <any> mappings --------------------------------------------- Key: HHH-3475 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3475 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.3.0.SP1 Reporter: Felix Gnass Priority: Minor It would be useful if the <any> element would support the not-found="ignore|exception" setting. Due to the nature of any-mappings it's impossible to use on-delete cascades at the database layer, so it's very likely that ObjectNotFoundExceptions occur. Currently the only work-around to gracefully handle such situations seems to be the implementation of a custom EntityNotFoundDelegate that doesn't throw an exception. -- 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

15 years, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4474) NullPointerException in AuditEventListener#generateBidirectionalCollectionChangeWorkUnits onPostInsert...

by Daniel Bleisteiner (JIRA)

NullPointerException in AuditEventListener#generateBidirectionalCollectionChangeWorkUnits onPostInsert... --------------------------------------------------------------------------------------------------------- Key: HHH-4474 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4474 Project: Hibernate Core Issue Type: Bug Components: envers Environment: <version>1.2.0.GA-hibernate-3.3</version> Reporter: Daniel Bleisteiner Attachments: stacktrace.txt I get the exception attached as file after creating an entity. The mapping works on my development machine... a test server throws that exception. I've tried to search for eny differences in the tables but can't find any so far. The last time a similar error occured I was missing the versioned entry in the version table - these have been filled with the lowest revision available (the same way on my machine as on the test server). So I'm stuck... I have no access to the related source either... maybe this would help! -- 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

15 years, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3992) SQLServer "contains" boolean predicate not handled in HQL

by Scott Van Wart (JIRA)

SQLServer "contains" boolean predicate not handled in HQL --------------------------------------------------------- Key: HHH-3992 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3992 Project: Hibernate Core Issue Type: Improvement Components: query-hql Affects Versions: 3.3.2, 3.3.1 Environment: Hibernate core 3.3.1, JDK 1.6, SQLServer 2003 Reporter: Scott Van Wart The following HQL: select pp from Product pp where CONTAINS( pp.keywords, :keywords ) Will throw this exception: org.hibernate.hql.ast.QuerySyntaxException: unexpected AST node: ( near line 1, column 33 [select pp from Product pp where CONTAINS( pp.keywords, :keywords )] at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:54) at org.hibernate.hql.ast.QuerySyntaxException.convert(QuerySyntaxException.java:47) at org.hibernate.hql.ast.ErrorCounter.throwQueryException(ErrorCounter.java:82) at org.hibernate.hql.ast.QueryTranslatorImpl.analyze(QueryTranslatorImpl.java:258) at org.hibernate.hql.ast.QueryTranslatorImpl.doCompile(QueryTranslatorImpl.java:183) at org.hibernate.hql.ast.QueryTranslatorImpl.compile(QueryTranslatorImpl.java:134) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:101) at org.hibernate.engine.query.HQLQueryPlan.<init>(HQLQueryPlan.java:80) at org.hibernate.engine.query.QueryPlanCache.getHQLQueryPlan(QueryPlanCache.java:94) at org.hibernate.impl.AbstractSessionImpl.getHQLQueryPlan(AbstractSessionImpl.java:156) at org.hibernate.impl.AbstractSessionImpl.createQuery(AbstractSessionImpl.java:135) at org.hibernate.impl.SessionImpl.createQuery(SessionImpl.java:1650) I tried changing it to this: select pp from Product pp where CONTAINS( pp.keywords, :keywords ) = TRUE But then SQL Server doesn't like it (it produces SQL like "CONTAINS(pkgproduct0_.keywords, ?)=1": org.hibernate.exception.SQLGrammarException: could not execute query using scroll Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Incorrect syntax near '='. -- 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

15 years, 11 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3002) database field name 'version' causes ClassCastException while building session factory

by Patrick Burke (JIRA)

database field name 'version' causes ClassCastException while building session factory -------------------------------------------------------------------------------------- Key: HHH-3002 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3002 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, Java 1.6.0_03, MySQL 5.0.41 Reporter: Patrick Burke Attachments: out.hib4 When a database table contains a field named 'version', like his one: DROP TABLE IF EXISTS `tester`.`software_package`; CREATE TABLE `tester`.`software_package` ( `software_id` int(11) NOT NULL auto_increment, `version` varchar(100) default NULL, `name` varchar(100) default NULL, `root_file_id` int(11) default NULL, PRIMARY KEY (`software_id`) ) ENGINE=InnoDB DEFAULT CHARSET=latin1; The following error is thrown: [java] Initial SessionFactory creation failed.java.lang.ClassCastException: org.hibernate.type.StringType cannot be cast to org.hibernate.type.VersionType [java] Exception in thread "main" java.lang.ExceptionInInitializerError [java] at util.HibernateUtil.<clinit>(Unknown Source) [java] at events.EventManager.listNodes(Unknown Source) [java] at events.EventManager.main(Unknown Source) [java] Caused by: java.lang.ClassCastException: org.hibernate.type.StringType cannot be cast to org.hibernate.type.VersionType [java] at org.hibernate.tuple.PropertyFactory.buildVersionProperty(PropertyFactory.java:84) [java] at org.hibernate.tuple.entity.EntityMetamodel.<init>(EntityMetamodel.java:168) [java] at org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:434) [java] at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:109) [java] at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:55) [java] at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:226) [java] at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) [java] ... 3 more -- 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

15 years, 11 months

6
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4968) Cannot deactivate default BeanValidationListener independently of DDL constraints generation

by Vladimir Klyushnikov (JIRA)

Cannot deactivate default BeanValidationListener independently of DDL constraints generation -------------------------------------------------------------------------------------------- Key: HHH-4968 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4968 Project: Hibernate Core Issue Type: Bug Components: annotations Affects Versions: 3.5.0-CR-2 Environment: Hibernate 3.5.0-CR-2, Hibernate Validator 4.0.2.GA Reporter: Vladimir Klyushnikov Hi, I need to configure my custom BeanValidationListener instance through Spring, but I cannot deactivate default BeanValidationListener instance. It can be switched off only with DDL constraint generation. When I provide *DDL* value for *javax.persistence.validation.mode* it still activates default BeanValidationListener. When I provide *NONE* value it switches off both BeanValidationListener and DDL constraints. This is because of following code in *BeanValidationListener.java*: {code} public static void activateBeanValidation(EventListeners eventListeners, Properties properties) { ... if ( modes.contains( ValidationMode.NONE ) ) return; ... } {code} It should be changed to following: {code} if (!(modes.contains(ValidationMode.CALLBACK) || modes.contains( ValidationMode.AUTO))) return; {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

15 years, 11 months

3
12
0 / 0

[Hibernate-JIRA] Created: (HHH-5195) FilterImpl.validate() throws NullPointerExeption at line 164

by Savochkin Alexander (JIRA)

FilterImpl.validate() throws NullPointerExeption at line 164 ------------------------------------------------------------ Key: HHH-5195 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5195 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.1 Environment: hibernate-distribution-3.5.1-Final-dist Reporter: Savochkin Alexander After deserialization NPE is thrown at this line FilterImpl {code} line:164 Iterator itr = definition.getParameterNames().iterator(); {code} the last lines from stack trace are: {code} java.lang.NullPointerException at org.hibernate.impl.FilterImpl.validate(FilterImpl.java:164) at org.hibernate.engine.LoadQueryInfluencers.getEnabledFilters(LoadQueryInfluencers.java:109) at org.hibernate.impl.SessionImpl.readObject(SessionImpl.java:2144) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:48) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37) at java.lang.reflect.Method.invoke(Method.java:600) at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:986) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1865) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1769) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1345) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:364) {code} Looking at SessionImpl class we see: {code} line 2143: Iterator iter = loadQueryInfluencers.getEnabledFilters().values().iterator(); while ( iter.hasNext() ) { ( ( FilterImpl ) iter.next() ).afterDeserialize( factory ); } {code} LoadQueryInfluencers: {code} line:105 Iterator itr = enabledFilters.values().iterator(); while ( itr.hasNext() ) { final Filter filter = ( Filter ) itr.next(); filter.validate(); } {code} So, afterDeserialization() on enabled filters method is invoked AFTER getEnabledFilters() method is. It seems to be the reason why the private TRANSIENT field "definition" of every filter is null at the moment of filter validation! "definition" field is supposed to be initialized only after validate() is called. -- 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

15 years, 11 months

3
11
0 / 0

[Hibernate-JIRA] Created: (HHH-4036) EntityMetamodel entityNameByInheritenceClassNameMap field used inconsistently

by Jeremy Stone (JIRA)

EntityMetamodel entityNameByInheritenceClassNameMap field used inconsistently ----------------------------------------------------------------------------- Key: HHH-4036 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4036 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Reporter: Jeremy Stone After upgrading (from 3.3.0.SP1) to 3.3.2.GA we have started getting the follow stack trace logged: org.hibernate.HibernateException: Unable to resolve entity name from Class [com.cyclone.netPrefect.admin.restriction.complex.TimeSpanRestrictionItemEntity] expected instance/subclass of [RestrictionItem] at org.hibernate.tuple.entity.PojoEntityTuplizer.determineConcreteSubclassEntityName(PojoEntityTuplizer.java:363) at org.hibernate.persister.entity.AbstractEntityPersister.getSubclassEntityPersister(AbstractEntityPersister.java:3643) at org.hibernate.impl.SessionImpl.getEntityPersister(SessionImpl.java:1375) at org.hibernate.engine.ForeignKeys.isTransient(ForeignKeys.java:203) at org.hibernate.event.def.AbstractSaveEventListener.getEntityState(AbstractSaveEventListener.java:535) at org.hibernate.event.def.DefaultSaveOrUpdateEventListener.performSaveOrUpdate(DefaultSaveOrUpdateEventListener.java:103) ... etc, etc The com.cyclone.netPrefect.admin.restriction.complex.TimeSpanRestrictionItemEntity is mapped (with entity name TimeSpanRestrictionItem) as a joined subclass of the entity named RestrictionItem. I have had a look at the Hibernate source for 3.3.2.ga and it looks like problem is the way that the org.hibernate.tuple.entity.EntityMetamodel is using it entityNameByInheritenceClassNameMap field: * Puts to the map are based on PersistentClass.getMappedClass() as a key - a Class object * Gets from the map (in findEntityNameByEntityClass method) are using the class name Presumably (given the name of the map field) both put and get should be using the class 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

15 years, 11 months

10
20
0 / 0

[Hibernate-JIRA] Created: (HHH-5192) Can't use group_concat in mysql without creating a custom function

by Douglas Ferguson (JIRA)

Can't use group_concat in mysql without creating a custom function ------------------------------------------------------------------ Key: HHH-5192 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5192 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.1 Environment: Linux, Mysql Reporter: Douglas Ferguson After upgrading we starting getting the exception below and had to register a "custom" function.. Caused by: org.hibernate.HibernateException: Unable to locate mapping for function named [group_concat] at org.hibernate.criterion.AggregateProjection.getFunction(AggregateProjection.java:93) at org.hibernate.criterion.AggregateProjection.getFunction(AggregateProjection.java:85) at org.hibernate.criterion.AggregateProjection.getTypes(AggregateProjection.java:64) at org.hibernate.criterion.ProjectionList.getTypes(ProjectionList.java:61) at org.hibernate.loader.criteria.CriteriaQueryTranslator.getProjectedTypes(CriteriaQueryTranslator.java:362) at org.hibernate.loader.criteria.CriteriaJoinWalker.<init>(CriteriaJoinWalker.java:101) at org.hibernate.loader.criteria.CriteriaJoinWalker.<init>(CriteriaJoinWalker.java:83) at org.hibernate.loader.criteria.CriteriaLoader.<init>(CriteriaLoader.java:92) at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1687) at org.hibernate.impl.CriteriaImpl.list(CriteriaImpl.java:347) -- 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

15 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5273) RowCountProjection long to int cast exception

by Pamir Erdem (JIRA)

RowCountProjection long to int cast exception --------------------------------------------- Key: HHH-5273 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5273 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.2 Environment: hibernate-core 3.5.2 Reporter: Pamir Erdem After we upgraded our hibernate.jar from 3.3.2 to 3.5.2 the methods which executes rowcount functions have started to throw long to cast exception. >From the source code of hibernate, it is clear that for the features which will be implemented in 3.6 some implementations are changed. #http://opensource.atlassian.com/projects/hibernate/browse/HHH-5138 In 3.3.2 {code:title=RowCountProjection.java|borderStyle=solid} public Type[] getTypes(Criteria criteria, CriteriaQuery criteriaQuery) throws HibernateException { return new Type[] { Hibernate.INTEGER }; } {code} In 3.5.2 {code:title=RowCountProjection.java|borderStyle=solid} return new Type[] { getFunction( criteriaQuery ).getReturnType( null, criteriaQuery.getFactory() ) }; {code} But the definitions of the rowcount functions in both versions in same in Dialect.java {code} static { STANDARD_AGGREGATE_FUNCTIONS.put( "count", new StandardSQLFunction("count") { public Type getReturnType(Type columnType, Mapping mapping) { return Hibernate.LONG; } public String render(List args, SessionFactoryImplementor factory) { if ( args.size() > 1 ) { if ( "distinct".equalsIgnoreCase( args.get( 0 ).toString() ) ) { return renderCountDistinct( args ); } } return super.render( args, factory ); } {code} By this minor change in 3.5.2 all the project tests which executes count sql function are failing by throwing class cast exception -- 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

15 years, 11 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5098) AssertionFailure thrown when collection contains a parameterized type

by Kahli Burke (JIRA)

AssertionFailure thrown when collection contains a parameterized type --------------------------------------------------------------------- Key: HHH-5098 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5098 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.5.0-Final Reporter: Kahli Burke Attachments: patch.txt The following exception is thrown when an entity exists with a collection containing a parameterized type: ERROR [AssertionFailure] an assertion failure occured (this may indicate a bug in Hibernate): org.hibernate.annotations.common.AssertionFailure: Fail to process type argument in a generic declaration. Type: class sun.reflect.generics.reflectiveObjects.ParameterizedTypeImpl at org.hibernate.ejb.metamodel.AttributeFactory$PluralAttributeMetadataImpl.getClassFromGenericArgument(AttributeFactory.java:836) at org.hibernate.ejb.metamodel.AttributeFactory$PluralAttributeMetadataImpl.<init>(AttributeFactory.java:748) at org.hibernate.ejb.metamodel.AttributeFactory$PluralAttributeMetadataImpl.<init>(AttributeFactory.java:723) at org.hibernate.ejb.metamodel.AttributeFactory.determineAttributeMetadata(AttributeFactory.java:518) at org.hibernate.ejb.metamodel.AttributeFactory.buildAttribute(AttributeFactory.java:93) at org.hibernate.ejb.metamodel.MetadataContext.wrapUp(MetadataContext.java:183) at org.hibernate.ejb.metamodel.MetamodelImpl.buildMetamodel(MetamodelImpl.java:66) at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:83) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:883) at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73) at org.jboss.jpa.builder.DefaultCEMFBuilder.build(DefaultCEMFBuilder.java:47) at org.jboss.jpa.deployment.PersistenceUnitDeployment.start(PersistenceUnitDeployment.java:316) For example if a field exists like: @OneToMany List<SomeEntity<SomeClass>> associatedList; I've attached a patch that includes a test case for the entity-manager project and a proposed fix. -- 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

15 years, 11 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5252) AttributeFactory needs more info in AssertionFailure

by Travis Stevens (JIRA)

AttributeFactory needs more info in AssertionFailure ---------------------------------------------------- Key: HHH-5252 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5252 Project: Hibernate Core Issue Type: Improvement Components: entity-manager Affects Versions: 3.5.2, 3.5.0-Final Environment: Hibernate version: 3.5.0-Final Reporter: Travis Stevens Priority: Trivial Attachments: tstevens-em.patch An exception is thrown that doesn't provide information about what member hibernate is asserting for. Attached is a patch that will include the associated Member object to the exception in order to provide some context. -- 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

15 years, 11 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5062) In the Session.flush method has a lost of perfomance about 50% when flush a large amout of data

by Fabiano Cury (JIRA)

In the Session.flush method has a lost of perfomance about 50% when flush a large amout of data ----------------------------------------------------------------------------------------------- Key: HHH-5062 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5062 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.5.0-Final, 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: Linux / DB2 / version 3.2.6 and above Reporter: Fabiano Cury Attachments: issueHibernate.JPG When the flush method is called this method call the onFlush method of class DefaultFlushEventListener and then the method flushEverythingToExecutions(event). This method (flushEverythingToExecutions) call many times (loop) the method log.isDebugEnabled(). This cause a big overhead in this method. I suggest you to put an attribute in the method flushEverythingToExecutions(flushEverythingToExecutions(FlushEvent event, Boolean isDebugEnable) and verify this attribute before the loop for. Attached the print screen of profiling that help me to detect this issue. Tks. -- 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

15 years, 11 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3045) Duplicated column aliases in scalar query

by Anderson Souza (JIRA)

Duplicated column aliases in scalar query ----------------------------------------- Key: HHH-3045 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3045 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.4SP1, 3.2.5GA Oracle 10g Reporter: Anderson Souza Priority: Critical Attachments: ddl-tables.sql, dominio.zip The HQL bellow works fine, but when I add a call to a funcion in the select clause the SQL generated has duplicated aliases and it generate error on query execution, because the query is paginated. {code} select a from Area a inner join fetch a.horarioPadrao left outer join fetch a.horarioTemporario as hrtemp {code} The SQL generated for this query is: {code} select * from ( select area0_.cod_local as cod1_15_0_, horarioare1_.cod_area as cod1_6_1_, horarioare2_.cod_area as cod1_7_2_, area0_.des_local as des2_15_0_, area0_.sig_local as sig3_15_0_, area0_.flg_extinto as flg4_15_0_, horarioare1_.hr_hora_ini as hr2_6_1_, horarioare1_.hr_hora_fim as hr3_6_1_, horarioare1_.flg_fim_semana as flg4_6_1_, horarioare2_.hr_hora_ini as hr2_7_2_, horarioare2_.hr_hora_fim as hr3_7_2_, horarioare2_.flg_fim_semana as flg4_7_2_, horarioare2_.dat_ini_vigencia as dat5_7_2_, horarioare2_.dat_fim_vigencia as dat6_7_2_ from esq_fp.tb_local area0_ inner join tb_horario_local_padrao horarioare1_ on area0_.cod_local=horarioare1_.cod_area left outer join tb_horario_local_temporario horarioare2_ on area0_.cod_local=horarioare2_.cod_area where 1=1 order by area0_.sig_local ) where rownum <= ? {code} The scalar HQL query that generate duplicated column names is: {code} select a, count(*) from Area a inner join fetch a.horarioPadrao left outer join fetch a.horarioTemporario as hrtemp {code} The SQL generated is: {code} select * from ( select area0_.cod_local as col_0_0_, count(*) as col_1_0_, horarioare1_.cod_area as cod1_6_1_, horarioare2_.cod_area as cod1_7_2_, area0_.cod_local as cod1_15_0_, horarioare1_.cod_area as cod1_6_1_, horarioare2_.cod_area as cod1_7_2_, area0_.des_local as des2_15_0_, area0_.sig_local as sig3_15_0_, area0_.flg_extinto as flg4_15_0_, horarioare1_.hr_hora_ini as hr2_6_1_, horarioare1_.hr_hora_fim as hr3_6_1_, horarioare1_.flg_fim_semana as flg4_6_1_, horarioare2_.hr_hora_ini as hr2_7_2_, horarioare2_.hr_hora_fim as hr3_7_2_, horarioare2_.flg_fim_semana as flg4_7_2_, horarioare2_.dat_ini_vigencia as dat5_7_2_, horarioare2_.dat_fim_vigencia as dat6_7_2_ from esq_fp.tb_local area0_ inner join tb_horario_local_padrao horarioare1_ on area0_.cod_local=horarioare1_.cod_area left outer join tb_horario_local_temporario horarioare2_ on area0_.cod_local=horarioare2_.cod_area where 1=1 order by area0_.sig_local ) where rownum <= ? {code} As you can see the aliases cod1_6_1_ and cod1_7_2_ are repeated and this repetition breaks the paginated query, beacause the main query appears in the from clause. The HBM's and classes are attached. -- 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

15 years, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4053) Incorrect SQL with substring for Firebird

by yeti the foot (JIRA)

Incorrect SQL with substring for Firebird ----------------------------------------- Key: HHH-4053 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4053 Project: Hibernate Core Issue Type: Bug Components: query-sql Affects Versions: 3.3.1 Reporter: yeti the foot HQL query substring function generate incorrect SQL query for Firebird. In Firebird SQL query with substring has follow syntax: substring(str from 1 for 3). Generated ин Hibernate query looks like: substring(str, 1, 3). -- 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

15 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2190) JDBCTransaction.isActive() should report false if jdbcContext.connection().isClosed()

by Jeffrey Bennett (JIRA)

JDBCTransaction.isActive() should report false if jdbcContext.connection().isClosed() ------------------------------------------------------------------------------------- Key: HHH-2190 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2190 Project: Hibernate3 Type: Bug Components: core Reporter: Jeffrey Bennett In error-handling routines, I use Transaction.isActive() to determine if it is 'safe' to perform Transaction.rollback(). If the Session has previously closed, Transaction.isActive() mis-reports that the transaction is still alive when it is not. I'll grant that the JavaDoc for isActive indicates it is the 'local transaction', not the underlying transaction, but since there is no way to delve into the underlying connection in the public API, that is really a cop-out. If you don't like the idea of modifying the behavior of isActive(), how about exposing a 'public Connection connection()' method that exposes the connection? -- 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

15 years, 11 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3058) When using native sql query and multiple selects with setMaxResults, Hibernate inserts the TOP statement in the first query

by Sean Blaes (JIRA)

When using native sql query and multiple selects with setMaxResults, Hibernate inserts the TOP statement in the first query --------------------------------------------------------------------------------------------------------------------------- Key: HHH-3058 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3058 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.4.sp1 Environment: Hibernate 3.2.4sp1, Microsoft SQL Server Reporter: Sean Blaes Priority: Minor When using a query similar to the following: DECLARE @SUB_TABLE TABLE( ID INT ) INSERT INTO @SUB_TABLE SELECT ID FROM FOO SELECT * FROM BAR INNER JOIN @SUB_TABLE ON ... Then if I call setMaxResults(100) on the query object. It inserts "TOP 100" in the first query, which isn't really what would be expected. Since the second SELECT actually consists of the data that will be returned, the TOP 100 statement should go there. I'd expect it's an easy fix. Just start your search for SELECT from the bottom rather than the top. However, I guess you have to make sure you're not hitting a subquery of a larger select either... I may try cooking up a patch this weekend for this if I can find the time, and I'll attach it to this issue if I do. -- 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

15 years, 11 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3405) Add support for Unicode aware MS SQL Server dialect

by Chris Larun (JIRA)

Add support for Unicode aware MS SQL Server dialect --------------------------------------------------- Key: HHH-3405 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3405 Project: Hibernate3 Issue Type: New Feature Components: core Affects Versions: 3.2.6 Reporter: Chris Larun Cf. http://jira.atlassian.com/browse/CONF-4786 for a description of the issue. http://forum.hibernate.org/viewtopic.php?t=941781&highlight=sqlserver+dia... for a possible solution. -- 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

15 years, 11 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3905) Improve FieldInterceptionHelper perfomance

by Sergey Vladimirov (JIRA)

Improve FieldInterceptionHelper perfomance ------------------------------------------ Key: HHH-3905 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3905 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.3.1 Reporter: Sergey Vladimirov Priority: Minor Attachments: patch.txt do not iterate over interfaces, use Class.isAssignableFrom -- 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

15 years, 11 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5262) Allow UserType and CompositeUserType to be registered with BasicTypeRegistry

by Steve Ebersole (JIRA)

Allow UserType and CompositeUserType to be registered with BasicTypeRegistry ---------------------------------------------------------------------------- Key: HHH-5262 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5262 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6 The implication here is that CustomType and CompositeCustomType need to (1) derive from the BasicType interface and (2) allow the user to configure the registration keys. 2 options for registration keys: # new (optional) interface, RegisterableUserType # allow passing the keys during registration via Configuration -- 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

15 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5268) Support for java.util.UUID properties/generators

by Steve Ebersole (JIRA)

Support for java.util.UUID properties/generators ------------------------------------------------ Key: HHH-5268 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5268 Project: Hibernate Core Issue Type: Improvement Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.x See discussion on dev mailing list : http://lists.jboss.org/pipermail/hibernate-dev/2010-May/005209.html -- 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

15 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-1989) Deleted object remains referenced in 2nd level cache collections

by Justin Haddad (JIRA)

Deleted object remains referenced in 2nd level cache collections ---------------------------------------------------------------- Key: HHH-1989 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1989 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2 Environment: Spring 1.2.8, Hibernate 3.2, Postgres 8.0.3 Reporter: Justin Haddad This problem seems identical to issue NH-678. I have enabled caching for an one-to-many association. I use Ehcache. I have a test in which I load the parent object along with its collection. Both the parent and the collection wind up in the 2nd level cache. I then delete an object that is in the collection, not by removing it from the collection, but rather by doing a delete on the object itself. After deleting, I try to reload the parent and get the following exception (User#3102 is the deleted object): aused by: org.hibernate.ObjectNotFoundException: No row with the given identifier exists: [com.bluenotenetworks.common.management.sm.User#3102] at org.hibernate.impl.SessionFactoryImpl$1.handleEntityNotFound(SessionFactoryImpl.java:372) at org.hibernate.event.def.DefaultLoadEventListener.load(DefaultLoadEventListener.java:128) at org.hibernate.event.def.DefaultLoadEventListener.proxyOrLoad(DefaultLoadEventListener.java:178) at org.hibernate.event.def.DefaultLoadEventListener.onLoad(DefaultLoadEventListener.java:86) at org.hibernate.impl.SessionImpl.fireLoad(SessionImpl.java:871) at org.hibernate.impl.SessionImpl.internalLoad(SessionImpl.java:839) at org.hibernate.type.EntityType.resolveIdentifier(EntityType.java:266) at org.hibernate.type.ManyToOneType.assemble(ManyToOneType.java:177) at org.hibernate.collection.PersistentSet.initializeFromCache(PersistentSet.java:101) at org.hibernate.cache.entry.CollectionCacheEntry.assemble(CollectionCacheEntry.java:35) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.initializeCollectionFromCache(DefaultInitializeCollectionEventListener.java:130) at org.hibernate.event.def.DefaultInitializeCollectionEventListener.onInitializeCollection(DefaultInitializeCollectionEventListener.java:48) at org.hibernate.impl.SessionImpl.initializeCollection(SessionImpl.java:1705) (continues on) I stepped through the code in the debugger and can see that the object's ID (3102 in this case) remains in the cached collection even after the deletion. -- 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

15 years, 11 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5228) In Envers, retrieve only the most recent revision for all entities of a particular type

by Edwin Tellman (JIRA)

In Envers, retrieve only the most recent revision for all entities of a particular type --------------------------------------------------------------------------------------- Key: HHH-5228 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5228 Project: Hibernate Core Issue Type: Improvement Components: envers Affects Versions: 3.3.2 Environment: any Reporter: Edwin Tellman Priority: Minor I would like to retrieve the most recent version of everything that has changed since a specified revision. This is useful for keeping one application synchronized with another. One system polls the other and the second system provides the current state of things that have changed recently. This query fetches everything that has changed since the specified revision: AuditQuery query = auditReader.createQuery() .forRevisionsOfEntity(entityClass, false, true) .add(AuditEntity.revisionNumber().gt(revision)) If I add a maximize restriction on the revision number, I get a single item which changed at the highest revision number, which isn't what I'm looking for. You could find the right data in SQL or HQL by grouping by ID and then selecting the maximum revision from each group. And, of course, I can use the above query and then filter out the older items from the result in Java, which is what I'm doing now. -- 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

15 years, 11 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3075) Should be possible to register UserTypes for known property types (classes) in configuration

by Martin Probst (JIRA)

Should be possible to register UserTypes for known property types (classes) in configuration -------------------------------------------------------------------------------------------- Key: HHH-3075 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3075 Project: Hibernate3 Issue Type: Improvement Components: core Environment: n/a Reporter: Martin Probst Priority: Minor Currently, when persisting primitive properties of a class that are not known to Hibernate, there are only cumbersome ways to tell Hibernate that a certain UserType should be used. Good example is Joda Time: <pre> @Entity class MyClass { org.joda.time.DateTime foo; } </pre> .. which will result in ugly binary fields in database. Next try: <pre> @Entity class MyClass { @Type(type = "org.joda.time.contrib.hibernate.PersistentDateTime") org.joda.time.DateTime foo; } </pre> That works, but now I have to specify that on all time fields of all classes. Plus it's different types for different classes, which makes it more messy. And it's simply a string in code, so it's fragile to refactoring, code move, etc. TypeDefs allow a shorter handle for certain types, but don't really address the refactoring issues. A better way might be to allow configurations to register UserTypes for known classes. E.g. have a configuration directive like this: <mappable-type class="org.joda.time.DateTime" usertype="org.joda.time.hibernate.DateTimeType"/> This would allow the classes to stay clean from type mappings and reduce coupling between domain objects and persistence mapping. This might be as easy as allowing the org.hibernate.type.TypeFactory map to be extended at configuration time. -- 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

15 years, 11 months

3
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-13) Fetch groups

by Sebastien Tardif (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-13?page=com... ] Sebastien Tardif commented on HHH-13: ------------------------------------- GK said: the "fetch group" notion does not work with annotations You can see an annotation example here: http://openjpa.apache.org/builds/1.0.2/apache-openjpa-1.0.2/docs/manual/r... > Fetch groups > ------------ > > Key: HHH-13 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-13 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Affects Versions: 3.1 rc3 > Reporter: Adrien > > I don't like JDO at all, but it may have a good feature : the fetch groups. Instead of saying in each request which relations (or property now) I want to be fetch, I could says which fetch groups I want to be loaded. I will be usefull for complex objects will lot of relationship. Each fetch group will represent a view to the object. > from Contract c > left join fetch c.customer > left join fetch c.items > left join fetch c.foo > ==> > from Contract c > left join fetch c.fetchGroup1 > with : > <many-to-one name="customer" fetch-group="fetchGroup1" /> > <set name="items" fetch-group="fetchGroup1, fetchGroup2" > > <many-to-one name="foo" fetch-group="fetchGroup1" /> > > Adrien -- 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

15 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5279) Performance: a lot of time is spent getting and setting the auto-commit flag. Suggest it be configurable

by Phillip Henry (JIRA)

Performance: a lot of time is spent getting and setting the auto-commit flag. Suggest it be configurable -------------------------------------------------------------------------------------------------------- Key: HHH-5279 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5279 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.5.2 Environment: Seen in Hibernate 3.2 but appears to still be in Trunk Reporter: Phillip Henry Priority: Minor In org.hibernate.transaction.JDBCTransaction, a call to getAutoCommit is made on the connection at the start of the transaction and if it returns true, a setAutoCommit(true) is made after Hibernate has finished. These calls may be network calls (they certainly are with Sybase JConnect 5.5 drivers. They may be with others as well) and they are done in the same thread as that executing my INSERT/UPDATE commands. This means that about 25% of the time spent making a simple Session.saveOrUpdate is spent on something that is not important to me (in my application, I am not sharing the connection pool with other services so I don't care about the auto-commit status of connections when they are in the pool). It would be nice if I could speed up my application a little by setting an optional flag that indicates to JDBCTransaction whether it should care or not about the state of the connection when it has finished with it. Or, to have this work done by another thread. See http://javaagile.blogspot.com/2010/05/hibernate-and-performance-tuning.html for YourKit profiles. -- 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

15 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5278) Wrong parsing of hql/ejbql query

by ron piterman (JIRA)

Wrong parsing of hql/ejbql query -------------------------------- Key: HHH-5278 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5278 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.2 Reporter: ron piterman Attachments: hibtest.tar.gz Hibernate parses following query, ignoring superfluous parentheses and rules after: FROM Parent AS p WHERE p.id = ? ) AND p.child is null Attached is a test which should not pass. -- 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

15 years, 11 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HV-326) Verify that for caching user objects during the validation process we use a IdentityHashMap or IdentityHashSet

by Emmanuel Bernard (JIRA)

Verify that for caching user objects during the validation process we use a IdentityHashMap or IdentityHashSet -------------------------------------------------------------------------------------------------------------- Key: HV-326 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-326 Project: Hibernate Validator Issue Type: Bug Components: engine Affects Versions: 4.0.1.GA Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik Fix For: 4.1.0 -- 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

15 years, 11 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5271) Support for Sybase IQ database in StandardDialectResolver

by Anton Nikitin (JIRA)

Support for Sybase IQ database in StandardDialectResolver --------------------------------------------------------- Key: HHH-5271 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5271 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.5.2 Reporter: Anton Nikitin Priority: Minor During our experiments we have found that StandardDialectResolver is not able to determine dialect for Sybase IQ 15.1 database. I recommend to include the check for getDatabaseProductName().startsWith("Sybase IQ") and return SybaseAnywhereDialect for it. -- 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

15 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5004) Specifying entity access type at class level and then redundantly again on id field or getId() causes EntityManagerFactory configuration failure

by Jesse Hutton (JIRA)

Specifying entity access type at class level and then redundantly again on id field or getId() causes EntityManagerFactory configuration failure ------------------------------------------------------------------------------------------------------------------------------------------------ Key: HHH-5004 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5004 Project: Hibernate Core Issue Type: Bug Components: annotations, entity-manager Affects Versions: 3.5.0-CR-2 Environment: I'm developing on Fedora 12 64bit version. java version: Java(TM) SE Runtime Environment (build 1.6.0_18-b07) Reporter: Jesse Hutton Priority: Minor Attachments: testHibernate.tar.gz If you annotation an entity class with @Access and either AccessType.FIELD or AccessType.PROPERTY and then repeat the same respective access annotation for identifier of the class, hibernate will not be able to find the identifier. An example stack trace is: javax.persistence.PersistenceException: [PersistenceUnit: testhibernate] Unable to configure EntityManagerFactory ... Caused by: org.hibernate.AnnotationException: No identifier specified for entity: com.mycompany.testhibernate.Foo ... To annotate a class as such is clearly redundant, but it doesn't seem like it should really cause this error. I happened to have discovered it while experimenting with different access type options in JPA 2 using EclipseLink, forgetting to remove an access type annotation to the getId() method of my entity, and then eventually switching JPA providers to Hibernate. Under EclipseLink, there was no problem with the redundant annotations. Attached is a sample test app illustrating the problem. It has access PROPERTY specified, but the error occurs with FIELD just the same. -- 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

15 years, 11 months

4
6
0 / 0

[Hibernate-JIRA] Created: (HHH-5270) Oracle Error ORA-01719 on @ManyToMany associations with @FilterJoinTable annotation

by Nico Mack (JIRA)

Oracle Error ORA-01719 on @ManyToMany associations with @FilterJoinTable annotation ----------------------------------------------------------------------------------- Key: HHH-5270 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5270 Project: Hibernate Core Issue Type: Bug Components: query-hql Environment: Hibernate 3.4.0GA (shipped with JBoss 5.1GA) Oracle 11R2 Standard Edition Reporter: Nico Mack I have an User EJB Bean who can be assigned via a relation table any number of roles. The following mapping in my User Bean @ManyToMany(fetch = FetchType.LAZY) @FilterJoinTable(name = "contextFilter", condition = "context_id = :contextId OR context_id IS NULL") @JoinTable(name = "rel_user_role", schema = "usermanagement", joinColumns = {@JoinColumn(name = "user_id")}, inverseJoinColumns = {@JoinColumn(name = "role_id")}) public Set <Role> getRoles() { return m_Roles; } results in the following query being generated: select roles0_.user_id as user4_1_, roles0_.role_id as role3_1_, role1_.id as id5_0_, role1_.created as created5_0_, role1_.creator as creator5_0_, role1_.modified as modified5_0_, role1_.modifier as modifier5_0_, role1_.description as descript4_5_0_, role1_.name as name5_0_ from usermanagement.rel_user_role roles0_, usermanagement.role role1_ where roles0_.role_id=role1_.id(+) and roles0_.context_id = ? OR roles0_.context_id IS NULL and roles0_.user_id=? which in turn causes the following oracle error: java.sql.SQLException: ORA-01719: outer join operator (+) not allowed in operand of OR or IN -- 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

15 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HCANN-24) @PrimaryKeyJoinColumn and @ForeignKey(name = "FOREIGN_FOOBAR") don't work for InheritanceType.JOINED

by Marcin Cinik (JIRA)

@PrimaryKeyJoinColumn and @ForeignKey(name = "FOREIGN_FOOBAR") don't work for InheritanceType.JOINED ---------------------------------------------------------------------------------------------------- Key: HCANN-24 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-24 Project: Hibernate Commons Annotations Issue Type: Bug Affects Versions: 3.2.0 Environment: dialect: Oracle10g Reporter: Marcin Cinik Attachments: jpr.zip, schema2.ddl I've got an example where I have two classes: Customer, ValuedCustomer, where ValuedCustomer inherits from Customer. As InheritanceType.JOINED is used here, hibernate will generate a primary key in ValuedCustomer as well as all integrity constraints for that (I use Oracle10g dialect). I would like to give a name to that foreign key in ValuedCustomer (which is also a primary key there), but it's not possible. In ValuedCustomer I use @PrimaryKeyJoinColumn annotation and @org.hibernate.annotations.Table with foreignKey property set in it. I would like that hibernate hbm2ddl generate foreign key constraint name as indicated in @ForeignKey annotation but it doesn't. It generates random constraint name instead. I'm attaching example java project and generated schema file. -- 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

15 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5269) Schema specified in @Table annotation should be passed as a parameter to the SequenceGenerator generate method.

by Nico Mack (JIRA)

Schema specified in @Table annotation should be passed as a parameter to the SequenceGenerator generate method. --------------------------------------------------------------------------------------------------------------- Key: HHH-5269 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5269 Project: Hibernate Core Issue Type: Improvement Components: core Environment: Hibernate 3.4.0GA (bundled with JBoss5.1GA) Reporter: Nico Mack Priority: Minor In the scope of a recent project built on JBoss5.1GA and using Oracle as a database we came up with the following architecture. Since all our EJBs are going to need an Id, we put the ID property in a class, called CoreEntityBean with the @MappedSuperclass annotation. Here's what the getId method looks like: @Id @GeneratedValue(generator="my_gen") @GenericGenerator(name = "my_gen", strategy = "my_package.TableNameSequenceGenerator") @Column(name = "id") public Integer getId() { return this.Id; } All our actual EJBs inherit from this CoreEntityBean, and are mapped using @Table annotations to tables in different schemas: @Entity @Table(name = "info", schema = "core") public class CoreInfo extends CoreEntityBean { Our custom TableNameSequenceGenerator basically takes the name of the table and adds the suffix "_seq" to determine the name of the sequence for the corresponding table. All sequences have been created beforehand, in the same schema the corresponding table is located. Here's what the generate method of our TableNameSequenceGenerator looks like: @Override public void configure (Type p_Type, Properties p_Parameters, Dialect p_Dialect) throws MappingException { String l_TableName; String l_SequenceName; String l_SchemaName; l_SequenceName = p_Parameters.getProperty(SequenceGenerator.SEQUENCE); if ((l_SequenceName == null) || (l_SequenceName.length() == 0)) { l_TableName = p_Parameters.getProperty(PersistentIdentifierGenerator.TABLE); l_SchemaName = p_Parameters.getProperty(PersistentIdentifierGenerator.SCHEMA); if (l_TableName != null) { l_SequenceName = (l_SchemaName != null)?l_SchemaName + "." + l_TableName + "_seq":l_TableName + "_seq"; p_Parameters.setProperty(SequenceGenerator.SEQUENCE, l_SequenceName); m_Logger.log(Level.INFO, "Sequence Name = " + l_SequenceName); } } super.configure (p_Type,p_Parameters,p_Dialect); } When single-stepping through the generate method, we came to realize that the SCHEMA property was never set and as a consequence the db sequences are not found. I'm not sure whether this issue has already been fixed in a later version or not. If not, I thought it would be useful to add the schema to the properties passed to the SequenceGenerator. -- 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

15 years, 11 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-293) Annotation processor fails in Eclipse when evaluating custom constraints not defined in the current project

by Gunnar Morling (JIRA)

Annotation processor fails in Eclipse when evaluating custom constraints not defined in the current project ----------------------------------------------------------------------------------------------------------- Key: HV-293 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-293 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.1.0-Beta-1 Reporter: Gunnar Morling Assignee: Hardy Ferentschik In certain situations the AP fails when being integrated in Eclipse with the following exception: java.lang.AssertionError: Class org.hibernate.validator.constraints.impl.LengthValidator specified in @Constraint.validatedBy doesn't implement ConstraintValidator. at org.hibernate.validator.ap.util.ConstraintHelper.getConstraintValidatorSuperType(ConstraintHelper.java:497) at org.hibernate.validator.ap.util.ConstraintHelper.getSupportedType(ConstraintHelper.java:426) at org.hibernate.validator.ap.util.ConstraintHelper.getSupportedTypes(ConstraintHelper.java:402) at org.hibernate.validator.ap.util.ConstraintHelper.checkCustomConstraint(ConstraintHelper.java:356) at org.hibernate.validator.ap.util.ConstraintHelper.checkConstraint(ConstraintHelper.java:295) at org.hibernate.validator.ap.ConstraintAnnotationVisitor.checkConstraintAtField(ConstraintAnnotationVisitor.java:290) at org.hibernate.validator.ap.ConstraintAnnotationVisitor.visitVariableAsField(ConstraintAnnotationVisitor.java:174) at org.hibernate.validator.ap.ConstraintAnnotationVisitor.visitVariableAsField(ConstraintAnnotationVisitor.java:45) at javax.lang.model.util.ElementKindVisitor6.visitVariable(ElementKindVisitor6.java:199) at org.eclipse.jdt.internal.compiler.apt.model.VariableElementImpl.accept(VariableElementImpl.java:55) at org.hibernate.validator.ap.ConstraintValidationProcessor.process(ConstraintValidationProcessor.java:84) at org.eclipse.jdt.internal.compiler.apt.dispatch.RoundDispatcher.handleProcessor(RoundDispatcher.java:139) at org.eclipse.jdt.internal.compiler.apt.dispatch.RoundDispatcher.round(RoundDispatcher.java:121) at org.eclipse.jdt.internal.compiler.apt.dispatch.BaseAnnotationProcessorManager.processAnnotations(BaseAnnotationProcessorManager.java:159) at org.eclipse.jdt.internal.apt.pluggable.core.dispatch.IdeAnnotationProcessorManager.processAnnotations(IdeAnnotationProcessorManager.java:134) at org.eclipse.jdt.internal.compiler.Compiler.processAnnotations(Compiler.java:810) at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:428) at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:364) at org.eclipse.jdt.internal.core.builder.IncrementalImageBuilder.compile(IncrementalImageBuilder.java:321) at org.eclipse.jdt.internal.core.builder.AbstractImageBuilder.compile(AbstractImageBuilder.java:301) at org.eclipse.jdt.internal.core.builder.IncrementalImageBuilder.build(IncrementalImageBuilder.java:134) at org.eclipse.jdt.internal.core.builder.JavaBuilder.buildDeltas(JavaBuilder.java:265) at org.eclipse.jdt.internal.core.builder.JavaBuilder.build(JavaBuilder.java:193) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:627) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) This happens, if the AP examines a constraint annotation, which is not defined in the currently built project itself, but is imported from some other JAR (e.g. @Length from HV): public class TestModel { @Length private String test; } The problem occurs, regardless whether the JAR containing the constraint is on the AP classpath or not. The AP works as expected when running on javac. -- 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

15 years, 11 months

2
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4436) Stackoverflow exception if Composite id has many to one relationship and fetchMode = EAGER

by Kirill Trofimov (JIRA)

Stackoverflow exception if Composite id has many to one relationship and fetchMode = EAGER ------------------------------------------------------------------------------------------ Key: HHH-4436 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4436 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.0.SP1 Environment: hibernate-core: 3.3.0.SP1, hibernate-annotations: 3.4.0.GA Reporter: Kirill Trofimov Attachments: hibernatetest.zip Stackoverflow occurred if composite id has many to one relationshipt. See unit test in attached file. -- 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

15 years, 11 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-4868) Upgrade to Javassist 3.11.GA

by Julien Kronegg (JIRA)

Upgrade to Javassist 3.11.GA ---------------------------- Key: HHH-4868 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4868 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.5.0-Beta-4, 3.3.2, 3.3.1 Reporter: Julien Kronegg Priority: Minor Hibernate 3.3.1 uses Javassist 3.4.GA (3.5 years old) Hibernate 3.3.2 uses Javassist 3.9.GA (1.5 years old) Hibernate 3.5.0 uses Javassist 3.9.GA (1.5 years old) -- 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

15 years, 11 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4738) getSingleResult returning SQLException in DerbyDialect

by Samuel Halliday (JIRA)

getSingleResult returning SQLException in DerbyDialect ------------------------------------------------------ Key: HHH-4738 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4738 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.5.0-Beta-2 Environment: hibernate 3.5.0-0.2, Glassfish v3, Derby Reporter: Samuel Halliday I am encountering problems when issuing getSingleResult queries using the Glassfish v3 "hibernate 3.5.0-0.2". These queries work fine if I use hibernate 3.3.1.GA, or a PostgreSQL backend/dialect. Something between 3.3.1 and 3.5 has therefore introduced this bug. The queries are along the lines of [code] Query q = em.createQuery("SELECT COUNT(s) FROM MyTable s"); Long result = (Long) q.getSingleResult(); [/code] and [code] Query query = em.createQuery("SELECT s FROM MyTable s ORDER BY s.id"); query.setFirstResult(id); query.setMaxResults(1); MyTable random = (MyTable) query.getSingleResult(); [/code] The exception I am seeing is below, when used with (at least) the Java Derby DB. The message is "The column position '1' is out of range. The number of columns for this ResultSet is '0'." [code] Caused by: java.sql.SQLException: The column position '1' is out of range. The number of columns for this ResultSet is '0'. at org.apache.derby.client.am.SQLExceptionFactory40.getSQLException(Unknown Source) at org.apache.derby.client.am.SqlException.getSQLException(Unknown Source) at org.apache.derby.client.am.ColumnMetaData.getColumnType(Unknown Source) at org.apache.derby.client.am.PreparedStatement.setInt(Unknown Source) at org.hibernate.loader.Loader.bindLimitParameters(Loader.java:1669) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1594) at org.hibernate.loader.Loader.doQuery(Loader.java:694) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:257) at org.hibernate.loader.Loader.doList(Loader.java:2232) ... 42 more Caused by: org.apache.derby.client.am.SqlException: The column position '1' is out of range. The number of columns for this ResultSet is '0'. at org.apache.derby.client.am.ColumnMetaData.checkForValidColumnIndex(Unknown Source) ... 49 more [/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

15 years, 11 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HCANN-21) EnumType speed up in initEnumValues()

by Ondrej Medek (JIRA)

EnumType speed up in initEnumValues() ------------------------------------- Key: HCANN-21 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-21 Project: Hibernate Commons Annotations Issue Type: Patch Affects Versions: 3.1.0.GA, 3.2.x Environment: Hibernate 3.5.1, Sun JDK 1.6.0_18 Reporter: Ondrej Medek Priority: Minor Attachments: EnumType.java.patch Hi, I have simplified and sped up the method EnumType.initEnumValues(). See the attached patch. Tested on Sun JDK 1.6.0_18 Note 1: I do not know, why the author (Emmanuel Bernard?) has used reflection. Maybe the method Class.getEnumConstants() in not implemented by other JREs (IBM, BEA) or he just didn't know this method.? Note: the method getEnumConstants() in SUN JRE does use the reflection to look for method "values()", too, but it's results are cached, so the second call to the getEnumConstants() is fast. And because the results are cached inside the Enum class itself, it does not cause any memory leaks like HHH-4317. -- 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

15 years, 11 months

3
4
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