September 2007 - hibernate-issues

[Hibernate-JIRA] Commented: (HHH-530) Better handling of filter params in HQL to allow filter use on subqueries

by Shawn Clowater (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-530?page=co... ] Shawn Clowater commented on HHH-530: ------------------------------------ Blast from the past. Forgot all about this until I jacked in the patch for the createAlias for Subqueries for a coworker today. Then noticed that filters weren't applied to the joins. And then when I touched that up, the incorrect binding order. This is definitely a show stopper for me, I either need this or the ability to specify the same association twice in 2 separate createAlias calls. I guess the other alternative would be HQL w/o the use of subqueries. I'll be investigating applying the above patch in the morning (which for me is 12 hours) to a 3.2.5 jar. If more work is needed for this I can be available for either development and/or guinea pig, we've got a bunch of filters being used so if something comes off the rails it should be pretty apparent. > Better handling of filter params in HQL to allow filter use on subqueries > ------------------------------------------------------------------------- > > Key: HHH-530 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-530 > Project: Hibernate3 > Issue Type: Bug > Components: core > Reporter: Gavin King > Assignee: Steve Ebersole > Attachments: hibernate_filter_fix-3.0.5.patch, hibernate_filter_fix-3.0.5_14.patch > > > Currently filter conditions are applied in subselects, they should not be. -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1493) mapping.Table fails to add a nullable column (without default value)

by Patrick Decat (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1493?page=c... ] Patrick Decat commented on HHH-1493: ------------------------------------ Hi, I too have encountered this problem with Sybase ASE 12.0.0.8. I've uploaded a proper patch generated with 'svn diff' as Table.java.patch2 (see HHH-1494). Best regards, Patrick. > mapping.Table fails to add a nullable column (without default value) > -------------------------------------------------------------------- > > Key: HHH-1493 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1493 > Project: Hibernate3 > Issue Type: Bug > Components: core > Affects Versions: 3.1.2 > Environment: Sybase 11.1.1-swr8229, Window XP, java 1.4.2_08-b03 > Reporter: Alexis Midon > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > org.hibernate.mapping.Table.sqlAlterStrings(...) method builds a malformed 'alter table' query when the column is nullable (without any default value). > For instance, generated query is: > alter table MY_TABLE add FOO varchar(255) > instead of: > alter table MSP_STPFC_ENTRY_TABLE add FUU varchar(255) null > The mistake is obvious when you compare with method Table.sqlCreateString(...) -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1494) Path for Bug HHH-1493

by Patrick Decat (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1494?page=c... ] Patrick Decat updated HHH-1494: ------------------------------- Attachment: Table.java.patch2 Proper patch against trunk @rev 14028 > Path for Bug HHH-1493 > --------------------- > > Key: HHH-1494 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1494 > Project: Hibernate3 > Issue Type: Patch > Components: core > Affects Versions: 3.1.1, 3.1.2 > Environment: sybase 11.1.1-swr8229, Windows XP, java 1.4.2_08-b03 > Reporter: Alexis Midon > Attachments: Table.java.patch, Table.java.patch2 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > This a patch for Bug HHH-1493: "mapping.Table fails to add a nullable column" > http://opensource.atlassian.com/projects/hibernate/browse/HHH-1493 -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1494) Path for Bug HHH-1493

by Patrick Decat (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1494?page=c... ] Patrick Decat commented on HHH-1494: ------------------------------------ Here is a proper patch against current trunk@14028 : Index: /home/pdecat/workspace/eclipse-3.3/hibernate-core-trunk-mapping/Table.java =================================================================== --- /home/pdecat/workspace/eclipse-3.3/hibernate-core-trunk-mapping/Table.java (révision 14028) +++ /home/pdecat/workspace/eclipse-3.3/hibernate-core-trunk-mapping/Table.java (copie de travail) @@ -295,15 +295,14 @@ String defaultValue = column.getDefaultValue(); if ( defaultValue != null ) { alter.append( " default " ).append( defaultValue ); - - if ( column.isNullable() ) { - alter.append( dialect.getNullColumnString() ); - } - else { - alter.append( " not null" ); - } - } + + if ( column.isNullable() ) { + alter.append( dialect.getNullColumnString() ); + } + else { + alter.append( " not null" ); + } boolean useUniqueConstraint = column.isUnique() && dialect.supportsUnique() && > Path for Bug HHH-1493 > --------------------- > > Key: HHH-1494 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1494 > Project: Hibernate3 > Issue Type: Patch > Components: core > Affects Versions: 3.1.1, 3.1.2 > Environment: sybase 11.1.1-swr8229, Windows XP, java 1.4.2_08-b03 > Reporter: Alexis Midon > Attachments: Table.java.patch > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > This a patch for Bug HHH-1493: "mapping.Table fails to add a nullable column" > http://opensource.atlassian.com/projects/hibernate/browse/HHH-1493 -- 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2089) ClobType.setToXMLNode: could not read XML from Clob

