September 2006 - hibernate-issues

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

by Francois Jean (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-656?page=co... ] Francois Jean commented on HBX-656: ----------------------------------- Are you suggesting adding the XML tag <db-type>, which would let us write the following reverse-engineering snippet? ... <type-mapping> <sql-type db-type="NVARCHAR2" hibernate-type="String" /> </type-mapping> ... > nvarchar2 > --------- > > Key: HBX-656 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-656 > Project: Hibernate Tools > Type: Improvement > Components: reverse-engineer > Versions: 3.1.beta5 > Environment: Oracle 10g release 2 > Reporter: Francois Jean > Fix For: 3.2beta8 > > > 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

18 years, 3 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=all ] Max Rydahl Andersen updated HBX-656: ------------------------------------ Fix Version: 3.2beta8 Priority: Major (was: Minor) would be solvable via db-type type-mapping > nvarchar2 > --------- > > Key: HBX-656 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-656 > Project: Hibernate Tools > Type: Improvement > Components: reverse-engineer > Versions: 3.1.beta5 > Environment: Oracle 10g release 2 > Reporter: Francois Jean > Fix For: 3.2beta8 > > > 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

18 years, 3 months

1
0
0 / 0

[Hibernate-JIRA] Closed: (HBX-594) Use database table comments to generate default class-descriptor in .hbm mapping file and description in java source file

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-594?page=all ] Max Rydahl Andersen closed HBX-594: ----------------------------------- Resolution: Won't Fix decided not to fix since trivial to implement in the templates. > Use database table comments to generate default class-descriptor in .hbm mapping file and description in java source file > -------------------------------------------------------------------------------------------------------------------------- > > Key: HBX-594 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-594 > Project: Hibernate Tools > Type: New Feature > Components: hbm2java, reverse-engineer > Versions: 3.1beta4, 3.1.beta5 > Environment: oracle 10g, hibernate 3.1, tools M4 > Reporter: tony nys > Priority: Minor > > > The idea is, when doing reverse engineering (jdbc db to hbm), to > 1) include the database table/column comment as class-description property in the hibernate mapping file > 2) include the comment as class description in the javasource file. > PS this jdbc setting must be on ! > hibernate.connection.remarksReporting=true -- 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] Closed: (HBX-377) Can't save HQL Scratchpad

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-377?page=all ] Max Rydahl Andersen closed HBX-377: ----------------------------------- Fix Version: 3.2beta7 (was: 3.2LATER) Resolution: Fixed the * now reflect the correct state and seems to work as expected. > Can't save HQL Scratchpad > ------------------------- > > Key: HBX-377 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-377 > Project: Hibernate Tools > Type: Bug > Components: consoleconfiguration > Versions: 3.1alpha5 > Environment: Windows XP, Eclipse 3.1 > Reporter: Dan Bradley > Priority: Minor > Fix For: 3.2beta7 > > > There is no way to save a non-empty HQL Scratchpad or otherwise mark it non-dirty. To reproduce: > - Open a scratchpad window, it's non-dirty. > - Enter anything into it, it's now dirty, as shown by the asterisk in front of the name on its tab. > - Try to save it, it doesn't save, and its dirty state does not change. > - Many Eclipse tasks will now ask you to save it before proceeding > - Try to close it, Eclipse prompts you to save. Say no and the editor closes. But say yes and it also closes also without saving. > More broadly, I'm not sure about the UI approach. What does it mean to save a scratchpad? Do I have to save it to a file? It's a scratchpad after all, not something I want to keep around. But I do want multiple scratchpads to be available. If I save it and it uses some hidden temporary file, that seems like an abuse of the Eclipse editor window. Maybe the scratchpad should be an Eclipse view that can be embedded in the Console Perspective, and which doesn't track a dirty/non-dirty state? -- 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] Closed: (HBX-624) Dialect class not found: org.hibernate.dialect.OracleDialect

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-624?page=all ] Max Rydahl Andersen closed HBX-624: ----------------------------------- Resolution: Incomplete no follow up.. > Dialect class not found: org.hibernate.dialect.OracleDialect > ------------------------------------------------------------ > > Key: HBX-624 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-624 > Project: Hibernate Tools > Type: Bug > Versions: 3.1beta4 > Environment: Eclipse > Reporter: Dominique Vernier > Priority: Minor > > > While I'm trying to create a sessionFactory from the hibernate console, I get this error. > org.hibernate.HibernateException: Dialect class not found: org.hibernate.dialect.OracleDialect > If I remove the hibernate.dialect properties from the hibernate.propertis file is works, but of course I guess the default dialect is loaded... > If I put the hibernate.dialect properties in the hibernate.cfg.xml it works to, but then I have to have one hibernate.cfg.xml for the Hibernate console and another one for my test. > I noticed that I have some spaces left after the "org.hibernate.dialect.OracleDialect". I removed them and it was ok. > It would be good, if we can add a trim() in the hibernate tool. -- 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] Closed: (HBX-593) Reverse engineering editor generates invalid XML (JDBC type)

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-593?page=all ] Max Rydahl Andersen closed HBX-593: ----------------------------------- Resolution: Rejected turned out not to be a bug > Reverse engineering editor generates invalid XML (JDBC type) > ------------------------------------------------------------ > > Key: HBX-593 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-593 > Project: Hibernate Tools > Type: Bug > Versions: 3.1beta4 > Reporter: Markus Junginger > Priority: Minor > > > If leaving the JDBC type empty in the Column section (Tab Table&Columns), the following XML is generated: > <column name="BEZAHLT" jdbc-type='' type="yes_no"/> > Would be better to a) check if the field is empty and diaply an error message or b) generate valid code ;) -- 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] Closed: (HBX-587) Null pointer exception in "Hibernate Code Generation"

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-587?page=all ] Max Rydahl Andersen closed HBX-587: ----------------------------------- Fix Version: 3.2beta8 Resolution: Fixed assumed fixed since i can't reproduce plus i added safety checks when launching > Null pointer exception in "Hibernate Code Generation" > ----------------------------------------------------- > > Key: HBX-587 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-587 > Project: Hibernate Tools > Type: Bug > Versions: 3.1beta4 > Reporter: Markus Junginger > Priority: Minor > Fix For: 3.2beta8 > > > Null pointer ex if no console configuration is chosen in "Hibernate Code Generation" Window -- 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] Closed: (HBX-599) Cannot export DDL from reverse engineered EJB3 File

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-599?page=all ] Max Rydahl Andersen closed HBX-599: ----------------------------------- Resolution: Duplicate > Cannot export DDL from reverse engineered EJB3 File > --------------------------------------------------- > > Key: HBX-599 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-599 > Project: Hibernate Tools > Type: Bug > Versions: 3.1beta4 > Reporter: Markus Junginger > Priority: Minor > > > FIrst, I created an EJB3 Java classes using: > <hibernatetool > > <jdbcconfiguration configurationfile="src/hibernate.cfg.xml" revengfile="hibernate.reveng.xml" packagename="de.unilog.ejb3"/> > <hbm2java destdir="src-ejb3" ejb3="true"/> > <hbm2cfgxml destdir="src-ejb3" ejb3="true" /> > </hibernatetool> > Then, I tried to let Hibernate Tools parse it's own output to generate DDL: > <hibernatetool> > <annotationconfiguration configurationfile="src-ejb3/hibernate.cfg.xml" /> > <hbm2ddl update="true" export="true" outputfilename="demo.ddl" delimiter=";" destdir="."/> > </hibernatetool> > However, I got the following error: > BUILD FAILED > C:\Daten\Projekte\hibernate-tools\build2.xml:4: org.hibernate.AnnotationException: Collection has neither generic type or OneToMany.targetEntity() defined: de.unilog.ejb3.Kunde.bestellungs > -- > PS.: The generated Java file: > package de.unilog.ejb3; > // Generated 15.02.2006 09:53:14 by Hibernate Tools 3.1.0.beta4 > import java.util.HashSet; > import java.util.Set; > import javax.persistence.CascadeType; > import javax.persistence.Column; > import javax.persistence.Entity; > import javax.persistence.FetchType; > import javax.persistence.Id; > import javax.persistence.OneToMany; > import javax.persistence.Table; > /** > * Kunde generated by hbm2java > */ > @Entity > @Table(name="KUNDE" > , uniqueConstraints = { } > ) > public class Kunde implements java.io.Serializable { > // Fields > private int kundeId; > private String name; > private Set bestellungs = new HashSet(0); > // Constructors > /** default constructor */ > public Kunde() { > } > /** minimal constructor */ > public Kunde(int kundeId) { > this.kundeId = kundeId; > } > > /** full constructor */ > public Kunde(int kundeId, String name, Set bestellungs) { > this.kundeId = kundeId; > this.name = name; > this.bestellungs = bestellungs; > } > > > // Property accessors > @Id > @Column(name="KUNDE_ID", unique=true, nullable=false, insertable=true, updatable=true) > public int getKundeId() { > return this.kundeId; > } > > public void setKundeId(int kundeId) { > this.kundeId = kundeId; > } > @Column(name="NAME", unique=false, nullable=true, insertable=true, updatable=true, length=99) > public String getName() { > return this.name; > } > > public void setName(String name) { > this.name = name; > } > @OneToMany(cascade={CascadeType.ALL}, fetch=FetchType.LAZY, mappedBy="kunde") > public Set getBestellungs() { > return this.bestellungs; > } > > public void setBestellungs(Set bestellungs) { > this.bestellungs = bestellungs; > } > > } -- 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] Closed: (HBX-536) Reverse Engineering Tool maps decimal to boolean, causing errors in POJO code ( hashcode() method in composite class )

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-536?page=all ] Max Rydahl Andersen closed HBX-536: ----------------------------------- Resolution: Cannot Reproduce need testcase to reproduce...closing. > Reverse Engineering Tool maps decimal to boolean, causing errors in POJO code ( hashcode() method in composite class ) > ---------------------------------------------------------------------------------------------------------------------- > > Key: HBX-536 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-536 > Project: Hibernate Tools > Type: Bug > Components: reverse-engineer > Versions: 3.1beta1 > Environment: Hibernate Tools 3.1.0 beta1JBIDERC2, DB2 UDB 7.2 > Reporter: John Hazel > Priority: Minor > > Original Estimate: 3 hours > Remaining: 3 hours > > The reverse engineering tool is mapping SQL DECIMAL to Java primitive boolean. This is also causing an error in the composite class hashcode() method, where the code is trying to cast from boolean to int. > ... > result = 37 * result + (int) this.isStatusactive(); > ... > STATUSACTIVE is a DECIMAL in the DB2 table. It is converted to a primitive boolean in the POJO generation. -- 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] Closed: (HBX-569) ReverseEngineeringStrategy doesn't observe destination package

