February 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HBX-866) schema-selection is not applying pattern matching on oracle database

by Nicolas Romantzoff (JIRA)

schema-selection is not applying pattern matching on oracle database -------------------------------------------------------------------- Key: HBX-866 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-866 Project: Hibernate Tools Type: Bug Components: reverse-engineer Versions: 3.2beta8, 3.2beta9 Environment: Hibernate 3.2.1, Oracle 10g (10.1.0.3.0) Reporter: Nicolas Romantzoff In the reverse-engineering file, when asking a pattern-matching schema and/or table in <schema-selection> (match-schema or match-table) it is ignored. Looks like table discovery is performing a raw '=' test. This behavior is seen with both OracleMetaDataDialect and JDBCMetaDataDialect Easy reproducible steps: - Create 1 single table "ABC" in an empty schema "TEST" Working schema-selections: <schema-selection/> => (select ... from all_tables;) <schema-selection match-schema="TEST"/> => (select ... from all_tables where owner='TEST';) <schema-selection match-table="ABC"/> => (select ... from all_tables where table_name='ABC';) <schema-selection match-schema="TEST" match-table="ABC"/> => (select ... from all_tables where owner='TEST' and table_name='ABC';) Not-Working schema-selections: <schema-selection match-schema=".*"/> => (select ... from all_tables where owner='.*'; !!!!!! ) <schema-selection match-table=".*"/> => (select ... from all_tables where table_name='.*'; !!!!!! ) <schema-selection match-schema="TEST" match-table=".*"/> => (select ... from all_tables where owner='TEST' and table_name='.*'; !!!!!! ) -- 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, 11 months

2
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-1786) JTASessionContext.CleanupSynch does not remove sessions from currentSessionMap

by David Churavy (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1786?page=c... ] David Churavy commented on HHH-1786: ------------------------------------ Maybe better alternative fix for this would be to change WebSphereExtendedJTATransactionLookup.TransactionAdapter to cache the transaction id the first time it obtains it from WS. Attached the modified class + corresponing SVN patch. > JTASessionContext.CleanupSynch does not remove sessions from currentSessionMap > ------------------------------------------------------------------------------ > > Key: HHH-1786 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1786 > Project: Hibernate3 > Type: Improvement > Versions: 3.1.2 > Environment: IBM WebSphere 6.0.2.7, Hibernate CVS snapshot from 2006-02-24 > Reporter: Tomi Szabo > Attachments: JTASessionContext.java, WebSphereExtendedJTATransactionLookup.java, WebSphereExtendedJTATransactionLookup.patch.txt > > > We are using JTASessionContext, CMTTransaction and WebSphereExtendedJTATransactionLookup. We have experienced some memmory leak problems and after closer inspection we have found that Hibernate sessions are not removed from currentSessionMap inside JTASessionContext. > Method JTASessionContext.CleanupSynch.afterCompletion() is called as expected but code "context.currentSessionMap.remove( txn );" does not remove session from Map because of key's hashcode has changed. This is due to fact that com.ibm.websphere.jtaextensions.ExtendedJTATransaction.hashCode is actually ID of underlaying transaction. But if it comes to the afterCompletion method in CleanupSynch the underlaying transaction is already closed. Closed transaction has ID 0 (default value) and it is different from ID under which the Hibernate session was previously inserted into Map. > Possible patch is in attachements. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1786) JTASessionContext.CleanupSynch does not remove sessions from currentSessionMap

by David Churavy (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1786?page=all ] David Churavy updated HHH-1786: ------------------------------- Attachment: WebSphereExtendedJTATransactionLookup.java > JTASessionContext.CleanupSynch does not remove sessions from currentSessionMap > ------------------------------------------------------------------------------ > > Key: HHH-1786 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1786 > Project: Hibernate3 > Type: Improvement > Versions: 3.1.2 > Environment: IBM WebSphere 6.0.2.7, Hibernate CVS snapshot from 2006-02-24 > Reporter: Tomi Szabo > Attachments: JTASessionContext.java, WebSphereExtendedJTATransactionLookup.java, WebSphereExtendedJTATransactionLookup.patch.txt > > > We are using JTASessionContext, CMTTransaction and WebSphereExtendedJTATransactionLookup. We have experienced some memmory leak problems and after closer inspection we have found that Hibernate sessions are not removed from currentSessionMap inside JTASessionContext. > Method JTASessionContext.CleanupSynch.afterCompletion() is called as expected but code "context.currentSessionMap.remove( txn );" does not remove session from Map because of key's hashcode has changed. This is due to fact that com.ibm.websphere.jtaextensions.ExtendedJTATransaction.hashCode is actually ID of underlaying transaction. But if it comes to the afterCompletion method in CleanupSynch the underlaying transaction is already closed. Closed transaction has ID 0 (default value) and it is different from ID under which the Hibernate session was previously inserted into Map. > Possible patch is in attachements. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1786) JTASessionContext.CleanupSynch does not remove sessions from currentSessionMap

