February 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2767) TimestampType uses SimpleDateFormat, which does not include Timestamp nanoseconds

by Alan Krueger (JIRA)

TimestampType uses SimpleDateFormat, which does not include Timestamp nanoseconds --------------------------------------------------------------------------------- Key: HHH-2767 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2767 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.2 Environment: Hibernate 3.2.2 Reporter: Alan Krueger Priority: Minor TimestampType uses SimpleDateFormat when storing the value as a string, which does not include java.sql.Timestamp's nanoseconds. This appears to mean that auto-flushes see Timestamp fields changing value when using EntityType.DOM4J when there is a nanosecond component to the timestamp. -- 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

16 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-751) Hibernate reports erroneous "possible typo error" for properties with protected accessor methods

by Stephen R. Saucier (JIRA)

Hibernate reports erroneous "possible typo error" for properties with protected accessor methods ------------------------------------------------------------------------------------------------ Key: ANN-751 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-751 Project: Hibernate Annotations Issue Type: Improvement Affects Versions: 3.3.0.ga Reporter: Stephen R. Saucier Priority: Minor Attachments: checkForOrphanProperties.patch According to the EJB3 spec, section 2.1.1 (Persistent Fields and Properties), "property accessor methods must be public or protected." However, the checkForOrphanProperties method of org.hibernate.cfg.annotations.reflection.EJB3OverridenAnnotationReader only looks for public methods (by virtue of the fact that it is using the getMethods method of Class. I believe that the checkForOrphanProperties method ought to look at the protected methods implemented in the entity class as well in order to eliminate the erroneous warning messages that are reported when using hibernate with protected property accessor methods. I've attached a patch which implements this additional behavior. -- 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

16 years, 8 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HBX-1093) Missing inverseJoinColumn at ManyToMany relations with composite keys

by Nils Kelleter (JIRA)

