June 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-625) @OrderBy usage on a joined classes (when using join table) produces incorred SQL syntax.

by Dima Gutzeit (JIRA)

@OrderBy usage on a joined classes (when using join table) produces incorred SQL syntax. ---------------------------------------------------------------------------------------- Key: ANN-625 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-625 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Reporter: Dima Gutzeit Please consider the following mapping : @ManyToMany(cascade = {CascadeType.PERSIST, CascadeType.MERGE}, fetch = FetchType.LAZY) @IndexColumn(name = "ListIndex") @JoinTable(name = "odp_rulemanipulatorjoin", joinColumns = @JoinColumn(name = "RoutingRuleId"), inverseJoinColumns = @JoinColumn(name = "ManipulatorComponentId")) @OrderBy(value = "priority asc") public List<RoutingManipulationComponent> getManipulators() { if (manipulators == null) { manipulators = new ArrayList<RoutingManipulationComponent>(); } return manipulators; } *********************************** @Entity(name = "RoutingManipulationComponent") @DiscriminatorValue("RoutingManipulationComponent") public abstract class RoutingManipulationComponent extends RoutingComponent implements Initializable { /** * Applies the manipulation to the given context. * * @param context the routing context to manipulate * @return true if any manipulation was applied, false if no manipulation * occurred */ public abstract boolean apply(RoutingContext context); } ****************************************** @Entity(name = "RoutingComponent") @Inheritance(strategy = InheritanceType.SINGLE_TABLE) @DiscriminatorColumn(name = "RoutingComponentType", discriminatorType = DiscriminatorType.STRING) @DiscriminatorValue("RoutingComponent") @Table(name = "odp_routingcomponent") public abstract class RoutingComponent extends DialPlanProvisionalEntity { @Deprecated public RoutingComponent() { // blank } /** * @param name * @param description */ public RoutingComponent(String name, String description) { super(name, description); } } ******************************* @MappedSuperclass @Cache(usage = CacheConcurrencyStrategy.READ_WRITE) public abstract class DialPlanProvisionalEntity extends ProvisionalEntity implements Initializable { private Long entityId; private boolean visible = true; private int priority; /** * Not for direct instantiation - this constructor also serves as public * constructor for hibernate, jax-ws etc. <br> */ @Deprecated public DialPlanProvisionalEntity() { this("(no name set)", "(no description set)"); } /** * @param name * @param description */ public DialPlanProvisionalEntity(String name, String description) { creationDate = GregorianCalendar.getInstance(); // now } @Id @GeneratedValue(strategy = GenerationType.AUTO) @Override public Long getId() { return entityId; } @Override public void setId(Long ruleCollectionId) { this.entityId = ruleCollectionId; } /** * @return Returns the priority. */ public int getPriority() { return priority; } /** * @param priority The priority to set. */ public void setPriority(int priority) { this.priority = priority; } @Override public boolean equals(Object o) { if (this == o) { return true; } if (o == null || Hibernate.getClass(this) != Hibernate.getClass(o)) { return false; } final ProvisionalEntity other = (ProvisionalEntity) o; return MiscUtils.equalOrBothNull(this.getName(), other.getName()); } @Override public int hashCode() { String name = this.getName(); return getClass().getName().hashCode() + 13 * name.hashCode(); } } The above mapping should use the "priority" field to the ordering. SQL that is produced is : select criteria0_.RoutingRuleId as RoutingR1_1_, criteria0_.CriteriaComponentId as Criteria2_1_, criteria0_.ListIndex as ListIndex1_, routingcri1_.id as id73_0_, routingcri1_.creationDate as creation3_73_0_, routingcri1_.description as descript4_73_0_, routingcri1_.lastModificationDate as lastModi5_73_0_, routingcri1_.name as name73_0_, routingcri1_.predefined as predefined73_0_, routingcri1_.status as status73_0_, routingcri1_.priority as priority73_0_, routingcri1_.visible as visible73_0_, routingcri1_.matcher_id as matcher25_73_0_, routingcri1_.criterion_id as criterion27_73_0_, routingcri1_.location_id aslocation26_73_0_, routingcri1_.RoutingComponentType as RoutingC1_73_0_ from odp_rulecriteriajoin criteria0_ left outer join odp_routingcomponent as routingcri1_ on criteria0_.CriteriaComponentId=routingcri1_.id where criteria0_.RoutingRuleId=1 order by odp_routingcomponent .priority asc It is wrong since not the table alias is used in the order by clause, but the real table name. Mysql fails with exception that odp_rulecriteriajoin.priority is unknown table. Changing the query to include "order by criteria0_.priority asc" returns the correct result. -- 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

13 years, 9 months

9
22
0 / 0

[Hibernate-JIRA] Created: (HHH-5565) Memory leak is possible if changes for audited entities are outside of transaction

by Eugene Goroschenya (JIRA)

Memory leak is possible if changes for audited entities are outside of transaction ---------------------------------------------------------------------------------- Key: HHH-5565 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5565 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.3.1 Environment: hibernate-core-3.3.1.GA.jar, jboss-envers-1.2.1-hibernate-3.3.jar Reporter: Eugene Goroschenya Envers always collects changes for audited objects in global (global per sessionFactory instance) application map (auditConfiguration.auditSyncManager.auditSyncs<Transaction, AuditSync>) even if transaction is inactive. It leads to memory leak in application if there were changes (insert/update/delete) for versioned objects outside of transaction (transaction.isActive() == false) because in this case transaction is not committed where collected changes for current transaction are removed from global map. Possible solution is patch Envers to check if transaction is active (AuditEventListener in onPostInsert/onPostUpdate/onPostDeleteonCollectionAction methods) before starting collect changes for audited object. Skip collecting (to prevent memory leak) if transaction is inactive and log WARN message to indicate problem ("Couldn't create revision for entity ${entityName} because transaction is not active.") -- 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

13 years, 9 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-5411) Missing value in not updatable column in Envers audit table

by Laurent Grangier (JIRA)

Missing value in not updatable column in Envers audit table ----------------------------------------------------------- Key: HHH-5411 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5411 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.3.0.GA Environment: Hibernate 3.4 Reporter: Laurent Grangier When I update an entity with a property which is updatable=false and that the property is not filled when passing the object to Hibernate, the update is correctly made by Hibernate but Envers fill a null value in the given column in the audit table. Example : {code} public class MyEntity { private String myString; @Column(updatable = false) private Long myLong; (...) } MyEntity entity = new MyEntity(); entity.setMyString("example"); entity.setMyLong(123L); entityManager.persist(entity); Long entityId = entity.getId(); (...) MyEntity entity = new MyEntity(); entity.setId(entityId); entity.setMyString("new value"); entityManager.persist(entity); // Here Envers miss to fill the column myLong in the audit table ! {code} In the above example, in the audit table, the value of "myLong" will be "null" but I expected "123" instead. -- 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

13 years, 9 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-7311) NullPointerException if TenantConnectionProvider class does not exist

