August 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Resolved: (HHH-1825) Improved mesage in Exception from Table.validateColumns

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1825?page=c... ] Diego Pires Plentz resolved HHH-1825. ------------------------------------- Assignee: Diego Pires Plentz Resolution: Cannot Reproduce Already done. if ( columnInfo == null ) { throw new HibernateException( "Missing column: " + col.getName() + " in " + Table.qualify( tableInfo.getCatalog(), tableInfo.getSchema(), tableInfo.getName())); } > Improved mesage in Exception from Table.validateColumns > ------------------------------------------------------- > > Key: HHH-1825 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1825 > Project: Hibernate3 > Issue Type: Improvement > Components: metamodel > Affects Versions: 3.1.2 > Reporter: Bjørn Bjerkeli > Assignee: Diego Pires Plentz > Priority: Minor > > The method validateColumns in Table throws an exception when it encounters a missing column. Each time I encounter this problem, I have to start the debugger and create a breakpoint to identify the which table that has the missing column. > So instead of: > if ( columnInfo == null ) { > throw new HibernateException( "Missing column: " + col.getName() ); > } > Add proper context to the Exception: > if ( columnInfo == null ) { > throw new HibernateException( "Table:"+this+has " missing column: " + col.getName() ); > } > This will make it trivial to identify and correct the bogus mapping or schema. -- 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

17 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2789) Section 19.2 of the documentation does not show OSCache as supporting clusters. It does.

by Diego Pires Plentz (JIRA)

Section 19.2 of the documentation does not show OSCache as supporting clusters. It does. ---------------------------------------------------------------------------------------- Key: HHH-2789 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2789 Project: Hibernate3 Issue Type: Improvement Components: documentation Reporter: Diego Pires Plentz Assignee: Diego Pires Plentz Priority: Minor Fix For: 3.3 Section 19.2 of the documentation does not show OScache as supporting clusters. It does. e.g. see the following email to the developers list: > from Andres March > to me, ltorunski, chris_overseas > > show details 7:41 pm (4 hours ago) > > OSCache only supports clustered invalidation not clustered replication. -- 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

17 years, 5 months

2
5
0 / 0

[Hibernate-JIRA] Resolved: (HHH-1920) Incorrect documentation regarding XML manipulation in Hibernate reference manual (chapter 18.3).

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1920?page=c... ] Diego Pires Plentz resolved HHH-1920. ------------------------------------- Resolution: Fixed Fix Version/s: 3.3 > Incorrect documentation regarding XML manipulation in Hibernate reference manual (chapter 18.3). > ------------------------------------------------------------------------------------------------ > > Key: HHH-1920 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1920 > Project: Hibernate3 > Issue Type: Bug > Components: documentation > Affects Versions: 3.1.3 > Reporter: Ignat Zapolsky > Assignee: Diego Pires Plentz > Priority: Trivial > Fix For: 3.3 > > > Manual has following sample (chapter 18.3): > Session session = factory.openSession(); > Session dom4jSession = session.getSession(EntityMode.DOM4J); > Transaction tx = session.beginTransaction(); > List results = dom4jSession > .createQuery("from Customer c left join fetch c.accounts where c.lastName like :lastName") > .list(); > for ( int i=0; i<results.size(); i++ ) { > //add the customer data to the XML document > Element customer = (Element) results.get(i); > doc.add(customer); > } > Mentioned code simply changes root node of doc, but supposed to add child elements. > Correct code shall look like: > Session session = factory.openSession(); > Session dom4jSession = session.getSession(EntityMode.DOM4J); > Transaction tx = session.beginTransaction(); > List results = dom4jSession > .createQuery("from Customer c left join fetch c.accounts where c.lastName like :lastName") > .list(); > for ( int i=0; i<results.size(); i++ ) { > //add the customer data to the XML document > Element customer = (Element) results.get(i); > doc.getRootEelemnt().add(customer); > } -- 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

17 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Reopened: (HHH-1920) Incorrect documentation regarding XML manipulation in Hibernate reference manual (chapter 18.3).

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1920?page=c... ] Diego Pires Plentz reopened HHH-1920: ------------------------------------- Sorry Ignat. I'm won't understand what you are trying to say, but after your last comment i figured out and found that I'm wrong. Sorry and thanks for this ;-) > Incorrect documentation regarding XML manipulation in Hibernate reference manual (chapter 18.3). > ------------------------------------------------------------------------------------------------ > > Key: HHH-1920 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1920 > Project: Hibernate3 > Issue Type: Bug > Components: documentation > Affects Versions: 3.1.3 > Reporter: Ignat Zapolsky > Assignee: Diego Pires Plentz > Priority: Trivial > > Manual has following sample (chapter 18.3): > Session session = factory.openSession(); > Session dom4jSession = session.getSession(EntityMode.DOM4J); > Transaction tx = session.beginTransaction(); > List results = dom4jSession > .createQuery("from Customer c left join fetch c.accounts where c.lastName like :lastName") > .list(); > for ( int i=0; i<results.size(); i++ ) { > //add the customer data to the XML document > Element customer = (Element) results.get(i); > doc.add(customer); > } > Mentioned code simply changes root node of doc, but supposed to add child elements. > Correct code shall look like: > Session session = factory.openSession(); > Session dom4jSession = session.getSession(EntityMode.DOM4J); > Transaction tx = session.beginTransaction(); > List results = dom4jSession > .createQuery("from Customer c left join fetch c.accounts where c.lastName like :lastName") > .list(); > for ( int i=0; i<results.size(); i++ ) { > //add the customer data to the XML document > Element customer = (Element) results.get(i); > doc.getRootEelemnt().add(customer); > } -- 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

