April 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3253) Bi-directional relationships with multiple endpoints shouldn't be allowed

by Paul Benedict (JIRA)

Bi-directional relationships with multiple endpoints shouldn't be allowed ------------------------------------------------------------------------- Key: HHH-3253 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3253 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Reporter: Paul Benedict I unwittingly had a configuration, in which I mapped a bi-directional association with two inversed ends. class StockingShelf { @OneToOne(mappedBy="shelf") private Item special; @OneToMany(mappedBy="shelf") private List<Item> items; } class Item { @ManyToOne(optional=false) private Shelf shelf; } No errors or warnings were thrown or logged, but I am pretty sure this configuration should be invalid. All Hibernate books and articles imply that a bi-directional relationship contains one and only one endpoint for each side of the relationship. -- 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

16 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1745) Returning resultset from PostgreSQL stored procedure

by Diego Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1745?page=c... ] Diego Plentz updated HHH-1745: ------------------------------ Fix Version/s: (was: 3.3.0) 3.3.0.CR1 > Returning resultset from PostgreSQL stored procedure > ---------------------------------------------------- > > Key: HHH-1745 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1745 > Project: Hibernate3 > Issue Type: Patch > Components: core > Affects Versions: 3.2.0 cr1 > Environment: 3.2 cr1 (2006.03.27), PostgreSQL 8.1 > Reporter: Ravi Hegde > Assignee: Diego Plentz > Fix For: 3.3.0.CR1 > > Attachments: patch.txt > > > Returning resultset from PostgreSQL stored procedure throws an exception because of incomplete PostgreSQL dialect implementation. Problem has been fixed and tested. I have attached the patch file with this issue. Would appreciate if the patch is included at the earliest. -- 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

16 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Resolved: (HHH-1745) Returning resultset from PostgreSQL stored procedure

by Diego Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1745?page=c... ] Diego Plentz resolved HHH-1745. ------------------------------- Assignee: Diego Plentz Resolution: Fixed Fix Version/s: 3.3.0 > Returning resultset from PostgreSQL stored procedure > ---------------------------------------------------- > > Key: HHH-1745 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1745 > Project: Hibernate3 > Issue Type: Patch > Components: core > Affects Versions: 3.2.0 cr1 > Environment: 3.2 cr1 (2006.03.27), PostgreSQL 8.1 > Reporter: Ravi Hegde > Assignee: Diego Plentz > Fix For: 3.3.0 > > Attachments: patch.txt > > > Returning resultset from PostgreSQL stored procedure throws an exception because of incomplete PostgreSQL dialect implementation. Problem has been fixed and tested. I have attached the patch file with this issue. Would appreciate if the patch is included at the earliest. -- 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

16 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3237) PreInsertEventListener.onPreInsert() return value is not documented

by Jim Cushing (JIRA)

PreInsertEventListener.onPreInsert() return value is not documented ------------------------------------------------------------------- Key: HHH-3237 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3237 Project: Hibernate3 Issue Type: Bug Components: documentation Affects Versions: 3.3.0.CR1 Reporter: Jim Cushing http://opensource.atlassian.com/projects/hibernate/browse/HHH-1942 This issue is marked fixed, but onPreInsert() return value remains undocumented. -- 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

16 years, 1 month

2
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1043) Added HAVING Support to Criteria

by Marco Brade (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1043?page=c... ] Marco Brade commented on HHH-1043: ---------------------------------- I got the same failure. After using Projections.sqlGroupProjection(sql, groupBy, columnAliases, types) i got a lot of different failures. Subqueries still don't work so I had to use joins build by criterias. Now I got the problem that with an scrollable result (for paging) I have duplicated entities in the result. The solution for me was after combining all criterias to add another Restriction. ... Criteria crit = buildComplexCriteria(...); crit.add( Restrictions(" 1=1 group by {alias}.GroupById")); Now I have the Entities I'm looking for as single entities. Regards Marco > Added HAVING Support to Criteria > -------------------------------- > > Key: HHH-1043 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1043 > Project: Hibernate3 > Issue Type: Patch > Components: query-criteria > Affects Versions: 3.1 rc 1 > Environment: 3.1 rc 1 > Reporter: Tony Voss > Priority: Minor > Attachments: criteria-having-improvement.patch, criteria-having-improvement.zip > > > I've added support for HAVING clauses to Criteria. Attached are my code changes. -- 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

16 years, 1 month

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-980) FetchMode.SELECT javadoc wrong

