September 2010 - hibernate-issues

[Hibernate-JIRA] Created: (HHH-3317) Entities saved within onPreUpdate() never inserted into db when id generator is sequenze (f.e. oracle)

by Martin Backhaus (JIRA)

Entities saved within onPreUpdate() never inserted into db when id generator is sequenze (f.e. oracle) ------------------------------------------------------------------------------------------------------ Key: HHH-3317 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3317 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: hibernate3.2.6.ga.jar, Oracle 10 Reporter: Martin Backhaus Priority: Minor If you save (insert) a entity within the event preUpdate and the id is a oracle-sequenze, hibernate put the entity to insert in the session-ActionQueue, BUT NEVER INSERTS it. If you use mysql/hsql... where the id is differently generated, the insert happens immediately and no put to the ActionQueue occures. As workaround you can queue the object (to insert) yourself and call save() within the postUpdate-Event. I use this events for historizing some stuff. Inserts within onDelete() works fine. the ids are annotated as shown here: @Id @GeneratedValue(strategy = GenerationType.AUTO) protected Long id = null; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
10
0 / 0

[Hibernate-JIRA] Created: (HHH-2657) Bulk select using primary key or natural id

by charbel (JIRA)

Bulk select using primary key or natural id ------------------------------------------- Key: HHH-2657 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2657 Project: Hibernate3 Issue Type: Improvement Reporter: charbel I think that the following methods are really useful once we use hibernate with huge datas in the database: Object[] get(Class,Object[] id): ---------------------------------------- return objects giving their primary key. First check in cache if it exists, if not either use a select in () either create a temporary table if too many ids. Object[] getUsingNaturalId(Class,Object[] id): ---------------------------------------- return objects giving their natural id. the same thing than before. Be careful on the fact that the primary key and the naturalid can be composite objects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2331) bulk deletes on ID must not use HT_ tables

by Amir Pashazadeh (JIRA)

bulk deletes on ID must not use HT_ tables ------------------------------------------ Key: HHH-2331 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2331 Project: Hibernate3 Type: Improvement Components: core Reporter: Amir Pashazadeh when using bulk deletes hibernate inserts ids of rows which must be deleted in a temporary table (with HT_ prefix); I believe that's just for knowing primary keys of objects which must be deleted and updating caches. so if that is the reason there is no need to do so when deleting on primary key property, (for example "delete from MyEntity where id = ?") -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-654) Generated SQL includes a column named "null" when referencing a map entry by key and using @LazyCollection(LazyCollectionOption.EXTRA)

by Paul Roe (JIRA)

Generated SQL includes a column named "null" when referencing a map entry by key and using @LazyCollection(LazyCollectionOption.EXTRA) -------------------------------------------------------------------------------------------------------------------------------------- Key: ANN-654 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-654 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.2.0.ga Environment: Oracle 10g, hibernate 3.2 Reporter: Paul Roe We have an Product entity with a map of RegionProduct by Region. @MapKey(name="region") @OneToMany(mappedBy="product", targetEntity= RegionProductImpl.class, fetch = FetchType.LAZY) @LazyCollection(LazyCollectionOption.EXTRA) private Map<Region, RegionProduct> regionProducts = new HashMap<Region, RegionProduct>(); When accessing an element of the map by key, the SQL that is generated includes a "null" column in the WHERE condition. where regionprod0_.PROD_ID=? and regionprod0_.null=? resulting in the stack trace org.hibernate.exception.SQLGrammarException: could not collection element by index at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:67) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.loader.Loader.loadEntity(Loader.java:1841) at org.hibernate.loader.entity.CollectionElementLoader.loadElement(CollectionElementLoader.java:72) at org.hibernate.persister.collection.OneToManyPersister.getElementByIndex(OneToManyPersister.java:360) at org.hibernate.collection.AbstractPersistentCollection.readElementByIndex(AbstractPersistentCollection.java:158) at org.hibernate.collection.PersistentMap.get(PersistentMap.java:146) Iterating over the collection works successfully, but populates the entire collection, which is what Extra-Lazy is meant to avoid. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

6
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3949) Intrumentated to one relations can not be join fetched

by Gérald Quintana (JIRA)