17 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2788) Oracl8iDialect No Dialect mapping for JDBC type 91

by Paul Stanton (JIRA)

Oracl8iDialect No Dialect mapping for JDBC type 91 -------------------------------------------------- Key: HHH-2788 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2788 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5.ga, Oracle8i (8.1.7) Reporter: Paul Stanton Priority: Critical Upgrading from 3.1.3 deprecation messages told me to use Oracle8iDialect instead of OracleDialect, but when I use this i get the following exception: org.hibernate.MappingException: No Dialect mapping for JDBC type: 91 at org.hibernate.dialect.TypeNames.get(TypeNames.java:56) at org.hibernate.dialect.TypeNames.get(TypeNames.java:81) at org.hibernate.dialect.Dialect.getTypeName(Dialect.java:291) at org.hibernate.mapping.Column.getSqlType(Column.java:182) at org.hibernate.mapping.Table.sqlTemporaryTableCreateString(Table.java:347) at org.hibernate.mapping.PersistentClass.prepareTemporaryTables(PersistentClass.java:742) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:210) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1294) I'm not sure which hbm is causing this, so i don't want to post all of them, but i think 91 is type date. http://forum.hibernate.org/viewtopic.php?t=978237 -- 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

17 years, 5 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2572) NullPointerException when cascade-merge detached entity graph that contains null component property

by Nguyen Hau Giang (JIRA)

NullPointerException when cascade-merge detached entity graph that contains null component property --------------------------------------------------------------------------------------------------- Key: HHH-2572 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2572 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3 Environment: hibernate 3.2.3 only Reporter: Nguyen Hau Giang Priority: Critical Attachments: testCase.zip when merging detached entity graph whose leaf-entity contains null-component property, hibernate 3.2.3 will throw NPE. (leaf-entity level>2) No exception was thrown in hibenate 3.2.2 Mapping: Parent -> Child -> GrandChild All associations is cascade. GrandChild contains a component property. Test Case: parent=<load>; child=parent.get1Child(); GrandChild grandChild=new GrandChild(); grandChild.setComponent(null); child.add(grandChild); evict(parent);//session is closed ... merge(parent);//merge in new sesson -> THROW NullPointerException for further detail, see attache test 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

17 years, 5 months

3
6
0 / 0

[Hibernate-JIRA] Resolved: (HHH-1527) Ant clean target subtask deletes current working directory files (including build.xml)

by Diego Pires Plentz (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1527?page=c... ] Diego Pires Plentz resolved HHH-1527. ------------------------------------- Assignee: Diego Pires Plentz Resolution: Fixed Migration to Maven solve this. > Ant clean target subtask deletes current working directory files (including build.xml) > -------------------------------------------------------------------------------------- > > Key: HHH-1527 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1527 > Project: Hibernate3 > Issue Type: Bug > Components: build > Affects Versions: 3.1.2 > Environment: Hibernate Core 3.1.2, any platform > Reporter: Allen Gates > Assignee: Diego Pires Plentz > > The Ant build.xml clean target contains a subtask: > <delete dir="${dist.dir}"/> > where dist.dir is defined > <property name="dist.dir" value="../${name}-${version.sansPatchLevel}"/> > Unfortunately, that resolves to precisely the the current directory (i.e. named hibernate-3.1) > from which ant clean is run, thus deleting build.xml and other files. This is obviously undesirable. > I found this in conjunction with running a standalone Ant build of Hibernate, while working on > a patch for Configuration.java to restrict table retrieval to only hibernate.default_schema ;) -- 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

17 years, 5 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2675) Session.contains() always return false

by Mohammad Shoaib Ashrafi (JIRA)

Session.contains() always return false -------------------------------------- Key: HHH-2675 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2675 Project: Hibernate3 Issue Type: Bug Components: build Affects Versions: 3.1.3 Environment: JDK1.5, Tomcat6.0 Hibernate 3, Windows XP Reporter: Mohammad Shoaib Ashrafi i have two class (User and Role) with hibernate one-to-one mapping in runtime i load the user object after this i create the new user object with same primary key as loaded object and when i call session.update(newUser) then it throws NonUniqueObjectException so i added some statement before update if( session.contains(userObject) ){ session.evict(userObject) } session.update(userObject) but the problem is here that session.contains(userObject) always return false kindly resolved this issue and give the chance of thanks Regards Mohammad Shoaib Ashraif -- 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

17 years, 5 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2164) Minor bug in section "20.1.1. Customizing the schema"

by Andres Gonzalez (JIRA)

Minor bug in section "20.1.1. Customizing the schema" ----------------------------------------------------- Key: HHH-2164 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2164 Project: Hibernate3 Type: Bug Components: documentation Versions: 3.2.0.ga Reporter: Andres Gonzalez Where it says: ******************************************************************************************************************************* A unique-key attribute may be used to group columns in a single unique key constraint. Currently, the specified value of the unique-key attribute is not used to name the constraint in the generated DDL, only to group the columns in the mapping file. <many-to-one name="org" column="orgId" unique-key="OrgEmployeeId"/> <property name="employeeId" unique-key="OrgEmployee"/> ******************************************************************************************************************************* i think the unique-key attributes should jave both the same value ("OrgEmployee", for example) -- 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

17 years, 5 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2601) Missing documentation in section 5.1.12

by Chris Bredesen (JIRA)

Missing documentation in section 5.1.12 --------------------------------------- Key: HHH-2601 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2601 Project: Hibernate3 Issue Type: Bug Components: documentation Affects Versions: 3.2.3 Reporter: Chris Bredesen Priority: Minor Section "5.1.12. many-to-one" lists (15) after the formula="" part, but never gives documentation on what (15) is. The list below stops at (14). -- 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

17 years, 5 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 August 2007