by Gabriel Falkenberg (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-980?page=co... ] Gabriel Falkenberg commented on HHH-980: ---------------------------------------- The two Jiira issues about FetchMode.SELECT (this one and HHH1211) seems to imply that maybe the documentation needs to be updated after all. The javadoc at http://www.hibernate.org/hib_docs/core/api/org/hibernate/FetchMode.html says: SELECT Fetch eagerly, using a separate select. Equivalent to fetch="select". LAZY Deprecated. use FetchMode.SELECT Fetch lazily. Equivalent to outer-join="false". So FetchMode.SELECT is eager but it should also be used instead of FetchMode.LAZY which is Lazy, what gives? Am I interpreting the words in the wrong way? Reading the above statement about FetchMode.SELECT makes me think that the following code should load a Foo-object with one select and the associated "bars" in another select: Foo getFooWithBarsBySomeProp(String propValue) { Criteria criteria = getSession().createCriteria(Foo.class); criteria.add(Restrictions.eq("someProp", propValue)); criteria.setFetchMode("bars", FetchMode.SELECT); return (Foo) criteria.uniqueResult(); } But when I run this and logs the SQL I can see that only one select is performed. It would be very helpful it this could be elaborated on in the documentation. > FetchMode.SELECT javadoc wrong > ------------------------------ > > Key: HHH-980 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-980 > Project: Hibernate3 > Issue Type: Bug > Components: documentation > Affects Versions: 3.1 beta 2 > Reporter: Dave Brondsema > Priority: Minor > > FetchMode.SELECT says "Fetch eagerly, using a separate select." but it should say "Fetch lazily, using a separate select." > This is quite misleading -- 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

16 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1523) LazyInitializationError on enabling query cache...

by DK (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1523?page=c... ] DK commented on HHH-1523: ------------------------- We are encountering this issue since upgrading to hibernate 3.2.6. Please help do a proper patch, the workaround is so ugly. Is anyone addressing this? Thanks, D > LazyInitializationError on enabling query cache... > -------------------------------------------------- > > Key: HHH-1523 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1523 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.0.5, 3.1 > Environment: 3.0.1 and 3.1, HSQLDB and Oracle > Reporter: Vikas Sasidharan > Attachments: cache_issue.log, QueryCacheIssue.zip > > > I have two domain objects - Employee and Department - and there is a 1:N relationship from Department to Employee. When I join fetch an Employee with its Department, without query cache enabled, it works fine. If I enable query cache for this same query, it bombs with a LazyInitializationException. > Notes: > 1) We get this error only if query cache is enabled. > 2) We observed the same behaviour on both oscache and ehcache > 3) Calling Hibernate.initialize() explicitly after firing the HQL seems to work. The initialization does not fire an extra query though (it seems to pick it from the cache). > 4) Setting "lazy=false" on the "many-to-one" mapping also works. However, it wouldn't be acceptable. > Hibernate version: 3.0.5 > Mapping documents: > Employee.hbm.xml > <hibernate-mapping> > <class name="tavant.platform.test.domain.Employee" > table="CACHE_ISSUE_EMP" lazy="true" dynamic-update="true" dynamic-insert="true"> > <cache usage="read-write" /> > <id name="id" column="EMP_ID" type="java.lang.Long" > access="field" unsaved-value="null"> > <generator class="increment" /> > </id> > > <property name="name" type="string" update="true" > insert="true" column="EMP_NAME"/> > <many-to-one name="department" class="tavant.platform.test.domain.Department" > cascade="none" outer-join="auto" update="true" insert="true" column="DEPARTMENT_ID"/> > </class> > </hibernate-mapping> > > Department.hbm.xml > <hibernate-mapping> > <class name="tavant.platform.test.domain.Department" table="CACHE_ISSUE_DEP" > lazy="true" dynamic-update="true" dynamic-insert="true"> > > <cache usage="read-write" /> > <id name="id" column="DEPARTMENT_ID" > type="java.lang.Long" access="field"> > <generator class="increment"/> > </id> > <property name="name" type="java.lang.String" > update="false" insert="true" column="NAME"/> > <bag name="employees" lazy="true" > inverse="true" cascade="save-update" access="field"> > <cache usage="read-write"/> > <key column="DEPARTMENT_ID"/> > <one-to-many class="tavant.platform.test.domain.Employee"/> > </bag> > </class> > </hibernate-mapping> > > Code between sessionFactory.openSession() and session.close(): > public Employee getEmployeeWithDepartment(String empName) { > Session session = null; > try { > session = sessionFactory.openSession(); > Employee emp = (Employee) session.createQuery( > "from Employee e join fetch e.department where e.name = :name") > .setString("name", empName) > .setCacheable(true) > .uniqueResult(); > // If I uncomment the next line, this works (even without > // firing an extra query)! > // Hibernate.initialize(emp.getDepartment()); > return emp; > } finally { > if (session != null) { > session.close(); > } > } > } > > // First load employee and populate cahces > Employee emp = test.getEmployeeWithDepartment(EMPLOYEE_NAME); > System.out.println("Employee : " + emp + ", Employee.Department : " > + emp.getDepartment()); > > // Now try to make use of the cache > emp = test.getEmployeeWithDepartment(EMPLOYEE_NAME); > System.out.println("Employee : " + emp + ", Employee.Department : " > + emp.getDepartment()); > > Full stack trace of any exception that occurs: > org.hibernate.LazyInitializationException: could not initialize proxy - the owning Session was closed > at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:53) > at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:84) > at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:134) > at tavant.platform.test.domain.Department$$EnhancerByCGLIB$$67b26899.toString(<generated>) > at java.lang.String.valueOf(String.java:2131) > at java.lang.StringBuffer.append(StringBuffer.java:370) > at tavant.platform.test.client.TestPrefetchRelationWithQueryCacheEnabled.main(TestPrefetchRelationWithQueryCacheEnabled.java:116) > > Name and version of the database you are using: > We have noticed this on Oracle and HSQL > The generated SQL (show_sql=true): > #First read, goes fine > Hibernate: select employee0_.EMP_ID as EMP1_0_, department1_.DEPARTMENT_ID as DEPARTMENT1_1_, employee0_.EMP_NAME as EMP2_1_0_, employee0_.DEPARTMENT_ID as DEPARTMENT3_1_0_, department1_.NAME as NAME0_1_ from CACHE_ISSUE_EMP employee0_ inner join CACHE_ISSUE_DEP department1_ on employee0_.DEPARTMENT_ID=department1_.DEPARTMENT_ID where (employee0_.EMP_NAME=? ) > #Prints the Employee and Department fine > Employee : [Id : 1, name : testEmployee], Employee.Department : [Id : 1, name : testDepartment] > #Second read bombs! > org.hibernate.LazyInitializationException: could not initialize proxy - the owning Session was closed > at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:53) > at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:84) > at org.hibernate.proxy.CGLIBLazyInitializer.intercept(CGLIBLazyInitializer.java:134) > [..] > Please have a look at the post [http://forum.hibernate.org/viewtopic.php?t=955839] for more details and follow ups. > Kindly help. I am attaching an Eclipse Project containing the TestCase. The main file is TestPrefetchRelationWithQueryCacheEnabled. > Thanks, > Vikas -- 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