Intrumentated to one relations can not be join fetched ------------------------------------------------------ Key: HHH-3949 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3949 Project: Hibernate Core Issue Type: Bug Components: core, query-criteria, query-hql Affects Versions: 3.3.1 Reporter: Gérald Quintana 1) Relation Person -> Vehicle is annotated @OneToOne(optional=true, mappedBy="driver", fetch=FetchType.LAZY) @LazyToOne(LazyToOneOption.NO_PROXY) private Vehicle vehicle; 2) Both entities are instrumented with Javassist 3) Query (HQL or Criteria) Person and Vehicle: from Person p left join fetch p.vehicle => SQL query is correct but Vehicles are not loaded -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-4953) Inconsistent behavior when fetching cached subclass entities from 2L

by Guenther Demetz (JIRA)

Inconsistent behavior when fetching cached subclass entities from 2L -------------------------------------------------------------------- Key: HHH-4953 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4953 Project: Hibernate Core Issue Type: Bug Components: caching (L2) 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.1, 3.2.5 Environment: Hibernate3.5.0CR2,HSQLDB, EHCache as 2L-cache Impl Reporter: Guenther Demetz Attachments: Test2LCache.jar Enabling the hibernate second-level cache is leading to inconsistent behavior when fetching cached subclass entities as opposed to fetching non-cached subclass entities. For more informations, please see https://forum.hibernate.org/viewtopic.php?f=1&t=1002880&p=2425931#p2425931 Testcase attached. Cause: IMHO the bug consists in the fact, that persister.getRootEntityName() instead to persister.getEntityName() is passed as 3thrd parameter to the constructor of CacheKey in most places where CacheKey is used, for example in DefaultLoadEventListener.java: new CacheKey( event.getEntityId(), persister.getIdentifierType(), persister.getRootEntityName(), source.getEntityMode(), source.getFactory() In this way the real entity name get swallowed and the type-saveness is not guaranteed anymore. Workaround: Subclass2 tofind = null; try { tofind = (Subclass2) em.find(Subclass2.class,"identifier1"); } catch (ClassCastException cc) { // swallow , this is a workaround } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3854) Issue with greedy loading of associations (default-lazy=false )

by Amar Singh (JIRA)

Issue with greedy loading of associations (default-lazy=false ) --------------------------------------------------------------- Key: HHH-3854 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3854 Project: Hibernate Core Issue Type: Bug Components: envers Environment: Hibernate - core 3.4.0-SNAPSHOT, Hibernate-envers (from trunk) Reporter: Amar Singh Attachments: greedy-loading.zip I have an Entity GP which has a many to one association to entity CA. <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping package="org.hibernate.envers.test.integration.onetoone.bidirectional" default-lazy="false"> <class name="BidirectionalRefIngPK" table="BIDIRECTIONAL_REFERENCING_ENTITY"> <id name="id" type="long" column="BIDIRECTIONAL_REFERENCING_ID" > <generator class="native"/> </id> <property name="data"/> <many-to-one name="reference" cascade="save-update" class="BidirectionalRefEdPK" column="BIDIRECTIONAL_REFERENCED_ID"/> </class> <class name="BidirectionalRefEdPK" table="BIDIRECTIONAL_REFERENCED_ENTITY"> <id name="longId" type="long" column="BIDIRECTIONAL_REFERENCED_ID"> <generator class="native"/> </id> <property name="data"/> </class> </hibernate-mapping> With this when I load a previous version of BidirectionalRefIngPK, the loading mechanism tries to create a proxy for BidirectionalRefEdPK, but in my case lazy is false so an internal call to createProxy will return NULL hence . This happens in ToOneIdMapper.java in method mapToEntityFromMap around line 82, which then internally calls for AbstractEntityTuplizer.java line 395 for getProxyFactory() ending in NULL pointer exception because proxy factory is null as mine is a greedy loading. TO REPRODUCE ~~~~~~~~~~~~~ Please find a zipped folder attached. The zipped file has 4 files: - GreedyLoading.java (actual testng test case) - BidirectionalRefEdPK.java (Entity 1) - BidirectionalRefIngPK.java (Entity 2) - greedyloading.hbm.xml Please place the three java files in its package (org.hibernate.envers.test.integration.onetoone.bidirectional), couldn't find the right package so created test case accordingly. Put the greedyloading.hbm.xml in src/test/resources. Now when testng runs GreedyLoading.java you should see NPE. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

7
11
0 / 0

[Hibernate-JIRA] Created: (HHH-5126) JPA Query with InExpression and Collection_valued_input_parameter Complains About Bad Syntax

by Guido Müller (JIRA)