by Oriel Maute (JIRA)

NullPointerException if TenantConnectionProvider class does not exist --------------------------------------------------------------------- Key: HHH-7311 URL: https://hibernate.onjira.com/browse/HHH-7311 Project: Hibernate ORM Issue Type: Bug Components: core Affects Versions: 4.1.2 Environment: Hibernate 4.1.2, using JPA Reporter: Oriel Maute Priority: Trivial Im using schema based multi tenancy. If i define a "hibernate.multi_tenant_connection_provider" which classfile does not exist in persistence.xml, a NullPointerException come up: <property name="hibernate.multi_tenant_connection_provider" value="com.xoricon.framework.server.jpa.tenant.TenantConnectionProvider"/> Class "com.xoricon.framework.server.jpa.tenant.TenantConnectionProvider" does not exist on classpath. Result: 1) testTreeOrder(com.xoricon.persistence.bo.multitenancy.test.SchemaBasedMultiTenancyTest)java.lang.NullPointerException at org.hibernate.engine.jdbc.internal.JdbcServicesImpl$MultiTenantConnectionProviderJdbcConnectionAccess.obtainConnection(JdbcServicesImpl.java:260) at org.hibernate.engine.jdbc.internal.JdbcServicesImpl.configure(JdbcServicesImpl.java:117) at org.hibernate.service.internal.StandardServiceRegistryImpl.configureService(StandardServiceRegistryImpl.java:75) at org.hibernate.service.internal.AbstractServiceRegistryImpl.initializeService(AbstractServiceRegistryImpl.java:159) at org.hibernate.service.internal.AbstractServiceRegistryImpl.getService(AbstractServiceRegistryImpl.java:131) at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java:71) at org.hibernate.cfg.Configuration.buildSettingsInternal(Configuration.java:2274) at org.hibernate.cfg.Configuration.buildSettings(Configuration.java:2270) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1739) at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:93) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:905) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:890) at org.hibernate.ejb.HibernatePersistence.createEntityManagerFactory(HibernatePersistence.java:57) at javax.persistence.Persistence.createEntityManagerFactory(Persistence.java:48) at com.xoricon.persistence.bo.test.AbstractTestCase.getEntityManagerFactory(AbstractTestCase.java:45) at com.xoricon.persistence.bo.multitenancy.test.SchemaBasedMultiTenancyTest.testTreeOrder(SchemaBasedMultiTenancyTest.java:42) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at com.xoricon.persistence.bo.multitenancy.test.SchemaBasedMultiTenancyTest.main(SchemaBasedMultiTenancyTest.java:53) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

