March 2009 - hibernate-issues - Jboss List Archives

[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-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, 6 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, 6 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2049) LEFT OUTER JOIN subcriteria filters children

by Mattias Jiderhamn (JIRA)

LEFT OUTER JOIN subcriteria filters children -------------------------------------------- Key: HHH-2049 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2049 Project: Hibernate3 Type: Bug Components: query-criteria Versions: 3.1.3, 3.2.0.cr4 Environment: Hibernate 3.1.3/3.2.0rc4, hsqldb 1.8 Reporter: Mattias Jiderhamn Attachments: SubCriteriaTestCase.zip When using the Criteria API with LEFT OUTER JOIN to add criterias to the children, i.e. criteria.createCriteria("children", JoinFragment.LEFT_OUTER_JOIN) the child collections will only contain those children matching the criteria. (Even when *not* using any Filters). The attached testcase (also found here: http://forum.hibernate.org/viewtopic.php?p=2320786) will explain it in more detail. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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, 6 months

13
52
0 / 0

[Hibernate-JIRA] Created: (HHH-3795) Unexpected behaviour of saveOrUpdate() for associations with delete-orphan

by Fabian Dankof (JIRA)

Unexpected behaviour of saveOrUpdate() for associations with delete-orphan -------------------------------------------------------------------------- Key: HHH-3795 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3795 Project: Hibernate Core Issue Type: Improvement Environment: Hibernate 3.2.6.GA, PostgreSQL 8.3 Reporter: Fabian Dankof Hello there, I think saveOrUpdate() behaves somewhat unexpected for associations with delete-orphan cascading style: Prerequisite: Association is set to cascade="all,delete-orphan" and nullable=true 1) Within a single session (i.e. a transient object): * Load parent * Delete child * saveOrUpdate() Result: Child is deleted from DB, a DELETE statement was issued 2) Across multiple session (i.e. a detached object): * Have parent with valid ID, but empty list/set of children * saveOrUpdate() Result: Child is not deleted from DB, an UPDATE statement is issued which sets FK of child to 'null' 3) like 2) but nullable is FALSE Result: Nothing happens. With merge() everything works as expected for detached and transient instances. I would either expect saveOrUpdate() to completely disregard DELETE statements OR behave similar to merge(). At least the different results of case 1) and 2) are pretty confusing. Best regards, Fabian -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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, 6 months

4
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3562) Support @OrderBy and @Sort annotations

by Adam Warski (JIRA)

Support @OrderBy and @Sort annotations -------------------------------------- Key: HHH-3562 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3562 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Adam Warski -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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, 6 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3628) Hilo optimizer problem in case of multiple threads accessing the sequence table

by Montagnon Cyril (JIRA)

Hilo optimizer problem in case of multiple threads accessing the sequence table ------------------------------------------------------------------------------- Key: HHH-3628 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3628 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.2.6 Environment: Sybase Reporter: Montagnon Cyril If 2 (or more) threads access the table storing the ids, this optimizer won't work and will try to insert entities with twice the same idea. The problem is the way the HiLoOptimizer class generates the id : public synchronized Serializable generate(AccessCallback callback) { if ( lastSourceValue < 0 ) { lastSourceValue = callback.getNextValue(); while ( lastSourceValue <= 0 ) { lastSourceValue = callback.getNextValue(); } hiValue = ( lastSourceValue * incrementSize ) + 1; value = hiValue - incrementSize; } else if ( value >= hiValue ) { lastSourceValue = callback.getNextValue(); hiValue = ( lastSourceValue * incrementSize ) + 1; } return make( value++ ); } In the 'else if' part, the 'value' variable isn't reaffected, which means the current thread will try to insert entities with an id that has already been used by another thread. The value should be reset with hiValue - incrementSize. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact 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, 6 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2223) BatchFetchQueue.getXXXBatch() cache check impeding batch fetching

by Joel Caplin (JIRA)

BatchFetchQueue.getXXXBatch() cache check impeding batch fetching ----------------------------------------------------------------- Key: HHH-2223 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2223 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga Environment: 3.2.0GA, Mac OS X/Solaris 10, Sybase 12.5/HSQLDB Reporter: Joel Caplin Priority: Minor Attachments: testcase.tar I have attached a test case which demonstrates the issue at hand by implementing a cheap data model: Pub >---|- Manager -|--< Employee Pub and Employee are uncached; Manager is cached (tried under both Eh and the non-prod HashMap implementation). All associations are lazy. The test case has a default batch size of 10 and uses hsqldb to demonstrate the problem - which was diagnosed against Sybase. When BatchFetchQueue.getXXXBatch() is invoked, it does not load any objects it finds in the second level cache - it merely acknowledges their presence by logging to INFO (isCached()). This in turn means that any child associations in that cached object will not have a proxy created for them. Suppose we want to find all the employees of the pubs in our database. We choose to do this by loading all the Pubs ("FROM Pub") and calling thePub.getManager().getEmployees() iteratively. When the managers are in the second level cache, Hibernate issues 11 select statements: one to load the pubs and one for each distinct manager. When the Managers are not in the cache, Hibernate issues 3 select statements: one to load the pubs, one to load the managers and one to load the employees. A solution might be to load the object from the cache instead of just ignoring 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

11 years, 6 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2009