March 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Updated: (HBX-288) "Generate 'raw' composite ids" setting for Ant script

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-288?page=co... ] Max Rydahl Andersen updated HBX-288: ------------------------------------ Fix Version/s: (was: 3.2.1) 3.2.2 > "Generate 'raw' composite ids" setting for Ant script > ----------------------------------------------------- > > Key: HBX-288 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-288 > Project: Hibernate Tools > Issue Type: Bug > Components: reverse-engineer > Affects Versions: 3.0alpha4 > Environment: Windows XP, Hibernate 3.0, Hibernate Tools 3.0 alpha4, Oracle 10g > Reporter: Jason > Fix For: 3.2.2 > > > According to te documentation the Eclipse Plugin contains a settings on the reverse enginerring UI called "Generate 'raw' composite ids", though there is no equivilant setting for the ant script. -- 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, 9 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HBX-662) Classes in linked folders are not found

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-662?page=co... ] Max Rydahl Andersen updated HBX-662: ------------------------------------ Fix Version/s: (was: 3.2.1) 3.2.2 > Classes in linked folders are not found > --------------------------------------- > > Key: HBX-662 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-662 > Project: Hibernate Tools > Issue Type: Bug > Components: eclipse > Affects Versions: 3.1.beta5 > Environment: Eclipse 3.1.1, JDK 1.4 > Reporter: Mark > Priority: Minor > Fix For: 3.2.2 > > > "Hibernate Configurations" widget shows class not found for classes that are linked to an external directory. > By External directory I mean a directory that is set as build location by using the "Link to folder in the file system" under Project Properties->"Java Build Path"->"Default output folder"->"Browse"->"Create new folder"->"Advanced" > I can pick this path in the "Hibernate Console Configuration"->"Add JAR/Dir", but the class is not picked up. > When I move the build directory to a directory that is physically located inside the Eclipse project tree it works. > MARK -- 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, 9 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HBX-657) improve foreign key constraint name docs and inverse generation

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-657?page=co... ] Max Rydahl Andersen updated HBX-657: ------------------------------------ Fix Version/s: (was: 3.2.1) 3.2.2 > improve foreign key constraint name docs and inverse generation > --------------------------------------------------------------- > > Key: HBX-657 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-657 > Project: Hibernate Tools > Issue Type: Improvement > Affects Versions: 3.1.beta5 > Reporter: Max Rydahl Andersen > Fix For: 3.2.2 > > > <foreign-key constraint-name/> > > Documentation for the constraint-name attribute has to be improved. What exactly is this? Is it something that comes from the database (I know it is)? The > foreign key constraint name is not generated/included in the <many-to-one> column or the collection key column in the hbm.xml file. The set is > inverse="true", even if <many-to-one> is excluded. -- 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, 9 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HBX-656) nvarchar2

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-656?page=co... ] Max Rydahl Andersen updated HBX-656: ------------------------------------ Fix Version/s: (was: 3.2.1) 3.2.2 > nvarchar2 > --------- > > Key: HBX-656 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-656 > Project: Hibernate Tools > Issue Type: Improvement > Components: reverse-engineer > Affects Versions: 3.1.beta5 > Environment: Oracle 10g release 2 > Reporter: Francois Jean > Fix For: 3.2.2 > > > Hello, > When using Oracle with columns of type NVARCHAR2, the reverse engineering tool maps the columns with a java attribute of type Serializable. We would prefer to have these columns mapped to String. However NVARCHAR2 has no corresponding JDBC type, so recognizing this type by Java would imply to verify the JDBC type and if the JDBC type is unknown then verify the type name and if it's VARCHAR2 than map it to String. Do you think it's a possible solution? > For now, we are doing the following in the reverse-eng.xml file, but it's not very neat since it maps all the "OTHER" types to String: > <type-mapping> > <sql-type jdbc-type="OTHER" hibernate-type="String" /> > </type-mapping> > Link on Oracle listing the unsupported Oracle type: > http://download-east.oracle.com/docs/cd/B19306_01/java.102/b14355/apxref.... > Link explaining the use of String with NVARCHAR2: > http://download-east.oracle.com/docs/cd/B19306_01/java.102/b14355/global.... > François Jean -- 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, 9 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HBX-1049) No class generated for tables with only PK columns

by Frank Langelage (JIRA)

No class generated for tables with only PK columns --------------------------------------------------- Key: HBX-1049 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1049 Project: Hibernate Tools Issue Type: Bug Components: hbm2java Affects Versions: 3.2.0.GA Environment: MS SQL Server 2005 Express Edition, Sun JDK 1.5.0_15, Sun Solaris Sparc 10. Hibernate Tools 3.2.0 GA. Reporter: Frank Langelage See http://forum.hibernate.org/viewtopic.php?p=2379128#2379128. Inside my database the are some tables containing only PK fields, nothing else. Both PK fields are also FK to different tables. Example SQL: CREATE TABLE [dbo].[BOMConfiguratorBOMTypes]( [bomcCode] [varchar](20) NOT NULL, [bomtCode] [char](2) NOT NULL, CONSTRAINT [PK_BOMConfiguratorBOMTypes_bomcCode_bomtCode] PRIMARY KEY CLUSTERED ( [bomcCode] ASC, [bomtCode] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] ALTER TABLE [dbo].[BOMConfiguratorBOMTypes] WITH CHECK ADD CONSTRAINT [FK_BOMConfiguratorBOMTypes_BOMConfigurators] FOREIGN KEY([bomcCode]) REFERENCES [dbo].[BOMConfigurators] ([bomcCode]) ON UPDATE CASCADE GO ALTER TABLE [dbo].[BOMConfiguratorBOMTypes] CHECK CONSTRAINT [FK_BOMConfiguratorBOMTypes_BOMConfigurators] GO ALTER TABLE [dbo].[BOMConfiguratorBOMTypes] WITH CHECK ADD CONSTRAINT [FK_BOMConfiguratorBOMTypes_BOMTypes] FOREIGN KEY([bomtCode]) REFERENCES [dbo].[BOMTypes] ([bomtCode]) ON UPDATE CASCADE Hibernate Tools does not generate a class for it. As soon as I add an additional column to such a table the class gets generated. -- 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, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HBX-1048) Table names which are already "camelcase" get false

