May 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HV-129) ResourceBundleMessageInterpolatorTest should not test ResourceBundleMessageInterpolato but rather the Bean Validation provider default bundle

by Emmanuel Bernard (JIRA)

ResourceBundleMessageInterpolatorTest should not test ResourceBundleMessageInterpolato but rather the Bean Validation provider default bundle --------------------------------------------------------------------------------------------------------------------------------------------- Key: HV-129 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-129 Project: Hibernate Validator Issue Type: Improvement Reporter: Emmanuel Bernard -- 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, 7 months

2
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-11) Incorrect use of generics

by Emmanuel Bernard (JIRA)

Incorrect use of generics ------------------------- Key: BVAL-11 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-11 Project: Bean Validation Issue Type: Bug Components: ri-general Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik There is too many @SuppressWarning("unchecked") For a library using no legacy code, this should not happen. Some might be the fault of an improper Bean Validation generics design but I have seen incorrect uses of generics in the ri itself hidden by @SWs I will open specific reports for the one I have seen but the goal is to get rid of (almost) all @SuppressWarnings. -- 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, 7 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3891) one-to-one with property-ref always non-lazy

by Sandeep Vaid (JIRA)

one-to-one with property-ref always non-lazy -------------------------------------------- Key: HHH-3891 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3891 Project: Hibernate Core Issue Type: Bug Components: core Reporter: Sandeep Vaid I have one-to-one relationship betnwee Product and ProductBasic. <one-to-one name="productBasic" cascade="save-update" property-ref="activeProduct" lazy="proxy"> <formula>'1'</formula> <formula>PRODUCTID</formula> </one-to-one> ProductBasic.hbm.xml as : <properties name="activeProduct"> <property name="Code" column="CODE"></property> <property name="pId" column="PID" insert="false" update="false"></property> </properties> When i am using property-ref, and try to load Product, it eagerly fetches ProductBasic also as : select * from PRODUCT productbo0_ left outer join PRODUCTPERIOD productbas1_ on '18'=productbas1_.CODE and productbo0_.PID=productbas1_.PID where productbo0_.PID=? NOTE: Along with Product, ProductBasic is also fetched in a single query. Even if i add constrained="true" in one-to-one mapping, the query gets fired as : select * from PRODUCT productbo0_ where productbo0_.PID=? select * from PRODUCTBASIC productbas0_ where productbas0_.CODE=? and productbas0_.PID=? NOTE: Along with Product, ProductBasic is also fetched in a different query. BUT in both these cases, ProductBasic is fetched always (non-lazy).. How can i fetch ProductBasic in a Non-Lazy manner in this case. -- 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, 7 months

4
5
0 / 0

[Hibernate-JIRA] Created: (ANN-822) org.hibernate.test.annotations.EntityTest fails because DB2 does not support unique constraints on nullable columns

by Gail Badner (JIRA)

org.hibernate.test.annotations.EntityTest fails because DB2 does not support unique constraints on nullable columns ------------------------------------------------------------------------------------------------------------------- Key: ANN-822 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-822 Project: Hibernate Annotations Issue Type: Bug Reporter: Gail Badner The following org.hibernate.test.annotations.EntityTest tests fail on DB2: testColumnUnique() testUniqueConstraint() DB2 does not support unique constraints on nullable columns. DB2 does support unique indexes on nullable columns, but only be 1 null value is allowed. (DB2 for z/OS does appear to allow multiple null values; is that a different dialect?) When DB2Dialect is used, Hibernate does not create unique constraints or indexes on nullable columns. This is why the expected constraint violations do not occur in the tests. The tests give an erroneous message "org.hibernate.TransactionException: Transaction not successfully started" because an attempt is made to rollback the transaction after it was successfully committed. -- 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, 7 months

4
8
0 / 0

[Hibernate-JIRA] Created: (HHH-2988) UnionSubclassEntityPersister.generateSubquery() does not use column.getQuotedName()

by benoit heinrich (JIRA)