by Pietro Iglio (JIRA)

ClobType.setToXMLNode: could not read XML from Clob --------------------------------------------------- Key: HHH-2089 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2089 Project: Hibernate3 Type: Patch Components: core Versions: 3.2.0.cr4 Environment: Hib 3.2.0cr4, database: any Reporter: Pietro Iglio I get "org.hibernate.HibernateException: could not read XML from Clob" trying to retrieve a CLOB column as XML. I think I have found the reason of the bug in org.hibernate.type.ClobType: public void setToXMLNode(Node node, Object value, SessionFactoryImplementor factory) { ... node.setText( clob.getSubString(0, len) ); ... } According to the JDBC spec, the first character of Clob is at 1 position, so the correct line should be node.setText( clob.getSubString(1, len) ); -- 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

18 years, 3 months

4
5
0 / 0

[Hibernate-JIRA] Created: (ANN-661) Add support for named pure native scalar queries

by Chris Bredesen (JIRA)

Add support for named pure native scalar queries ------------------------------------------------ Key: ANN-661 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-661 Project: Hibernate Annotations Issue Type: New Feature Components: binder Reporter: Chris Bredesen Priority: Minor This feature has been requested but is not yet implemented: Caused by: org.hibernate.cfg.NotYetImplementedException: Pure native scalar queries are not yet supported at org.hibernate.cfg.annotations.QueryBinder.bindNativeQuery(QueryBinder.java:118) at org.hibernate.cfg.AnnotationBinder.bindQueries(AnnotationBinder.java:277) at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:417) at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:498) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:277) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1286) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:915) at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:730) -- 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

18 years, 3 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HBX-730) SchemaExport with hibernate.hbm2ddl.auto does not create database schemas before it creates tables (fails with invalid schema name: on HSQLDB)

by Andrew Thompson (JIRA)

SchemaExport with hibernate.hbm2ddl.auto does not create database schemas before it creates tables (fails with invalid schema name: on HSQLDB) ----------------------------------------------------------------------------------------------------------------------------------------------- Key: HBX-730 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-730 Project: Hibernate Tools Type: Improvement Environment: Hibernate 3.0.5, HSQLDB 1.8 I've also read the code in the SchemaExport, Table and Configuration classes in 3.2rc3 and it looks like this hasn't been added in 3.1 or 3.2. Reporter: Andrew Thompson I'm writing a unit test that creates the database it will work with using hibernate.hbm2ddl.auto=create-drop. This all works fine, so long as I don't use schemas in my .hbm.xml: <class name="com.example.Foo" table="foo_table"> If I add a schema like this, then the database creation fails on HSQLDB 1.8: <class name="com.example.Foo" schema="bar" table="foo_table"> Unsuccessful: create table bar.foo_table ( ... column names ... ) hbm2ddl.SchemaExport - invalid schema name: BAR in statement [create table bar.foo_table] As far as I know there is no way to ask Hibernate to create the schema before it tries to create the tables. There is a forum thread here that shows I am not the only one with this issue: http://forum.hibernate.org/viewtopic.php?p=2316411&sid=c0cd248a87bfb8d684... As this is a unit test, precreating the schema in the test code is plausible, but not particularly attractive. -- 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

18 years, 3 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2314) EntityUpdateAction does not do a deepCopy for loadedState, making change detection of Custom Type based on a Collection not working

by arnaud.roger＠gmail.com (JIRA)