3
2
0 / 0

[Hibernate-JIRA] (HHH-7382) refact: unify the configuration implementation loading strategy

by Strong Liu (JIRA)

13 years, 9 months

1
2
0 / 0

[Hibernate-JIRA] (JPA-32) Setting cacheable="true" in orm.xml does not enable caching of entity in 2lc

by John O'Hara (JIRA)

13 years, 9 months

3
8
0 / 0

[Hibernate-JIRA] Created: (HHH-7310) Resolution of types registered in type registry does not work properly for Properties of @Embeddable types

by Chris Pheby (JIRA)

Resolution of types registered in type registry does not work properly for Properties of @Embeddable types ---------------------------------------------------------------------------------------------------------- Key: HHH-7310 URL: https://hibernate.onjira.com/browse/HHH-7310 Project: Hibernate ORM Issue Type: Bug Components: core Affects Versions: 4.1.3 Environment: Any Reporter: Chris Pheby The new type registry capability in Hibernate 4 and above is really useful. I have implemented an integrator that autoregisters some types, however what I have found is that whilst this works perfectly, the registered types are not being resolved correctly when they are used within @Embeddable classes. This is easily reproduced: for example, using Jadira Usertype (usertype.sourceforge.net), setting the system property to autoregister types and updating a test class to use @Embeddable triggers the problem. The problem occurs because the types are first initialised during a call to Configuration validate(). This occurs before any integrators are invoked and consequently types that will be mapped by the integrator at that time are mapped to either their existing basic type or Serializable. They are only remapped on future calls to getType on the type (such as within heuristic type). The resolution of the issue lies in removing the caching from Component because in the case of Component types these are not remapped on repeated calls to getType. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-5929) PooledLoOptimizer in conjunction with SequenceStyleGenerator is not thread-safe

by Robin Sander (JIRA)

PooledLoOptimizer in conjunction with SequenceStyleGenerator is not thread-safe ------------------------------------------------------------------------------- Key: HHH-5929 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5929 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.1 Environment: Hibernate 3.6.1, Java 6, Mac OS 10.6.6 Reporter: Robin Sander The generate method of the PooledLoOptimizer introduced in 3.6.1 is not synchronized in difference to the one in PooledOptimizer and in other Optimizer implementations. The problem is that some IdentifierGenerator implementations have themselve a synchronized generate method (like SequenceHiLoGenerator e.g.) and some don't, like the new SequenceStyleGenerator. According to the javadoc IdentifierGenerator implementations have to be thread-safe. Now I don't know if there is any agreement among the developers whether this thread-safety is to be achieved in the IdentifierGenerator itself or in the Optimizer most of them delegate to but what I know is that SequenceStyleGenerator in conjunction with PooledLoOptimizer is not thread-safe because neither of them guards against concurrent access in any way. -- 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

13 years, 9 months

3
3
0 / 0

[Hibernate-JIRA] (HHH-7380) bug when initialize MULTI_TENANT_IDENTIFIER_RESOLVER and CUSTOM_ENTITY_DIRTINESS_STRATEGY

by Strong Liu (JIRA)

13 years, 9 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6707) One-to-One mapping with foreign key in target table and foreign key being the primary key fails with Oracle

by Florian Rampp (JIRA)

One-to-One mapping with foreign key in target table and foreign key being the primary key fails with Oracle ----------------------------------------------------------------------------------------------------------- Key: HHH-6707 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6707 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.6 Environment: Oracle 11g, Oracle JDBC 11.2.0.1.0 Reporter: Florian Rampp Attachments: bugreports-hibernate-oracleUniquePk-1.0-SNAPSHOT-src.zip When mapping a one-to-one parent/child relationship with the foreign key being in the child table and forming its primary key, in addition to the primary key definition, a unique constraint is generated (due to the one-to-one inverse mapping). A unique constraint and a primary key definition on the same column is not accepted by Oracle. The error is "ORA-02261: such unique or primary key already exists in the table" when creating the schema. The key entities: {code:java} @Entity public class Parent { @Id Long id; @OneToOne(cascade = CascadeType.ALL, orphanRemoval = true, mappedBy = "parent") Child child; } @Entity public class Child implements Serializable { @Id @OneToOne(optional = false) private Parent parent; } {code} The resulting DDL is: {code:sql} create table Child ( parent_id number(19,0) not null, primary key (parent_id), unique (parent_id) ) {code} This issue is similar to https://hibernate.onjira.com/browse/HBX-978. But I refiled it here since I consider it to be a bug in Hibernate core. Also, I provided a test case that can be used for regression tests. It needs to be executed with the arguments {{-Dhibernate.connection.username=<USERNAME> -Dhibernate.connection.password=<PASSWORD> -Dhibernate.connection.url=<JDBC_URL>}}. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 9 months

2
1
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 June 2012