by Frank Langelage (JIRA)

Table names which are already "camelcase" get false --------------------------------------------------- Key: HBX-1048 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1048 Project: Hibernate Tools Issue Type: Bug Components: hbm2java Affects Versions: 3.2.0.GA Environment: MS SQL Server Express Edition, sun JDK 1.5.0_15 on Solaris Sparc 10 Reporter: Frank Langelage See http://forum.hibernate.org/viewtopic.php?p=2379127#2379127. This small diff fixes the problem for me. If the tablename contains at least one upper case character and one lower case character the table name is taken as it is to use as the class name. If only lower case or only upper case characters are found, the current algorithm is used (camlecase the table name). jboss@sb2000:/home/jboss/Hibernate svn diff HibernateExt Index: HibernateExt/tools/src/java/org/hibernate/cfg/reveng/DefaultReverseEngineeringStrategy.java =================================================================== --- HibernateExt/tools/src/java/org/hibernate/cfg/reveng/DefaultReverseEngineeringStrategy.java (revision 14422) +++ HibernateExt/tools/src/java/org/hibernate/cfg/reveng/DefaultReverseEngineeringStrategy.java (working copy) @@ -128,7 +128,13 @@ public String tableToClassName(TableIdentifier tableIdentifier) { String pkgName = settings.getDefaultPackageName(); - String className = toUpperCamelCase( tableIdentifier.getName() ); + String tableName = tableIdentifier.getName(); + String className; + if(tableName.matches(".*\\p{javaLowerCase}.*" ) && tableName.matches( ".*\\p{javaUpperCase}.*")) { + className = tableName; + } else { + className = toUpperCamelCase( tableName ); + } if(pkgName.length()>0) { return StringHelper.qualify(pkgName, className); -- 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, 9 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-705) Getter annotation trouble

by Cédric Chantepie (JIRA)

Getter annotation trouble ------------------------- Key: ANN-705 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-705 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.1.CR1 Environment: Hibernate EntityManager 3.3.1.ga, PostgreSQL 8.x Reporter: Cédric Chantepie Persistent property annotated by getter (not directly on field, like at page 168 in JPA specs PDF) doesn't seem to be flush to store. -- 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, 9 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-166) documentation error : hibernate.search.worker.batch_size vs hibernate.worker.batch_size

by koen handekyn (JIRA)

documentation error : hibernate.search.worker.batch_size vs hibernate.worker.batch_size --------------------------------------------------------------------------------------- Key: HSEARCH-166 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-166 Project: Hibernate Search Issue Type: Bug Components: documentation Affects Versions: 3.0.1.GA Reporter: koen handekyn in the documentation in table 3.2 the configuration parameter hibernate.worker.batch_size is discussed while it should be hibernate.search.worker.batch_size. -- 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, 9 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3162) Using @CollectionId annotation breaks schema generation

by Tim Evers (JIRA)

Using @CollectionId annotation breaks schema generation ------------------------------------------------------- Key: HHH-3162 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3162 Project: Hibernate3 Issue Type: Bug Environment: Hibernate version: 3.2.5 GA Hibernate Annotations version: 3.3.0 GA Ingres Database 2006 Reporter: Tim Evers Basically, if I use the org.hibernate.annotations.CollectionId annotation, for some reason, hibernate won't generate the table for the mapping. This works: @CollectionOfElements @JoinTable( name = "contact", joinColumns = @JoinColumn(name = "n_key_person")) @IndexColumn(name = "n_index_order") This doesn't: @CollectionOfElements @JoinTable( name = "contact", joinColumns = @JoinColumn(name = "n_key_person")) @CollectionId( columns = @Column(name = "n_key_contact"), type = @Type(type = "long"), generator = "increment" ) It fails when it tries to select from the contact table, because it didn't get created. The @CollectionId mapping seems to work exactly the way I want if I go create the contact table manually. Forum topic here: http://forums.hibernate.org/viewtopic.php?t=980254&highlight=collectionid... -- 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, 9 months

2
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3171) Class with @IdClass gets lazy-loaded when "id" field accessed

by Carl Allain (JIRA)

Class with @IdClass gets lazy-loaded when "id" field accessed -------------------------------------------------------------- Key: HHH-3171 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3171 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Postgres 8.2.5 (also with Oracle 10g) Reporter: Carl Allain Attachments: BugIdClassIds.java, CountrySubdivisionPdoWithEmbeddedId.java, CountrySubdivisionPdoWithIdClass.java Getting id values from Hibernate Proxy cause unwanted lazy initialization when using composite key and IdClass annotation. Lazy initialization behavior should be the same as when using EmbeddedId annotation instead of IdClass since we're accessing fields marked with Id annotation and their value has been provided for the Hibernate Proxy creation. -- 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, 9 months

1
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2008