January 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5820) Improved second level caching for immutable entities

by Nicolas Estrada (JIRA)

Improved second level caching for immutable entities ---------------------------------------------------- Key: HHH-5820 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5820 Project: Hibernate Core Issue Type: Improvement Components: core Environment: Hibernate 3.6.0.Final, EhCache 2.3.0, MySQL Reporter: Nicolas Estrada Priority: Minor A description of my problem and a fix is available here: https://forum.hibernate.org/viewtopic.php?f=1&t=1008946&p=2440121#p2440121 The problem is as follows: I am using simple POJOs, no dynamic updates, no formula properties, some using a single table and others spanning multiple tables. In my special case they are also IMMUTABLE. Now when an EntityInsertAction (in my case from doAfterTransactionCompletion()) wants to update the cache is invokes the method isCachePutEnabled(). For single table entities it works fine but when the entity spans multiple tables (ie. getTableSpan() > 1), isCacheInvalidationRequired() returns true, which I think stems from the fact that a concurrent cache may have simultaneous locks on different CacheKeys pointing to the same entity (not sure). Now the transaction was successfully completed, ie. an immutable entity was successfully persisted into the datastore. Why then can't it be inserted in the second level cache? The culprit is the table spanning check. I think that in a special case if the entity is immutable it should override the latter. A fix which seemed possible would be to version the entities. However, since they are immutable, I'm opting for using a read-only cache mode for the entities. And when I try to update the version I get an UnsupportedOperationException in the ReadOnlyEhcacheEntityRegionAccessStrategy from Ehcache when it tries to invoke lockItem() from the EntityUpdateAction in order to upgrade the version. Versions are not a solution in my case. Any thoughts on the matter would be appreciated. Thank you -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5818) Malformed exception message

by Archie Cobbs (JIRA)

Malformed exception message --------------------------- Key: HHH-5818 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5818 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0 Reporter: Archie Cobbs Priority: Trivial I happened to run across this exception: {noformat} org.hibernate.exception.SQLGrammarException: could not collection element by index org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:92) org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66) org.hibernate.loader.Loader.loadEntity(Loader.java:2084) org.hibernate.loader.entity.CollectionElementLoader.loadElement(CollectionElementLoader.java:94) org.hibernate.persister.collection.OneToManyPersister.getElementByIndex(OneToManyPersister.java:385) org.hibernate.collection.AbstractPersistentCollection.readElementByIndex(AbstractPersistentCollection.java:183) org.hibernate.collection.PersistentMap.get(PersistentMap.java:169) ... {noformat} The exception message "could not collection element by index" makes no sense and should be clarified. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5816) Expose list of modified properties in PostUpdateEvent

by Emmanuel Bernard (JIRA)

Expose list of modified properties in PostUpdateEvent ----------------------------------------------------- Key: HHH-5816 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5816 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.6.0 Reporter: Emmanuel Bernard Assignee: Emmanuel Bernard Fix For: 3.6.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

14 years, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5698) Sort inserts in primary key order (patch included)

by Søren Mathiasen (JIRA)

Sort inserts in primary key order (patch included) -------------------------------------------------- Key: HHH-5698 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5698 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.6.0 Environment: Hibernate 3.6.0, all databases Reporter: Søren Mathiasen Priority: Critical Attachments: hibernate-insert.patch When inserting rows in the database, we should make a sort on primary key in order to ensure that database fragmentation is minimal. Attached is a patch that does that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
4
0 / 0

[Hibernate-JIRA] Commented: (HHH-892) HQL parser does not resolve alias in ORDER BY clause

by Matheus Luis Ramos de Souza (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-892?page=co... ] Matheus Luis Ramos de Souza commented on HHH-892: ------------------------------------------------- \o/ Very nice! Thanks!! > HQL parser does not resolve alias in ORDER BY clause > ----------------------------------------------------- > > Key: HHH-892 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-892 > Project: Hibernate Core > Issue Type: Bug > Components: query-hql > Affects Versions: 3.5.4, 3.6.0.Beta1 > Environment: Hibernate 3.0.5, MySQL, Tomcat > Reporter: Guido Laures > Assignee: Gail Badner > Fix For: 3.6.0.CR2 > > Attachments: HHH-892.patch, HibernateHavingAliasTest.java > > > When using an alias for an ORDER BY clause this is not always correctly resolved. Example: > SELECT SUM(A.x) AS mySum FROM MyClass AS A GROUP BY A.y ORDER BY mySum > does not work because "mySum" is not resolved in the ORDER BY clause which results in an exception telling that mySum is an unknown column. > Workaround (not to say "hack") is using: > SELECT SUM(A.x) AS mySum FROM MyClass AS A GROUP BY A.y ORDER BY col_0_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