JPA Query with InExpression and Collection_valued_input_parameter Complains About Bad Syntax -------------------------------------------------------------------------------------------- Key: HHH-5126 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5126 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.5.1 Reporter: Guido Müller Priority: Blocker JPA 2.0 spec final chapter 4.6.9 In Expressions In the spec there are 3 alternatives allowed for the query argument. For the 3rd alternative there are no parenthesis allowed. Hibernate seems to expect these illegal parenthesis. The error occurs within a named query in an entity 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

11 years, 5 months

6
16
0 / 0

[Hibernate-JIRA] Created: (HHH-3280) Remove OracleDialect and Oracle9Dialect

by Diego Plentz (JIRA)

Remove OracleDialect and Oracle9Dialect --------------------------------------- Key: HHH-3280 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3280 Project: Hibernate3 Issue Type: Deprecation Components: metamodel Reporter: Diego Plentz Fix For: 4.x Since they already really old ones. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 5 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2891) Query cache fails on many-to-many select

by Oleg Efimov (JIRA)

Query cache fails on many-to-many select ---------------------------------------- Key: HHH-2891 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2891 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.5 Reporter: Oleg Efimov I have two entities, User and Group, with many-to-many relation: -------------------------------------------------------------------------------------------------- User.hbm.xml <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping package="test.hibernate"> <class name="User" table="`USER`"> <id name="id" type="long" unsaved-value="null"> <column name="USER_ID" not-null="true"/> <generator class="native"/> </id> <property name="login"> <column name="LOGIN" not-null="true" length="255"/> </property> <bag name="groups" table="USER_GROUP" lazy="false" cascade="none"> <key column="USER_ID"/> <many-to-many class="Group" column="GROUP_ID"/> </bag> </class> </hibernate-mapping> -------------------------------------------------------------------------------------------------- Group.hbm.xml <?xml version="1.0"?> <!DOCTYPE hibernate-mapping PUBLIC "-//Hibernate/Hibernate Mapping DTD 3.0//EN" "http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd"> <hibernate-mapping package="test.hibernate"> <class name="Group" table="`GROUP`"> <id name="id" type="long" unsaved-value="null"> <column name="GROUP_ID" not-null="true"/> <generator class="native"/> </id> <property name="name"> <column name="GROUPNAME" not-null="true" length="100"/> </property> <bag name="users" table="USER_GROUP" lazy="true" inverse="true" cascade="all-delete-orphan"> <key column="GROUP_ID"/> <many-to-many class="User" column="USER_ID"/> </bag> </class> <query name="Group.select.by.login" cacheable="true"><![CDATA[ select user.groups from User user where user.login=? ]]> </query> </hibernate-mapping> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- test.hibernate.User and test.hibernate.Group classes are just simple beans. In Group.hbm.xml there is a query called "Group.select.by.login", it's intended to be cached. So I add corresponding properties to Hibernate configuraition: -------------------------------------------------------------------------------------------------- properties.put("hibernate.cache.provider_class", "org.hibernate.cache.EhCacheProvider"); properties.put("hibernate.cache.use_query_cache", "true"); ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Configuration has no extra parameters. Then I'm trying to execute the query two times: -------------------------------------------------------------------------------------------------- test fragment SessionFactory sessionFactory = configuration.buildSessionFactory(); Session session = null; try { session = sessionFactory.openSession(); Query query = session.getNamedQuery("Group.select.by.login"); List<Group> groups; groups = query.setParameter(0, "admin").list(); // +++++++++++++++This list() returns list of two Group objects, ok +++++++++++++++ System.out.println("-----------------------------------------------------------------------------------"); for (Group group : groups) { System.out.println(group.getName()); } System.out.println("-----------------------------------------------------------------------------------"); groups = query.setParameter(0, "admin").list(); // +++++++++++++++This list() returns list of two nulls +++++++++++++++ System.out.println("-----------------------------------------------------------------------------------"); for (Group group : groups) { System.out.println(group.getName()); } System.out.println("-----------------------------------------------------------------------------------"); } finally { if (session != null) { session.close(); } sessionFactory.close(); } ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The first query returns list of, in my case, two groups. The second query returns list of two nulls instead of the same list. I've investigated the problem, and found the following: Query return value is "user.groups", and during query analysis (org.hibernate.hql.ast.QueryTranslatorImpl:160) query return type is defined as "org.hibernate.type.BagType(test.hibernate.User.groups)". This seems to be the problem, as during query put operation org.hibernate.CollectionType.disassemble is called (org.hibernate.cache.StandardQueryCache:80), which simply returns null as owner is null. If this query is not a misuse, then I think, something is to be done at the time of analysis, so that return type be somewhat different. 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

11 years, 5 months

4
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2010