May 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5963) TS:Oracle, PostgreSQL: Transaction#commit() throws TransientObjectException, expected JDBCexception - MultiPathCircleCascadeCheckNullibilityFalseTest

by Ondrej Zizka (JIRA)

TS:Oracle, PostgreSQL: Transaction#commit() throws TransientObjectException, expected JDBCexception - MultiPathCircleCascadeCheckNullibilityFalseTest ----------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-5963 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5963 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.2 Environment: Oracle 10g PostgreSQL 8.2, 8.3 Reporter: Ondrej Zizka Assignee: Strong Liu In MultiPathCircleCascadeCheckNullibilityFalseTest#testMergeEntityWithNonNullableTransientEntity(), TransientObjectException is thrown on commit, whilst JDBCException is expected. For other DBs, it behaves as expectd. -- 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, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5785) HQL UPDATE omits alias when referencing an entity

by Ondrej Medek (JIRA)

HQL UPDATE omits alias when referencing an entity ------------------------------------------------- Key: HHH-5785 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5785 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Environment: Hibernate 3.3.1 in JBoss AS 5.1.0, org.hibernate.dialect.HSQLDialect Reporter: Ondrej Medek HQL UPDATE: UPDATE Lesson e SET e.state = 'N' WHERE EXISTS (SELECT 1 FROM LessonOrder lso WHERE lso.lesson = e) produces wrong SQL: update LESSON set lsn_state='N' where exists (select 1 from LESSON_ORDER lessonorde1_ where lessonorde1_.lsn_id=lsn_id) since in the database exists columns if the same name: LESSON.lsn_id and LESSON_ORDER.lsn_id. The problem is, that Hibernate omits the alias "e" in the SQL. When I make a little different query: UPDATE Lesson e SET e.state = 'N' WHERE EXISTS (SELECT 1 FROM LessonOrder lso WHERE lso.lesson.id = e.id) then the resulting SQL is right: update LESSON set lsn_state='N' where exists (select 1 from LESSON_ORDER lessonorde1_ where lessonorde1_.lsn_id=LESSON.lsn_id) However, I think the Hibernate should not omit the alias "e" in either case. -- 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, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-5146) org.hibernate.util.IdentitySet.iterator() return Map.Entry instances instead of actual elements

by Nicklas Nordborg (JIRA)

org.hibernate.util.IdentitySet.iterator() return Map.Entry instances instead of actual elements ----------------------------------------------------------------------------------------------- Key: HHH-5146 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5146 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Nicklas Nordborg Priority: Trivial Attachments: patch.txt By accident I used the IdentitySet implementation in my code and got ClassCastException:s when iterating over it. It turns out that the iterator() method returns Map.entrySet().iterator() instead of Map.keySet().iterator(). There is also a similar problem with the toArray() methods. I provide a patch. -- 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, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-680) Clarify the documentation around date bridges and that they are using DateTools

by Hardy Ferentschik (JIRA)

Clarify the documentation around date bridges and that they are using DateTools ------------------------------------------------------------------------------- Key: HSEARCH-680 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-680 Project: Hibernate Search Issue Type: Task Components: documentation Affects Versions: 3.3.0.Final Reporter: Hardy Ferentschik Fix For: 3.4.0 See also https://forum.hibernate.org/viewtopic.php?f=9&t=1009427 Maybe also time to implement some of the todos in {{DateBridge}} * allow pattern like yyyyMMdd? * allow base timezone? -- 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, 2 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-732) Add hibernate-entitymanager and javassist as optional dependencies in the distribution

by Emmanuel Bernard (JIRA)

Add hibernate-entitymanager and javassist as optional dependencies in the distribution -------------------------------------------------------------------------------------- Key: HSEARCH-732 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-732 Project: Hibernate Search Issue Type: Task Reporter: Emmanuel Bernard Fix For: 3.5 I tried quickly to hack dist.xml but Maven was yelling like a puppy MODULE BINARIES MAY NOT BE AVAILABLE FOR THIS ASSEMBLY! To refactor, move this assembly into a child project and use the flag <useAllReactorProjects>true</useAllReactorProjects> in each moduleSet. [INFO] Processing sources for module project: org.hibernate:hibernate-search:jar:3.4.0-SNAPSHOT [WARNING] NOTE: Currently, inclusion of module dependencies may produce unpredictable results if a version conflict occurs. [WARNING] The following patterns were never triggered in this artifact inclusion filter: o 'org.hibernate:hibernate-entitymanager' [WARNING] [DEPRECATION] moduleSet/binaries section detected in root-project assembly. MODULE BINARIES MAY NOT BE AVAILABLE FOR THIS ASSEMBLY! -- 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, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3404) Regular expressions (regex) boolean operator in HQL's where clause: rlike in mysql, regexp_match in informix, ... (regression from hibernate2)