by David Churavy (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1786?page=all ] David Churavy updated HHH-1786: ------------------------------- Attachment: WebSphereExtendedJTATransactionLookup.patch.txt > JTASessionContext.CleanupSynch does not remove sessions from currentSessionMap > ------------------------------------------------------------------------------ > > Key: HHH-1786 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1786 > Project: Hibernate3 > Type: Improvement > Versions: 3.1.2 > Environment: IBM WebSphere 6.0.2.7, Hibernate CVS snapshot from 2006-02-24 > Reporter: Tomi Szabo > Attachments: JTASessionContext.java, WebSphereExtendedJTATransactionLookup.java, WebSphereExtendedJTATransactionLookup.patch.txt > > > We are using JTASessionContext, CMTTransaction and WebSphereExtendedJTATransactionLookup. We have experienced some memmory leak problems and after closer inspection we have found that Hibernate sessions are not removed from currentSessionMap inside JTASessionContext. > Method JTASessionContext.CleanupSynch.afterCompletion() is called as expected but code "context.currentSessionMap.remove( txn );" does not remove session from Map because of key's hashcode has changed. This is due to fact that com.ibm.websphere.jtaextensions.ExtendedJTATransaction.hashCode is actually ID of underlaying transaction. But if it comes to the afterCompletion method in CleanupSynch the underlaying transaction is already closed. Closed transaction has ID 0 (default value) and it is different from ID under which the Hibernate session was previously inserted into Map. > Possible patch is in attachements. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HBX-589) Null Pointer Exception if output directory does not exist

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-589?page=all ] Steve Ebersole updated HBX-589: ------------------------------- Comment: was deleted > Null Pointer Exception if output directory does not exist > --------------------------------------------------------- > > Key: HBX-589 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-589 > Project: Hibernate Tools > Type: Bug > Versions: 3.1beta4 > Reporter: Markus Junginger > Fix For: 3.2beta7 > Attachments: Neues Bild.jpg, scrnshot_launcher.jpg > > > It was not possible to generate any artifacts. The given information does not explain anything. > There should be more information about the exception - no stacktrace, etc. See attachment. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-589) Null Pointer Exception if output directory does not exist

by john book (JIRA)

17 years, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2404) Join table should allow to join on multiple columns.

by Daljeet Singh Sarna (JIRA)

Join table should allow to join on multiple columns. ---------------------------------------------------- Key: HHH-2404 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2404 Project: Hibernate3 Type: Improvement Components: core Reporter: Daljeet Singh Sarna Hibernate should allow to perform join on multiple columns. HHH-1829 is fixing issue related to join with column other than key. but if we want to join with more than one column, what should we do. for eg. select * from table1 t1 left outer join table2 t2 on (t1.column1=t2.column3 and t1.column2=t2.column1) -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1829) Allow join on any property using property-ref