Missing inverseJoinColumn at ManyToMany relations with composite keys --------------------------------------------------------------------- Key: HBX-1093 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1093 Project: Hibernate Tools Issue Type: Bug Components: hbm2java Affects Versions: 3.2.2, 3.2LATER Environment: Hibernate Tools version 3.2.2.Beta1 and 3.2.4.CR1-N200810300202, Oracle Database Reporter: Nils Kelleter Using the hbm2java tool for reverse engineering of database tables, the following problem exists: At ManyToMany relations with composite keys an inverseJoinColumn is missing. Wrong code: @ManyToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY) @JoinTable(name = "ET_MANY_TO_MANY_COMP_MAPPING", joinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP1_ID", nullable = false, updatable = false), @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP11_ID", nullable = false, updatable = false) }, inverseJoinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP2_ID", nullable = false, updatable = false) }) public Set<EtManyToManyComp2> getEtManyToManyComp2s() { return this.etManyToManyComp2s; } @ManyToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY) @JoinTable(name = "ET_MANY_TO_MANY_COMP_MAPPING", joinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP2_ID", nullable = false, updatable = false), @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP22_ID", nullable = false, updatable = false) }, inverseJoinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP1_ID", nullable = false, updatable = false) }) public Set<EtManyToManyComp1> getEtManyToManyComp1s() { return this.etManyToManyComp1s; } Correct code: @ManyToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY) @JoinTable(name = "ET_MANY_TO_MANY_COMP_MAPPING", joinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP1_ID", nullable = false, updatable = false), @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP11_ID", nullable = false, updatable = false) }, inverseJoinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP2_ID", nullable = false, updatable = false), @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP22_ID", nullable = false, updatable = false) }) public Set<EtManyToManyComp2> getEtManyToManyComp2s() { return this.etManyToManyComp2s; } @ManyToMany(cascade = CascadeType.ALL, fetch = FetchType.LAZY) @JoinTable(name = "ET_MANY_TO_MANY_COMP_MAPPING", joinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP2_ID", nullable = false, updatable = false), @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP22_ID", nullable = false, updatable = false) }, inverseJoinColumns = { @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP1_ID", nullable = false, updatable = false), @JoinColumn(name = "FK_ET_MANY_TO_MANY_COMP11_ID", nullable = false, updatable = false) }) public Set<EtManyToManyComp1> getEtManyToManyComp1s() { return this.etManyToManyComp1s; } For reproducing this, you can use the following Oracle SQL scripts: CREATE TABLE ET_MANY_TO_MANY_COMP1 ( ET_MANY_TO_MANY_COMP1_ID NUMBER, ET_MANY_TO_MANY_COMP11_ID NUMBER, FIELD VARCHAR2(10), PRIMARY KEY (ET_MANY_TO_MANY_COMP1_ID, ET_MANY_TO_MANY_COMP11_ID) ); CREATE TABLE ET_MANY_TO_MANY_COMP2 ( ET_MANY_TO_MANY_COMP2_ID NUMBER, ET_MANY_TO_MANY_COMP22_ID NUMBER, FIELD VARCHAR2(10), PRIMARY KEY (ET_MANY_TO_MANY_COMP2_ID, ET_MANY_TO_MANY_COMP22_ID) ); CREATE TABLE ET_MANY_TO_MANY_COMP_MAPPING ( FK_ET_MANY_TO_MANY_COMP1_ID NUMBER, FK_ET_MANY_TO_MANY_COMP11_ID NUMBER, FK_ET_MANY_TO_MANY_COMP2_ID NUMBER, FK_ET_MANY_TO_MANY_COMP22_ID NUMBER, FOREIGN KEY (FK_ET_MANY_TO_MANY_COMP1_ID,FK_ET_MANY_TO_MANY_COMP11_ID) REFERENCES ET_MANY_TO_MANY_COMP1(ET_MANY_TO_MANY_COMP1_ID,ET_MANY_TO_MANY_COMP11_ID), FOREIGN KEY (FK_ET_MANY_TO_MANY_COMP2_ID, FK_ET_MANY_TO_MANY_COMP22_ID) REFERENCES ET_MANY_TO_MANY_COMP2(ET_MANY_TO_MANY_COMP2_ID, ET_MANY_TO_MANY_COMP22_ID), PRIMARY KEY (FK_ET_MANY_TO_MANY_COMP1_ID,FK_ET_MANY_TO_MANY_COMP11_ID,FK_ET_MANY_TO_MANY_COMP2_ID,FK_ET_MANY_TO_MANY_COMP22_ID) ); -- 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

16 years, 8 months

5
9
0 / 0

[Hibernate-JIRA] Created: (HBX-1112) Reverse engineering problem with composite primary key

by Christian Meyer (JIRA)

Reverse engineering problem with composite primary key ------------------------------------------------------ Key: HBX-1112 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1112 Project: Hibernate Tools Issue Type: Bug Affects Versions: 3.2.4 Beta1 Environment: configuration: Hibernate Tools version: HibernateTools-3.2.4.CR2-R200901280154 Hibernate version: hibernate-3.2.6.ga.zip Database: Sybase SQL Anywhere 10.0.1.3415 JDBC-Driver: jconnect 6.05 Eclipse Version: 3.4.0 Code Generation Configuration: Use Java 5 syntax and generate EJB3 annotations switched on. Exporters: domain code. Reporter: Christian Meyer Hello, I have a problem reverse engineering domain code from a sybase anywhere 10 database. For every table with composite primary key i get the following exception: org.hibernate.cfg.JDBCBinderException: Duplicate names found for primarykey. Her is one example: create table DCALLS ( AES timestamp default timestamp, APPLID char(8) not null, DIALOG integer not null, COUNTER integer, constraint PK_DCALLS primary key (APPLID, DIALOG) ); For downloading developer edition of sybase anywhere version 10 follow the link: http://marketing.ianywhere.com/forms/SQLAny10DevEditionCDReigster I used a Hibernate dialect from the sybase homepage: http://www.sybase.de/detail?id=1057826 org.hibernate.cfg.JDBCBinderException: Duplicate names found for primarykey. Existing name: APPLID JDBC name: DIALOG on table org.hibernate.mapping.Table(sybase10.DCALLS) Duplicate names found for primarykey. Existing name: APPLID JDBC name: DIALOG on table org.hibernate.mapping.Table(sybase10.DCALLS) all Tables with single key are fine. -- 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

16 years, 8 months

5
8
0 / 0

[Hibernate-JIRA] Created: (BVAL-109) Write unit tests for bootstrapping

by Hardy Ferentschik (JIRA)

Write unit tests for bootstrapping ----------------------------------- Key: BVAL-109 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-109 Project: Bean Validation Issue Type: Task Components: ri-general Reporter: Hardy Ferentschik There are already some tests in ValidationTest, but we need more tests. Especially we have to test that we can plug custom MessageInterpolator, ConstraintValidatorFactory and TraversableResolver using different ConfigurationStates. -- 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

16 years, 8 months

2
7
0 / 0

[Hibernate-JIRA] Created: (ANN-657) @Enumerated(value=EnumType.STRING) for Maps (java.util.EnumMap) ?

by Michael Grünewald (JIRA)

@Enumerated(value=EnumType.STRING) for Maps (java.util.EnumMap) ? ----------------------------------------------------------------- Key: ANN-657 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-657 Project: Hibernate Annotations Issue Type: Improvement Affects Versions: 3.3.0.ga Environment: hibernate 3.2.4.sp1; PostgresSql 8.2 Reporter: Michael Grünewald Priority: Minor Hi, I faced the problem, that I can't enforce a String-Mapping for an enum type key of an Map. E.g.: Map<? extends Enum<?>, String> I would suppose to use an attribute for @MapKey to do that. E.g.: @MapKey (enumerated=EnumType.STRING) Please read the forum entry for more informations. http://forum.hibernate.org/viewtopic.php?t=97827 Greetings Michael -- 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

16 years, 8 months

5
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2603) Deprecate the Session.connection() method

