August 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3873) DB2Dialect.getLimitString raise DB2 error message when called with limit=0

by Julien Kronegg (JIRA)

DB2Dialect.getLimitString raise DB2 error message when called with limit=0 -------------------------------------------------------------------------- Key: HHH-3873 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3873 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: DB2, http://viewvc.jboss.org/cgi-bin/viewvc.cgi/hibernate/core/branches/Branch... http://viewvc.jboss.org/cgi-bin/viewvc.cgi/hibernate/core/branches/Branch... Reporter: Julien Kronegg Priority: Minor Executing a query called with setMaxResults(n) makes the underlying Hibernate code to call DB2Dialect.getLimitString. While this is working fine in general case, the following database error is raised when setting the maximum number of results to zero: SqlException: NUMBER 0 DIRECTLY SPECIFIED IN AN SQL STATEMENT IS OUTSIDE THE RANGE OF ALLOWABLE VALUES IN THIS CONTEXT (1, 2147483647) This is due to the getLimitString method in classes DB2400Dialect and DB2390Dialect : public String getLimitString(String sql, int offset, int limit) { return new StringBuffer(sql.length() + 40) .append(sql) .append(" fetch first ") .append(limit) .append(" rows only ") .toString(); } When the limit parameter is set to zero, the fetch limit is appended, which explains why the error message occur. Solution: ------------ When the limit is 0, there should be no "fetch first" instruction appended (as 0 is the general convention for "no limit"). The code would be: public String getLimitString(String sql, int offset, int limit) { + if (limit==0) return sql; return new StringBuffer(sql.length() + 40) .append(sql) .append(" fetch first ") .append(limit) .append(" rows only ") .toString(); } Workaround: ------------------ In order to avoid the error message, getLimitString(n) or setMaxResults(n) should be called with the 'newN' argument: int newN = (n==0?Integer.MAX_VALUE:n); Note: since the workaround is quite easy, I set the priority to "Minor" -- 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

14 years, 2 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HHH-3144) Final methods preclude some useful Hibernate extensions

by Ali Ibrahim (JIRA)

Final methods preclude some useful Hibernate extensions ------------------------------------------------------- Key: HHH-3144 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3144 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6 Reporter: Ali Ibrahim Priority: Minor The following methods are final: AbstractPersistentCollection#read, AbstractPersistentCollection#write, AbstractLazyInitializer#initialize. It can be useful to override these methods. Fix is to make them protected. -- 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

14 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4074) Polymorphic queries avoid with polymorphism="explicit" in hbm.xml file doesn't work

by Radics Laszlo (JIRA)

Polymorphic queries avoid with polymorphism="explicit" in hbm.xml file doesn't work ----------------------------------------------------------------------------------- Key: HHH-4074 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4074 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: hibernate 3.3.2 Oracle 9i Reporter: Radics Laszlo hbm.xml: <hibernate-mapping default-cascade="none"> <class name="hu.raiffeisen.aps.soa.entity.collateral.AncestorImpl" table="ANCESTOR" dynamic-insert="false" dynamic-update="false" polymorphism="explicit"> <id name="id" type="java.lang.Long" unsaved-value="null"> <column name="ID" sql-type="NUMBER(19)"/> <generator class="sequence"> <param name="sequence">ANCESTOR_SEQ</param> </generator> </id> <property name="top" type="java.lang.Long"> <column name="TOP" not-null="true" unique="false" sql-type="NUMBER(19)"/> </property> <union-subclass name="hu.raiffeisen.aps.soa.entity.collateral.DescendantImpl" table="DESCENDANT" dynamic-insert="false" dynamic-update="false" abstract="false"> <property name="bottom" type="java.lang.Long"> <column name="BOTTOM" not-null="true" unique="false" sql-type="NUMBER(19)"/> </property> </union-subclass> </class> </hibernate-mapping> hql: "from AncestorImpl" fetch both ancestor and descendant rows -- 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

14 years, 2 months

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-470) enrich UniqueConstraint with property name

by Johnny D. (JIRA)

enrich UniqueConstraint with property name ------------------------------------------ Key: ANN-470 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-470 Project: Hibernate Annotations Type: Improvement Reporter: Johnny D. To be able in annotation to give uniqueConstraint exact database name, there is need to add field java.lang.String name(); to annotation class UniqueConstraint in similar way like in index is. -- 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

14 years, 2 months

5
10
0 / 0

[Hibernate-JIRA] Created: (HHH-4042) StatelessSession does not flush when using jdbc batch_size > 1

by Gael Beaudoin (JIRA)