16 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-84) No ConstraintViolationException thrown with HSQL database

by Davide Angelocola (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-84?page=com... ] Davide Angelocola commented on HHH-84: -------------------------------------- Hi, I'm using hibernate 3.2.5 and hsqldb 1.8.0.7. ConstraintViolationException is not throwned for id of type java.lang.String. Hsqldb however report this the constraints violation as showed by this simple testcase: create table "PUBLIC".test ( id VARCHAR not null, primary key (id) ) INSERT INTO TEST VALUES('a') INSERT INTO TEST VALUES('a') Error code -104, SQL state 23000: Violation of unique constraint $$: duplicate value(s) for column(s) $$: SYS_PK_48 Hope it helps. > No ConstraintViolationException thrown with HSQL database > --------------------------------------------------------- > > Key: HHH-84 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-84 > Project: Hibernate3 > Issue Type: Bug > Components: core > Environment: Hibernate version:3.0-beta1 > Database:HSQL1.7.2 > Reporter: Marcel Schroer > Assignee: Emmanuel Bernard > Priority: Minor > Fix For: 3.0 beta 2 > > > When a unique constraint violation is thrown by the HSQL database > (java.sql.SQLException: Unique constraint violation: SYS_CT_171 in statement), the SQLException is wrapped in a GenericSQLException instead of the ConstraintViolationException that I expected. -- 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

16 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3251) EJB query UPDATE with java.sql.Timestamp

by Ralf Alt (JIRA)

EJB query UPDATE with java.sql.Timestamp ---------------------------------------- Key: HHH-3251 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3251 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.3.0.CR1 Environment: MS SQL 2005, java version "1.6.0_05", Sun Java System Application Server 9.1_01 (build b09d-fcs) Hibernate 3.3.2.GA Reporter: Ralf Alt Priority: Critical Entity bean with Timestamp field. @Version @Column(name="modtime",nullable=false,insertable=false,updatable=true) protected Timestamp getModificationtimeTS() { return myModTime; } protected void setModificationtimeTS(Timestamp timestamp) { myModTime = timestamp; } EJBQuery: "UPDATE ADRESS.class.getName() set name = :_name, modificationtimeTS = :_modtime where id = :_id" Query qry = entityMgr.createQuery( query ) .setParameter( "_name", "Newer" ) .setParameter( "_modtime", new Timestamp( System.currentTimeMillis() )) .setParameter( "_id", 1 ); The generated SQL declare @p1 int set @p1=NULL exec sp_prepexec @p1 output,N'@P0 nvarchar(4000),@P1 datetime',N'update ADRESS set name=@P0, modtime=@P1 where id=@P2',N'Newer',''2008-04-24 16:14:17:490'',1 select @p1 The error is in the time stampformat for the sql server (syntax error in the near of '2008'). -- 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

16 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-852) start hql/criteria editing based on selected project

by Max Rydahl Andersen (JIRA)

start hql/criteria editing based on selected project ---------------------------------------------------- Key: HBX-852 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-852 Project: Hibernate Tools Type: Improvement Components: eclipse Versions: 3.2beta9 Reporter: Max Rydahl Andersen now that projects know which console configuration they are associated too we can start hql/criteria editing directly on a consoleconfig when a resource in a project is selected. probably should have an action set (in toolbar or menu) together with adding it to a context sensitive right menu. -- 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

16 years, 2 months

2
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues April 2008