August 2012 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] (HHH-7516) session.get is returning object which does not exist

by Suneel Nallagonda (JIRA)

12 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] (HHH-7562) Error locating Hibernate Session Factory in Terracotta configuration with EHCache

by David Harrigan (JIRA)

12 years, 3 months

4
7
0 / 0

[Hibernate-JIRA] Created: (HHH-6433) PostCommitListeners are called during rollback

by Shawn Clowater (JIRA)

PostCommitListeners are called during rollback ---------------------------------------------- Key: HHH-6433 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6433 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.6.2 Environment: JDK 1.6u25, Win7, Oracle10 Reporter: Shawn Clowater EntityActions that are registered as part of transaction completion are still called when the transaction didn't succeed. As an example, the DeleteEntityAction {code} public void doAfterTransactionCompletion(boolean success, SessionImplementor session) throws HibernateException { if ( getPersister().hasCache() ) { final CacheKey ck = new CacheKey( getId(), getPersister().getIdentifierType(), getPersister().getRootEntityName(), getSession().getEntityMode(), getSession().getFactory() ); getPersister().getCacheAccessStrategy().unlockItem( ck, lock ); } postCommitDelete(); } {code} The success is false in the event of a rollback so it doesn't update the cache but it still calls the postCommitDelete which triggers the postCommitDelete listeners. I would think this should only occur in the event that the transaction was actually committed. To add insult to injury the ActionQueue will also add failed actions to the after transaction completion queue and invalidate the query spaces. {code} public void execute(Executable executable) { try { executable.execute(); } finally { registerCleanupActions( executable ); } } private void registerCleanupActions(Executable executable) { beforeTransactionProcesses.register( executable.getBeforeTransactionCompletionProcess() ); if ( session.getFactory().getSettings().isQueryCacheEnabled() ) { final String[] spaces = (String[]) executable.getPropertySpaces(); afterTransactionProcesses.addSpacesToInvalidate( spaces ); session.getFactory().getUpdateTimestampsCache().preinvalidate( spaces ); } afterTransactionProcesses.register( executable.getAfterTransactionCompletionProcess() ); } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HBX-935) H2MetaDataDialect for identity detection

by Max Rydahl Andersen (JIRA)

H2MetaDataDialect for identity detection ---------------------------------------- Key: HBX-935 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-935 Project: Hibernate Tools Issue Type: Sub-task Components: reverse-engineer Affects Versions: 3.2beta9 Reporter: Max Rydahl Andersen Fix For: 3.2beta10 -- 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

12 years, 3 months

4
15
0 / 0

[Hibernate-JIRA] Created: (HHH-6682) add support for oracle "bitand" function to Oracle Dialect

by Amir Pashazadeh (JIRA)

add support for oracle "bitand" function to Oracle Dialect ---------------------------------------------------------- Key: HHH-6682 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6682 Project: Hibernate Core Issue Type: Improvement Components: query-hql Affects Versions: 3.6.7 Reporter: Amir Pashazadeh Priority: Minor Oracle has a function "bitand" which "and"s each bit of two numbers and returns its result. Oracle 10g supports this function, I'm not sure about older versions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-6664) contribute JavaDoc for EnumType

by Cédrik LIME (JIRA)

contribute JavaDoc for EnumType ------------------------------- Key: HHH-6664 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6664 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.6.7 Reporter: Cédrik LIME Attachments: EnumType.patch The {{org.hibernate.type.EnumType}} has no user documentation. This patch adds some well-needed JavaDoc. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6557) Add varargs to Restrictions.and(...) and Restrictions.or(...)

by Lorber Sebastien (JIRA)

Add varargs to Restrictions.and(...) and Restrictions.or(...) ------------------------------------------------------------- Key: HHH-6557 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6557 Project: Hibernate Core Issue Type: Improvement Components: query-criteria Affects Versions: 4.0.0.Beta5 Environment: any Reporter: Lorber Sebastien Priority: Trivial Add varargs to Restrictions.and(c1,c2) and Restrictions.or(c1,c2) This becomes more userfriendly to create a large list of AND / OR restrictions, without the pain or instantiating and filling a (con/dis)junction Note that the old methods returning LogicalExpression (and not Criterion) should be kept for retrocompatibility. As Java uses varargs in last resort in the case of an overload, callind and(c1,c2) will still call the old methods so it doesn't break the compatibility for people that uses the return type as a LogicalExpression and not a Criterion Pull request on github: https://github.com/slorber/hibernate-core/commit/7a6e3adb783c8e3f9fd00b67... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-6429) GROUP BY clause doesn't work with composite objects

by Fernando Santos (JIRA)