StatelessSession does not flush when using jdbc batch_size > 1 -------------------------------------------------------------- Key: HHH-4042 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4042 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.1 Environment: JBoss 4.2.3, Linux, java 1.6, hibernate 3.3.1, entityManager 3.4.0, jboss seam 2.1.2, postgresql 8.3 Reporter: Gael Beaudoin I'm using a StetelessSession to insert millions of rows : it works great and without using much memory. But I've just seen that with a jdbc batch size of 50 for example (<property name="hibernate.jdbc.batch_size" value="0"/> in my persistence.xml) the last round of inserts aren't flushed to the database. For example, with 70 insert, only the first 50 are sent to the database. I've searched a lot about this issues and on this thread (https://forum.hibernate.org/viewtopic.php?f=1&t=987882&start=0), the only solution found is to set the batch_size to 1, which is really a shame. I've tried to flush the session, close the jdbc connection, etc etc ... no luck. I'd be fine with a way to set the batch_size to 1 only for this method, pro grammatically, but I've not found any way to do that. If you don't pay attention, it's a easy way to lose data. -- 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

14 years, 2 months

5
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2319) StatelessInterceptor

by Max Rydahl Andersen (JIRA)

StatelessInterceptor -------------------- Key: HHH-2319 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2319 Project: Hibernate3 Type: New Feature Components: core Versions: 3.2.1 Reporter: Max Rydahl Andersen It would make sense to have an Interceptor for StatelessSession to solve the following usecases: Log/adjust SQL: onPrepareStatement Proper entityname handling: instantiate/getEntity Maybe also tx interaction: afterTransationBegin/beforeTransactionCompletion/afterTransactionCompletion Technically it could be solved by just allowing to pass in a normal interceptor to a StatelessSession and just document that the state oriented callbacks will not be called. Alternatively we can create a StatelessInterceptor that only implement the releavant methods and wrap that instance into an internal Interceptor. -- 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

14 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2007) Hibernate doesn't support optional one-to-one associations

by Andrei Iltchenko (JIRA)

Hibernate doesn't support optional one-to-one associations ---------------------------------------------------------- Key: HHH-2007 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2007 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.0.cr2 Reporter: Andrei Iltchenko Hibernate doesn't properly support optional one-to-one associations, e.g. Person (0..1) -- (0..1) Passport. The Hibernate books and reference all talk of two ways of mapping one-to-one associations: 1. using a many-to-one fk association with a unique constraint on the fk; 2. using a pk association. the trouble with both of them is that they enforce the mandatory property of an association end, which sometimes is not desirable. The first way enforces the mandatory property with the uniqueness constraint on the fk, the other by using the fact that one table's pk is its fk. I tried to see if I could adapt the 1st way of representing one-to-ones to support optional association ends. What I did was simply remove the unique and not null constrains from DDL generated (without removing it it would be impossible to have a Person record that doesn't reference a Passport record): from CREATE TABLE Person ( PassUniqueId VARCHAR (32) NOT NULL, version INTEGER NOT NULL, uniqueId VARCHAR (32) NOT NULL, name VARCHAR (40) NULL, PRIMARY KEY (uniqueId), UNIQUE(PassUniqueId), FOREIGN KEY (PassUniqueId) REFERENCES Passport (uniqueId) ); to CREATE TABLE Person ( PassUniqueId VARCHAR (32) NULL, version INTEGER NOT NULL, uniqueId VARCHAR (32) NOT NULL, name VARCHAR (40) NULL, PRIMARY KEY (uniqueId), FOREIGN KEY (PassUniqueId) REFERENCES Passport (uniqueId) ); but leave the uniqueness attribute in the mapping file: <many-to-one name="pass" class="application.business.logic.Passport" cascade="save-update,merge" unique="true" > <column name="PassUniqueId"/> </many-to-one> The resulting solution worked fine and I was able to create instances of Person not linked to a Passport. However Hibernate didn't succed in keeping the association from degrading into a many-to-one. It enabled me to create two Persons linked with the same Passport: PASSUNIQUEID | VIRSION | UNIQUEID | Name ================================================ 0d8b3919fffff | 1 | 0d5fb1dcfff | John 0d8b3919fffff | 0 | 10fd07bdfff | Sam A subsequent attempt at retrieving such Persons with Hibernate failed: org.hibernate.HibernateException: More than one row with the given identifier was found: 0d8b3919ffffffd60151e135b6da0164, for class: application.business.logic.Passport. Hibernate should be able to impose the single end property of such associations without relying on the underlying RDBMS engine and never allow them to degrade to many-to-ones. -- 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

14 years, 2 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-24) Improve the default message of InvalidStateException

by Mike Quilleash (JIRA)