by Geoffrey De Smet (JIRA)

Regular expressions (regex) boolean operator in HQL's where clause: rlike in mysql, regexp_match in informix, ... (regression from hibernate2) ---------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-3404 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3404 Project: Hibernate3 Issue Type: New Feature Components: query-hql Affects Versions: 3.2.6 Reporter: Geoffrey De Smet Hibernate 2 supported the rlike boolean operator (at least for mysql): HB-1034. Hibernate3 currently doesn't. It turns out that most mainstream databases support regular expression patterns (independently from normal like patterns). Mysql: rlike where a.serial rlike '\d*' Informix: regexp_match() where regexp_match(a.serial, '\d*') Oracle: REGEXP_LIKE where REGEXP_LIKE(a.serial, '\d*') There have been several forum posts asking about this feature for hibernate3 btw: http://forum.hibernate.org/viewtopic.php?p=2391395 http://forum.hibernate.org/viewtopic.php?p=2375634 etc -- 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, 2 months

6
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3887) Envers hbm xml based configuration

by Helmut Pasch (JIRA)

Envers hbm xml based configuration ---------------------------------- Key: HHH-3887 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3887 Project: Hibernate Core Issue Type: Improvement Components: envers Affects Versions: 3.5 Environment: Hibernate: All Hibernate Versions including Envers as subproject Our Project: Hibernate 3.3.1, Spring 2.5.6, Spring DM 1.2.0, Swing, GWT, .... Reporter: Helmut Pasch Currently the tool library Envers can only be configured / mapped to java POJOs by annotations. We would appreciate if this mapping could be done by hbm xml files. Using this approach the POJO won't be bound to Envers annotations. They simply would be left as POJOs instead of transformed to JPA like Entity Beans. We use POJOs to directly serialize them to a client tier, e.g. a Swing or GWT client tier. If our POJOs have to rely on Envers annotations similar like JPA annotations we see only two options objects may leave the server tier. First by a copy to an annotation less value object, which is consuming performance and resources. Second by coping / using Envers / Hibernate libraries for reference purposes on the client tier. Both solutions are not very attractive compared to the very well working hbm xml approach Hibernate core ORM functionality provides us. It is our intention to reduce / eliminate in client server communication model transformations like coping objects or transforming them to other formats like XML, e.g. like web services does. The easiest way would be to just serialize the Java POJO objects. But never then less the client should only depend (logically) on the server API. It is not intended to rely on a specific server implementation. -- 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, 2 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5525) Convert Getting Started Guide to use DocBook 5

by Steve Ebersole (JIRA)

Convert Getting Started Guide to use DocBook 5 ---------------------------------------------- Key: HHH-5525 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5525 Project: Hibernate Core Issue Type: Task Components: documentation Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6.0.CR1 This may require work on jDocBook to support, not sure. For sure we will need a docbook 5 bundle for maven respoitory -- 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, 2 months

2
13
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-765) close ScopedAnalyzers used at indexing time

by Sanne Grinovero (JIRA)

close ScopedAnalyzers used at indexing time ------------------------------------------- Key: HSEARCH-765 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-765 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.4.0.Alpha1 Reporter: Sanne Grinovero Assignee: Sanne Grinovero org.hibernate.search.backend.impl.lucene.works.AddWorkDelegate is creating a new Analyzer clone but never closes 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

13 years, 2 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-571) MassIndexer eats lock Exception

by Marc Schipperheyn (JIRA)

MassIndexer eats lock Exception ------------------------------- Key: HSEARCH-571 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-571 Project: Hibernate Search Issue Type: Improvement Components: engine Affects Versions: 3.2.1 Reporter: Marc Schipperheyn MassIndexer eats Lock exceptions and reports in stead: org.hibernate.search.SearchException: Unable to open IndexWriter -- 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, 2 months

3
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2011