UnionSubclassEntityPersister.generateSubquery() does not use column.getQuotedName() ----------------------------------------------------------------------------------- Key: HHH-2988 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2988 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Reporter: benoit heinrich Priority: Critical Hi all, I'm new to hibernate and I'm trying to use the Inheritance strategy TABLE_PER_CLASS with a Postgres database. The postgres database contains tables and column with upper cases names (names must be quoted). In the entity I used the back-quote ` sign to quote the table names and column names. All basic requests work but when I have an association going to the virtual parent table then I got an error due to the fact that the Union subclass entity persister does not quote the column names inside the sub query. I've locate the problem and I think it occurs here: org.hibernate.persister.entity.UnionSubclassEntityPersister.java (svn rev. 11398) line 395 ------------------------------------------------------------------------------------------------ while ( citer.hasNext() ) { Column col = (Column) citer.next(); if ( !table.containsColumn(col) ) { int sqlType = col.getSqlTypeCode(mapping); buf.append( dialect.getSelectClauseNullString(sqlType) ) .append(" as "); } buf.append( col.getName() ); buf.append(", "); But should be ------------------------------------------------------------------------------------------------ buf.append( col.getQuotedName() ); Here is an example to test: Item.java: --------------------------------- @Entity @Inheritance(strategy = InheritanceType.TABLE_PER_CLASS) public abstract class Item implements java.io.Serializable { private long id; private Container parent; /** getter / setter */ @Id @Column(name = "`ID`", unique = true, nullable = false, insertable = true, updatable = true) @GeneratedValue(strategy=GenerationType.SEQUENCE, generator = "item_id_seq_generator") @SequenceGenerator(name="item_id_seq_generator", sequenceName="item_id_seq", allocationSize=1) public long getId() { return this.id; } public void setId(long id) { this.id = id; } @ManyToOne(cascade = {}, fetch = FetchType.LAZY) @JoinColumn(name = "`ParentID`", unique = false, nullable = true, insertable = true, updatable = true) public Container getParent() { return this.parent; } public void setParent(Container parent) { this.parent = parent; } } Container.java --------------------------------- @Entity @Table(name = "`CoNTaiNeR`") public class Container extends Item { private Set<Item> items = new HashSet<Item>(0); @OneToMany(cascade = { CascadeType.ALL }, fetch = FetchType.LAZY, mappedBy = "parent", targetEntity = Item.class) public Set<Item> getItems() { return this.items; } public void setItems(Set<Item> items) { this.items = items; } } SimpleItem.java --------------------------------- @Entity @Table(name = "`SimpleItem`") public class SimpleItem extends Item { /*...*/ } So when you try to get the Container.getItems() then it generates the wrong query. Cheers, /Benoit -- 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, 7 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-218) add indexAll( Class type ) to rebuild indexes from all data

by Sanne Grinovero (JIRA)

add indexAll( Class type ) to rebuild indexes from all data ----------------------------------------------------------- Key: HSEARCH-218 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-218 Project: Hibernate Search Issue Type: New Feature Reporter: Sanne Grinovero Assignee: Sanne Grinovero The implementation should be as efficient as possible, to cover this scenarios: * Developers change an entity and want to test the effect on the index structure, they want do to search experiments with the new fields. * A production system is up(down)graded to a new(old) release, involving index changes. (the system is "down for maintenance" but the speed is crucial) * Existing index is corrupted/lost. (Again, speed to recover is critical) * A Database backup is restored, or data is changed by other jobs. * Some crazy developer like me prefers to disable H.Search's event listeners for some reason. (I wouldn't generally recommend it, but have met other people who have a reasonable argument to do this) * A Lucene update breaks the index format (not so irrationale as they just did on trunk). -- 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, 7 months

3
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3206) criteria.uniqueResult() is null when criteria.firstResult is NOT null when projection is count

by Will Hoover (JIRA)

criteria.uniqueResult() is null when criteria.firstResult is NOT null when projection is count ---------------------------------------------------------------------------------------------- Key: HHH-3206 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3206 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.5 Environment: JBoss 4.0/JDK 1.6/Oracle 10g Reporter: Will Hoover Priority: Minor SYNOPSIS: "criteria.uniqueResult()" is null when criteria.firstResult is NOT null when projection is count. This happens regardless if using "criteria.setProjection(Projections.countDistinct(distinctPropertyName));" or "criteria.setProjection(Projections.rowCount())". The reason why the criterias firstResult is not null is because we are reusing the same criteria to perform "criteria.list()" as "criteria.uniqueResult()" to avoid having to set all of the same restrictions etc. twice. -- 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, 7 months

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-572) @Node(name=, embedXml=true|false) for DOM4J

by Emmanuel Bernard (JIRA)

@Node(name=, embedXml=true|false) for DOM4J ------------------------------------------- Key: ANN-572 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-572 Project: Hibernate Annotations Type: Improvement Components: binder Reporter: Emmanuel Bernard -- 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, 7 months

7
18
0 / 0

[Hibernate-JIRA] Created: (ANN-684) Query with an IN Clause object that holds an Enum is failing with ORA-01722: invalid number (Criteria) OR ORA-17041: Missing IN or OUT parameter at index (HQL)

by Li Ho (JIRA)

Query with an IN Clause object that holds an Enum is failing with ORA-01722: invalid number (Criteria) OR ORA-17041: Missing IN or OUT parameter at index (HQL) --------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: ANN-684 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-684 Project: Hibernate Annotations Issue Type: Bug Components: search Affects Versions: 3.2.0.ga Environment: Hibernate 3.2.0 (cr4) Oracle Annotations Reporter: Li Ho I am trying to do a query with an IN clause. The object I am passing into the IN clause contains an Enum. I'm not 100% sure, but I think the Enum is causing the problem based on the resulting error message. When I use the Criteria API, I get the following error: ORA-01722: invalid number When I use the equivalent HQL, I get: ORA-17041: Missing IN or OUT parameter at index Here is some code (using criteria) that produces the error List<AccountKey> accountKeys; // AccountKey contains some Strings and an Enum ... List results = session.createCriteria(MyObject.class). add(Expression.in("key.account.key", accountKeys)). list(); The debug SQL looks right... and when I manually try it by replacing the ? params with valid values, it works! So, it seems like there's a problem with the passing of the query parameter values. I am currently working around this issue by bypassing the object comparison. I extract the variables I want to compare and force it to do a direct String comparison on those elements. -- 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, 7 months

3
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-74) Make sure Validator<T> is thread-safe in the RI

by Emmanuel Bernard (JIRA)

Make sure Validator<T> is thread-safe in the RI ----------------------------------------------- Key: BVAL-74 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-74 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard Fix For: 1.0 public draft -- 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, 7 months

2
2
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 May 2009