by Daljeet Singh Sarna (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829?page=c... ] Daljeet Singh Sarna commented on HHH-1829: ------------------------------------------ I tried using the patch you provided. But I found that it would still fail and then further debugging I found adding following lines to "src/org/hibernate/persister/entity/AbstractEntityPersister.java" will fix the issue. you have suggested one change in the method below. but it seems that "join.addJoin(" inside for loop - > if look also requires update. protected JoinFragment createJoin(String name, boolean innerJoin, boolean includeSubclasses) { //final String[] idCols = StringHelper.qualify( name, getIdentifierColumnNames() ); //all joins join to the pk of the driving table final String[] idCols = getPropertyRefColumnNames() != null && getPropertyRefColumnNames().length > 0 && getPropertyRefColumnNames()[0] != null ? StringHelper.qualify( name, getPropertyRefColumnNames() ) : StringHelper.qualify( name, getIdentifierColumnNames() ); //all joins join to the pk of the driving table final JoinFragment join = getFactory().getDialect().createOuterJoinFragment(); final int tableSpan = getSubclassTableSpan(); for ( int j = 1; j < tableSpan; j++ ) { //notice that we skip the first table; it is the driving table! final boolean joinIsIncluded = isClassOrSuperclassTable( j ) || ( includeSubclasses && !isSubclassTableSequentialSelect( j ) && !isSubclassTableLazy( j ) ); if ( joinIsIncluded ) { join.addJoin( getSubclassTableName( j ), generateTableAlias( name, j ), (getPropertyRefColumnNames() != null && getPropertyRefColumnNames().length > 0 && getPropertyRefColumnNames()[0] != null ) ? new String[]{idCols[j-1]} : idCols, //idCols, getSubclassTableKeyColumns( j ), innerJoin && isClassOrSuperclassTable( j ) && !isInverseTable( j ) && !isNullableTable( j ) ? JoinFragment.INNER_JOIN : //we can inner join to superclass tables (the row MUST be there) JoinFragment.LEFT_OUTER_JOIN //we can never inner join to subclass tables ); } } return join; } > Allow join on any property using property-ref > --------------------------------------------- > > Key: HHH-1829 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829 > Project: Hibernate3 > Type: New Feature > Components: core > Versions: 3.2.0 cr1, 3.2.0.cr2 > Reporter: Maarten Winkels > Assignee: Steve Ebersole > Fix For: 3.2.3 > Attachments: AbstractJoinTest.java, JoinNoPropertyRefTest.java, JoinPropertyRefTest.java, Person.hbm.xml, Person.java, PersonNoPropertyRef.hbm.xml, hhh-1829.patch > > > Currently joining tables for one class (uing the <join...> tag) is only supported for the id property. The property-ref is allowed on the <key..> tag inside the <join..> tag, but this is ignored. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-550) @FieldBridge now use o.h.s.a.Parameter rather than o.h.a.Parameter

by Emmanuel Bernard (JIRA)

@FieldBridge now use o.h.s.a.Parameter rather than o.h.a.Parameter ------------------------------------------------------------------ Key: ANN-550 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-550 Project: Hibernate Annotations Type: Improvement Components: search Versions: 3.2.1 Reporter: Emmanuel Bernard Assigned to: Emmanuel Bernard Fix For: 3.2.2 Better SoC -- 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, 11 months

1
1
0 / 0

[Hibernate-JIRA] Updated: (HB-1458) SchemaUpdate does not create column indexes (MySql)

by rayray (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HB-1458?page=all ] rayray updated HB-1458: ----------------------- Attachment: hibernate3.jar.description.txt > SchemaUpdate does not create column indexes (MySql) > --------------------------------------------------- > > Key: HB-1458 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HB-1458 > Project: Hibernate2 > Type: Improvement > Components: toolset > Versions: 2.1.8 > Environment: Hibernate version: 2.1.8, MySQL version: 4.0.20, MySQL driver: mysql-connector-java-3.0.10-stable (also verified with 3.0.16 and 3.1.7) > Reporter: Keith Wall > Priority: Minor > Attachments: CSDiff.txt, hibernate3.jar, hibernate3.jar.description.txt > > > From forum thread: http://forum.hibernate.org/viewtopic.php?t=939655 > SchemaUpdate is failing to create indices specified using the <column> element in the mapping file. There is no error message generated. If I repeat the same test with the SchemaExport utility, the indices are created successfully. > I include: > 1) A mapping file that demonstrates the problem. This is a modified version of Simple.hbm.xml included in the Hibernate 2.1.8 distribution. > 2) SQL sent to the server by SchemaUpdate (starting with a clean DB). > 3) For comparison, the SQL sent to the server by SchemaExport (starting with a clean DB). > Mapping file: > <hibernate-mapping> > <class name="org.hibernate.test.Simple"> > <id type="long" column="id_"> > <generator class="assigned"/> > </id> >  > <property name="name"> > <column name="name" > index="test_idx" /> > </property> >  > <property name="address"/> > <property name="count" column="count_" not-null="true" unique="true"/> > <property name="date" column="date_"/> > <property name="pay"/> > <many-to-one name="other" access="field"/> > </class> > </hibernate-mapping> > Result: > The table is created successfully, the primary key is created successfully, but no index on the column 'name' is created. > SQL sent to server by SchemaUpdate: > 050309 15:42:57 69 Init DB test > 69 Query select round('inf'), round('-inf'), round('nan') > 69 Query SHOW VARIABLES > 69 Query SET autocommit=1 > 69 Query SET autocommit=0 > 69 Query commit > 69 Query SET autocommit=1 > 69 Query SHOW TABLES FROM `test` LIKE 'Simple' > 69 Query SHOW TABLES FROM `test` LIKE 'Simple' > 69 Query create table Simple (id_ bigint not null, name varchar(255), address varchar(255), count_ integer not null unique, date_ datetime, pay float, other bigint, primary key (id_)) > 69 Query alter table Simple add index FK939D1DD26527F10 (other), add constraint FK939D1DD26527F10 foreign key (other) references Simple (id_) > 69 Query SET autocommit=0 > 69 Query rollback > 69 Quit > SQL sent to server by SchemaExport: > 050309 15:48:22 70 Connect root@localhost on test > 70 Init DB test > 70 Query select round('inf'), round('-inf'), round('nan') > 70 Query SHOW VARIABLES > 70 Query SET autocommit=1 > 70 Query SET autocommit=0 > 70 Query commit > 70 Query SET autocommit=1 > 70 Query alter table Simple drop foreign key FK939D1DD26527F10 > 70 Query drop table if exists Simple > 70 Query create table Simple (id_ bigint not null, name varchar(255), address varchar(255), count_ integer not null unique, date_ datetime, pay float, other bigint, primary key (id_)) > 70 Query create index test_idx on Simple (name) > 70 Query alter table Simple add index FK939D1DD26527F10 (other), add constraint FK939D1DD26527F10 foreign key (other) references Simple (id_) > 70 Quit -- 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, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2007