by Max Rydahl Andersen (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-569?page=all ] Max Rydahl Andersen closed HBX-569: ----------------------------------- Fix Version: 3.2beta7 Resolution: Fixed strategies now get those settings via ReverseEngineeringSettings > ReverseEngineeringStrategy doesn't observe destination package > -------------------------------------------------------------- > > Key: HBX-569 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-569 > Project: Hibernate Tools > Type: Bug > Components: reverse-engineer > Versions: 3.1beta4 > Environment: Eclipse 3.1.2, JDK 1.5.0_01, SQL Server 2005, JTDS JDBC Driver > Reporter: Matt Read > Priority: Minor > Fix For: 3.2beta7 > > > I have successfully used the Hibernate Code Generation part of the plugin to generate .hbm.xml files and POJO Java classes from my JDBC Connection. The code generation configuration has a target package name of com.matt. > I then implemented a ReverseEngineering Strategy as shown below. The destination package is ignored and both .java and .hbm.xml files are put in the directory specified as "output directory". > Should I be explicitly coding the package name into my ReverseEngineeringStrategy implementation or is their a utility to allow me to access the target package setting? > public class InsuranceLedgerStrategy extends DelegatingReverseEngineeringStrategy { > public InsuranceLedgerStrategy(ReverseEngineeringStrategy delegate) { > super(delegate); > } > public String tableToClassName(TableIdentifier table) { > > return table.getName().substring(3); > > } > } > Thanks, > Matt. -- 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 2006