EntityUpdateAction does not do a deepCopy for loadedState, making change detection of Custom Type based on a Collection not working ----------------------------------------------------------------------------------------------------------------------------------- Key: HHH-2314 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2314 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.ga, 3.2.1 Environment: Hibernate 3.2.1.ga, SQLServer and Oracle 10 Reporter: arnaud.roger(a)gmail.com We have a User object with a roles HashSet<String> that is map with a CustomType to VARCHAR in the database using a comma separated format. When this Entity is manipulated through a long transaction hibernate does not detect that the Entity is dirty and does not flush the change to the database. This does not happen in Hibernate 3.1.1 After tracing through Hibernate I identified the bug. This is due to a change in the 3.2 branch in EntityUpdateAction http://fisheye.jboss.org/browse/~br=tag%3Av321/Hibernate/tags/v321/Hibern... The deepCopy is done only when hasUpdateGeneratedProperties() is true, which I is not for our User object. So the set is not deepCopy and the lastUpdated array got a reference to the the same set as the user object. Any modification is so done in the lastUpdated and the User entity, making the object non dirty. rollbacking to the 3.1.1 version of this file probably fix the issue. Regards Arnaud PS: I'd try to produce a simple test case in the next days -- 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

18 years, 3 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-2865) Criteria generated SQL query has duplicated column names

by Juan Ignacio Sánchez (JIRA)

Criteria generated SQL query has duplicated column names -------------------------------------------------------- Key: HHH-2865 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2865 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, Oracle Reporter: Juan Ignacio Sánchez I'm doing a Criteria.list() query and it throws this exception: INFO LongType:182 - could not read column value from result set: C2_12_; Fallo al convertir a representación interna (internal representation conversion failure). So I looked at the generated query, and saw C2_12_ appears twice. SELECT this_.c_tarea_id AS c1_2_10_, this_.d_comentario AS d2_2_10_, this_.f_alta AS f3_2_10_, this_.f_hecho AS f4_2_10_, this_.f_plazo AS f5_2_10_, this_.c_mgestionado_modelo AS c7_2_10_, ... estado5_.d_nombre AS d4_0_1_, opciones6_.c_tarea_id AS c1_12_, [b]opcs1_.c_mgestionado_id AS c2_12_[/b], opcs1_.c_transicion_id AS c3_12_, opcs1_.c_mgestionado_id AS c1_3_2_, opcs1_.c_transicion_id AS c2_3_2_, ... rolespermi10_.c_mgestionado_id AS c1_12_, [b]rolespermi10_.c_transicion_id AS c2_12_[/b], rol11_.c_rol AS c3_12_, rol11_.c_rol AS c1_26_5_, rol11_.d_rol AS d2_26_5_, ... WHERE ups2_.c_usuario IN (?) AND this_.f_hecho IS NULL When Hibernate extracts query results to objects it will fail because 'C2_12_' refers to different data types. -- 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

18 years, 3 months

2
1
0 / 0

[Hibernate-JIRA] Updated: (HHH-1853) CREATE SCHEMA inside database-object need to execute before tables are created

by Stephen Cooper (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853?page=c... ] Stephen Cooper updated HHH-1853: -------------------------------- Attachment: create-schema2.patch Modification of previous patch, so that the schema creation syntax is delegated to the dialect object. Also, patched the HSQL dialect so that it generates the schema with the required "authorization dba" additional syntax. > CREATE SCHEMA inside database-object need to execute before tables are created > ------------------------------------------------------------------------------ > > Key: HHH-1853 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1853 > Project: Hibernate3 > Issue Type: Improvement > Affects Versions: 3.1.3 > Environment: hsqldb 1.8.0 > Reporter: Mattias Jiderhamn > Priority: Minor > Attachments: create-schema.patch, create-schema2.patch > > > In order to have Hibernate create database schemas for hsqldb, you have to insert a <database-object> in your mapping file (http://forums.hibernate.org/viewtopic.php?p=2305138). Problem is, all the database-object statements are executed after the tables are created, so tables in non-default schemas will not be created. To get around this, you have to first use Configuration.generateSchemaCreationScript() to get the schemas, and then Configuration.generateSchemaUpdateScript() to get the tables inside the schemas. > (This is a bit problematic when using Springs LocalSessionFactoryBean) -- 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

18 years, 3 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues September 2007