14 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5588) Improve support for entityNames - determine the entityName for a retrieved object vía envers

by Hernán Chanfreau (JIRA)

Improve support for entityNames - determine the entityName for a retrieved object vía envers -------------------------------------------------------------------------------------------- Key: HHH-5588 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5588 Project: Hibernate Core Issue Type: Improvement Components: envers Affects Versions: 3.6.0.CR1, 3.5.6 Reporter: Hernán Chanfreau Priority: Minor Basically, the idea is provide a mechanism to determine the entityName for an object previously retrieved by envers. The original discussion is here: http://community.jboss.org/thread/155727?tstart=0 I've already upload a proposal patch for this issue in envers forum. Regards. Hernán. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-659) @IndexedEmbedded entities with empty String prefix should be clearly flagged

by Kyrill Alyoshin (JIRA)

@IndexedEmbedded entities with empty String prefix should be clearly flagged ---------------------------------------------------------------------------- Key: HSEARCH-659 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-659 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.3.0.Final Reporter: Kyrill Alyoshin I've just spent some time figuring out an issue that was caused by the simple fact that one of my @IndexedEmbedded associations was mapped as @IndexedEmbedded(prefix = ""). The documentation clearly states that such things are not allowed. However, it sure would be nice if the framework gave some feedback to the developer by either causing the application to fail at start-up or simply by logging an error message in the logs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5813) org.hibernate.impl.AbstractQueryImpl.uniqueElement() should use equal()

by Joey Jiang (JIRA)

org.hibernate.impl.AbstractQueryImpl.uniqueElement() should use equal() ----------------------------------------------------------------------- Key: HHH-5813 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5813 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.0 Reporter: Joey Jiang I think there is a modify in method in uniqueElement of org.hibernate.impl.AbstractQueryImp.java Before modify: if ( list.get(i)!=first ) { After modify: if ( !list.get(i).equals(first)) { Due the data in list is: Long 999, Long 999 i use hibernate-distribution-3.6.0.Final for debug. Wish you have a good day. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1706) Named parameters ignored when single apostrophe encountered within an SQL comment

by Matthew Lieder (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1706?page=c... ] Matthew Lieder commented on HHH-1706: ------------------------------------- I can confirm this is a legitimate bug and still exists in 3.5.1. org.hibernate.engine.query.ParameterParser isn't aware of comments and thus treats anything inside comments as if it's actual SQL. > Named parameters ignored when single apostrophe encountered within an SQL comment > --------------------------------------------------------------------------------- > > Key: HHH-1706 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1706 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1.3, 3.2.0 cr1 > Environment: 3.1.2, DB2/400 > Reporter: Curtis Witherow > Attachments: bug.zip > > > Found that named parameters in an named SQL query are ignored when a single apostrophe is encountered in an SQL comment (either /* ... */ or -- ... form). > The obvious workaround is to remove single apostrophes from SQL comments. > I have included test code that runs two queries -- the first succeeds, the second fails. The only difference between the queries is that the second contains the apostrophe character within a comment. > Since I was testing against DB2/400, I was using SYSIBM.SYSDUMMY1 as my source table. This is analygous to using DUAL on an Oracle db. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5814) set entity id for auto-generated id annotation

by Dave (JIRA)

set entity id for auto-generated id annotation ---------------------------------------------- Key: HHH-5814 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5814 Project: Hibernate Core Issue Type: Bug Environment: ALL Reporter: Dave We need to copy data from one data source to another, and need keep same id to keep entity relations. 1. fetch entities from data source A 2. evict entities from session, set version to null, keep id not changed. 3. create entities in data source B. for @GeneratedValue(strategy = GenerationType.AUTO), entity id is reset by Hibernate. But for auto increment id in mysql, it can be set manually and AUTO_INCREMENT is automatically adjusted. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues January 2011