Improve the default message of InvalidStateException ---------------------------------------------------- Key: HV-24 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-24 Project: Hibernate Validator Issue Type: Improvement Components: engine Affects Versions: 3.0.0.ga Environment: Any Reporter: Mike Quilleash Doing a printStackTrace on InvalidStateException does not give the actual invalid values anywhere. Would greatly improving debugging speed if this was included by default as often this indicates a programming error. Currently I have to run the code again and debug the right place to find out what the InvalidValues are. -- 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

14 years, 2 months

7
14
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-371) Refactor DocumentBuilder and introduce abstract base class

by Hardy Ferentschik (JIRA)

Refactor DocumentBuilder and introduce abstract base class ---------------------------------------------------------- Key: HSEARCH-371 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-371 Project: Hibernate Search Issue Type: Task Components: engine Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.2.0 Further improvement of the document builder. Introducing a common base class and moving some methods into there and taking care of some not so nice method overriding between the two existing DocumentBuilders will further improve the design of these classes. -- 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

14 years, 3 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4072) ManyToMany with single table inheritance fails when multiple subclasses

by david sinclair (JIRA)

ManyToMany with single table inheritance fails when multiple subclasses ----------------------------------------------------------------------- Key: HHH-4072 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4072 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.3.2 Environment: Windows XP, Java 1.6 Reporter: david sinclair Priority: Critical I have a base entity named BusinessSoftwareMatrixElement declare as such @Entity @Inheritance(strategy = InheritanceType.SINGLE_TABLE) @DiscriminatorColumn(name = "software_type", discriminatorType = DiscriminatorType.STRING) @DiscriminatorValue("Software") @Audited BusinessSoftwareMatrixElement ...{ } I then have a subclass of BusinessSoftwareMatrixElement that is a mapped super class which defines a many to many relationship. @MappedSuperclass @Audited public abstract class BusinessOSProcessServiceMatrixElement extends BusinessSoftwareMatrixElement { private Set<BusinessOSMatrixElement> applicableOperatingSystems = new HashSet<BusinessOSMatrixElement>(); @ManyToMany(fetch = FetchType.LAZY, cascade = {CascadeType.REMOVE, CascadeType.REFRESH }, targetEntity = BusinessOSMatrixElement.class) @JoinTable(name="matrix_elements_procserv_aos", joinColumns=@JoinColumn(name="sw_guid"), inverseJoinColumns = @JoinColumn(name="os_guid")) public Set<BusinessOSMatrixElement> getApplicableOperatingSystems() { return applicableOperatingSystems; } } There are then to subclasses that add no new fields, only different discriminators @Entity @DiscriminatorValue("Database") @Audited public class BusinessDBMatrixElement extends BusinessOSProcessServiceMatrixElement { @Entity @DiscriminatorValue("Application") @Audited public class BusinessAppMatrixElement extends BusinessOSProcessServiceMatrixElement { Running the ant task to create the DDL results in an exception being thrown for that many to many table. Caused by: org.hibernate.DuplicateMappingException: Duplicate class/entity mapping matrix_elements_procserv_aos_AUD at org.hibernate.tool.ant.HibernateToolTask.reportException(HibernateToolTask.java:226) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:189) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) at org.apache.tools.ant.Task.perform(Task.java:364) at org.apache.tools.ant.Target.execute(Target.java:341) at org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:108) ... 24 more Caused by: org.hibernate.DuplicateMappingException: Duplicate class/entity mapping matrix_elements_procserv_aos_AUD at org.hibernate.cfg.Mappings.addClass(Mappings.java:141) at org.hibernate.cfg.HbmBinder.bindRoot(HbmBinder.java:167) at org.hibernate.cfg.Configuration.add(Configuration.java:716) at org.hibernate.cfg.AnnotationConfiguration.processArtifactsOfType(AnnotationConfiguration.java:531) at org.hibernate.cfg.AnnotationConfiguration.secondPassCompile(AnnotationConfiguration.java:291) at org.hibernate.cfg.Configuration.buildMappings(Configuration.java:1162) at org.hibernate.envers.configuration.AuditConfiguration.getFor(AuditConfiguration.java:102) at org.hibernate.envers.ant.AnnotationConfigurationTaskWithEnvers.doConfiguration(AnnotationConfigurationTaskWithEnvers.java:38) at org.hibernate.tool.ant.ConfigurationTask.getConfiguration(ConfigurationTask.java:55) at org.hibernate.tool.ant.HibernateToolTask.getConfiguration(HibernateToolTask.java:302) at org.hibernate.tool.ant.Hbm2DDLExporterTask.createExporter(Hbm2DDLExporterTask.java:51) at org.hibernate.tool.ant.ExporterTask.execute(ExporterTask.java:39) at org.hibernate.tool.ant.HibernateToolTask.execute(HibernateToolTask.java:186) -- 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

14 years, 3 months

3
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 August 2009