by Steve Ebersole (JIRA)

Deprecate the Session.connection() method ----------------------------------------- Key: HHH-2603 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2603 Project: Hibernate3 Issue Type: Deprecation Components: core Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.2.4 Deprecate the Session.connection() method, in favor of a "JDBC work" API. Schedule for removal in 4.0 -- 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

16 years, 8 months

14
26
0 / 0

[Hibernate-JIRA] Created: (HHH-3686) Sybase - QueryCacheTest.testQueryCacheInvalidation fails

by Gail Badner (JIRA)

Sybase - QueryCacheTest.testQueryCacheInvalidation fails -------------------------------------------------------- Key: HHH-3686 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3686 Project: Hibernate Core Issue Type: Bug Reporter: Gail Badner Assignee: Gail Badner By default, Sybase string comparisons are case-insensitive. It can be configured to be case-insensitive. It may be possible to determine which is configured by looking at DatabaseMetaData to return the appropriate value for SybaseDialect.areStringComparisonsCaseInsensitive(). -- 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

16 years, 8 months

2
9
0 / 0

[Hibernate-JIRA] Created: (EJB-315) unnecessary update when merge managed entity

by Jifeng Liu (JIRA)

unnecessary update when merge managed entity -------------------------------------------- Key: EJB-315 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-315 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.3.1.GA Environment: Hibernate Core 3.2.5.ga Hibernate Annotations 3.3.0 GA hsqldb Reporter: Jifeng Liu Attachments: testcase.zip If the entity in em.merge(entity) is managed entity, the merge operation should be ignored. However it issues a update statement in the test case even if there is no changes. In the test case, Parent entity has a list of Image entity with Many-To-Many relation. em.merge() somehow marks the list as dirty, which causes the update statement. The following is trace log of the test case. 07.20,23 INFO ASTQueryTranslatorFactory - Using ASTQueryTranslatorFactory 07.20,601 DEBUG SQL - /* insert test.Parent */ insert into Parent (updateDateTime, Parent_No) values (?, ?) 07.20,617 DEBUG SQL - /* insert test.Image */ insert into Image (name, imageNo) values (?, ?) 07.20,617 DEBUG SQL - /* insert collection row test.Parent.images */ insert into Parent_Image (Parent_Parent_No, images_ imageNo) values (?, ?) 07.20,632 DEBUG SQL - /* load test.Parent */ select parent0_.Parent_No as Parent1_0_0_, parent0_.updateDateTime as updat eDa2_0_0_ from Parent parent0_ where parent0_.Parent_No=? 07.20,648 DEBUG SQL - /* load collection test.Parent.images */ select images0_.Parent_Parent_No as Parent1_1_, images0_. images_imageNo as images2_1_, image1_.imageNo as imageNo1_0_, image1_.name as name1_0_ from Parent_Image images0_ left o uter join Image image1_ on images0_.images_imageNo=image1_.imageNo where images0_.Parent_Parent_No=? 07.20,679 DEBUG SQL - /* update test.Parent */ update Parent set updateDateTime=? where Parent_No=? and updateDateTime=? 07.20,679 DEBUG SQL - /* delete collection test.Parent.images */ delete from Parent_Image where Parent_Parent_No=? 07.20,679 DEBUG SQL - /* insert collection row test.Parent.images */ insert into Parent_Image (Parent_Parent_No, images_ imageNo) values (?, ?) -- 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

16 years, 8 months

4
3
0 / 0

[Hibernate-JIRA] Created: (HHH-3560) Assume entities relationships as unversioned by default

by Adam Warski (JIRA)

Assume entities relationships as unversioned by default ------------------------------------------------------- Key: HHH-3560 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3560 Project: Hibernate Core Issue Type: New Feature Components: envers Reporter: Adam Warski http://www.jboss.com/index.html?module=bb&op=viewtopic&t=141471 Assume that each relation between entities is unversioned unless entity is explicitly annotated with @Versioned. In current implementation if versioned entity has reference to non-versioned entity an MappingException is being thrown unless the @Unversioned annotation is used in appropriate field. If there is a lot of entities that are referenced but not versioned it requires to apply lot of @Unversioned annotations. This is quite error-prone while it is easy to forgot about some fields. I've suggest to treat each reference to entity as it is annotated with @Unversioned unless the entity is annotated with @Versioned. In other words treat entities ralationships as implicitly @Unversioned unless @Versioned is not set explicitly. -- 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

16 years, 8 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2009