GROUP BY clause doesn't work with composite objects --------------------------------------------------- Key: HHH-6429 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6429 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.6.5 Environment: Firebird 2.1 Server, Hibernate 3.6.5, java 6, eclipse IDE Reporter: Fernando Santos Priority: Critical I'm trying to run the HQL below in the latest hibernate version {quote} SELECT m.account, (SELECT sum(amount) from Movement where date > '20-02-2011') as primo FROM Movement m GROUP BY m.account {quote} The problem is when the HQL is parsed, the account fields are added to my SELECT query but not to my GROUP BY query like below. Has someone been faced the same problem? Generated SQL: {quote} select movement0_.MOV_ACCOUNT_NUMBER as col_0_0_, movement0_.MOV_ACCOUNT_AFDELING_ID as col_0_1_, (select sum(movement2_.MOV_AMOUNT) from MOVEMENT movement2_) as col_1_0_, account1_.KONTONR as KONTONR12_, account1_.AFDELING_ID as AFDELING14_12_, account1_.KON_FUNCTION as KON2_12_, account1_.KON_BALANCE as KON3_12_, account1_.KON_BLOCKED as KON4_12_, account1_.KONTO_NAVN as KONTO5_12_, account1_.KON_KEY_FIGURE_CODE as KON6_12_, account1_.KON_MONITORED as KON7_12_, account1_.KON_SUGGEST_CONTRA_ACC as KON8_12_, account1_.KON_TOTALFROM as KON9_12_, account1_.KON_TYPE as KON10_12_, account1_.UAFD_GRP_NAVN as UAFD11_12_, account1_.UAFD_NAVN as UAFD12_12_, account1_.KON_TAX as KON15_12_, account1_.OPTLOCK as OPTLOCK12_ from MOVEMENT movement0_ inner join KONTOPLAN account1_ on movement0_.MOV_ACCOUNT_NUMBER=account1_.KONTONR and movement0_.MOV_ACCOUNT_AFDELING_ID=account1_.AFDELING_ID group by movement0_.MOV_ACCOUNT_NUMBER, movement0_.MOV_ACCOUNT_AFDELING_ID {quote} Error {quote} Caused by: org.firebirdsql.jdbc.FBSQLException: GDS Exception. 335544569. Dynamic SQL Error SQL error code = -104 Invalid expression in the select list (not contained in either an aggregate function or the GROUP BY clause) {quote} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6452) PostgreSQL Dialect does not fully implement NOWAIT locking

by Hannes Erven (JIRA)

PostgreSQL Dialect does not fully implement NOWAIT locking ---------------------------------------------------------- Key: HHH-6452 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6452 Project: Hibernate Core Issue Type: Improvement Components: core Affects Versions: 3.6.6, 4.x Reporter: Hannes Erven Priority: Trivial The PostgreSQL dialect should override the following methods from Dialect to fully support NOWAIT locks: @Override public String getForUpdateNowaitString() { return getForUpdateString()+" NOWAIT "; } @Override public String getForUpdateNowaitString(String aliases) { return getForUpdateString(aliases)+" NOWAIT "; } The syntax is documented at http://www.postgresql.org/docs/8.2/static/sql-select.html A possible workaround is to implement a custom PostgreSQL dialect, like discussed in https://forum.hibernate.org/viewtopic.php?p=2426758 . -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-7302) HQL uses multiple column Types in a inconsitent manner between Where and Order By clauses

by Miek Dunn (JIRA)

HQL uses multiple column Types in a inconsitent manner between Where and Order By clauses ----------------------------------------------------------------------------------------- Key: HHH-7302 URL: https://hibernate.onjira.com/browse/HHH-7302 Project: Hibernate ORM Issue Type: Bug Components: query-hql Affects Versions: 4.1.0 Environment: Java 1.7.0 Eclipse 3.7.2 Reporter: Miek Dunn When a type maps to multiple columns and that type is used in HQL the generated SQL will order the values in different manner in the Order By clause then it does in the Where clause. The Order By clause assumes the fields are mapped in order of importance, while the where clause assumes not field is more important then any other. For example assume a database stores a timestamp you using multiple fields (T2SCEN T2SYER T2SMTH T2SDAY T2STIM : century year month day time) and that there is a type that turns those fields into a Calendar. Now that type is used in an entity class named WorkOrder with a field named scheduled. The following HQL query: {quote} Select wo From WorkOrder wo WHERE wo.scheduled > :scheduled Order By wo.scheduled {quote} Will generate the following SQL {quote} select ... from SVDSPT workorder0_ where workorder0_.T2SCEN>? and workorder0_.T2SYER>? and workorder0_.T2SMTH>? and workorder0_.T2SDAY>? and workorder0_.T2STIM>? order by workorder0_.T2SCEN, workorder0_.T2SYER, workorder0_.T2SMTH, workorder0_.T2SDAY, workorder0_.T2STIM {quote} The Order By clause will order the values as one would expect for date, that is 2012-05-03T12:12:12 comes after 0001-12-01T00:00:00. The Where clause on the other hand implies that 2012-05-03T12:12:12 does not come after 0001-12-01T00:00:00, since the month 5>12 will be false. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

3
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2012