July 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-77) Expose configuration settings through API

by Christian Bauer (JIRA)

Expose configuration settings through API ----------------------------------------- Key: HSEARCH-77 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-77 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Christian Bauer Priority: Minor I'd like to access my configuration settings, probably on a SearchFactory. I want to be able to e.g. get the hibernate.search.worker.batch_size to adjust my loops dynamically. I imagine there are a few other usecases, for example, avoid hardcoding the analyzer for hit highlighting but using the same as the HSearch indexer. -- 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, 2 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-75) Use FieldSelector to filter returned Fields

by Emmanuel Bernard (JIRA)

Use FieldSelector to filter returned Fields ------------------------------------------- Key: HSEARCH-75 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-75 Project: Hibernate Search Issue Type: Improvement Components: engine Reporter: Emmanuel Bernard Priority: Minor Might be useful for projections, but is most likely unnecessary. -- 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, 2 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2254) A query validation bug produces QueryException: "Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.id.parent = ?]"

by Hernan Liendo (JIRA)

A query validation bug produces QueryException: "Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.id.parent = ?]" ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ Key: HHH-2254 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2254 Project: Hibernate3 Type: Bug Components: query-hql Versions: 3.2.0.ga Environment: Hibernate 3.2 using Sybase. However this is not an environment caused problem. It's supposed to happen in every environment. Reporter: Hernan Liendo -- Short description ============================================================================ -- A query validation bug produces QueryException: "Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.id.parent = ?]. Both Parent and Child use composite keys. -- Context ====================================================================================== -- Having composite keys for a Parent class and a Child class, I want to retrieve childs that belong to an specific Parent. -- Parent Definition ============================================================================ -- public class Parent { public ParentId ParentId; ... } public class ParentId { private String idField1; private int idField2; ... } // the parent mapping <hibernate-mapping> <class mutable="false" table="xx" name="Parent"> <composite-id class="ParentId" access="field" name="parentId"> <key-property column="idField1" access="field" name="idField1"/> <key-property column="idField2" access="field" name="idField2"/> </composite-id> </class> </hibernate-mapping> -- Child Definition ============================================================================ -- public class Child { public ChildId childId; ... } public class ChildId { public Parent parent; public String aditionalIdField; ... } // the mapping <hibernate-mapping> <class mutable="false" table="yyy" name="Child"> <composite-id class="ChildId" access="field" name="childId"> <key-many-to-one name="parent" class="Parent" access="field"> <column name="idField1" not-null="true" /> <column name="idField2" not-null="true" /> </key-many-to-one> <key-property column="aditionalIdField" access="field" name="aditionalIdField"/> </composite-id> </class> </hibernate-mapping> -- HQL Statement ============================================================================ -- from Child this where this.childId.parent = ? or from Child this where this.id.parent = ? // using aliased id -- The Exception ============================================================================ -- org.hibernate.QueryException: Expected positional parameter count: 1, actual parameters: [Parent@bec357b] [from Child this where this.childId.parent = ?] at org.hibernate.impl.AbstractQueryImpl.verifyParameters(AbstractQueryImpl.java:319) at org.hibernate.impl.AbstractQueryImpl.verifyParameters(AbstractQueryImpl.java:275) at org.hibernate.impl.QueryImpl.list(QueryImpl.java:75) ... -- The Problem ============================================================================ -- class: org.hibernate.impl.AbstractQueryImpl method: protected void verifyParameters(boolean reserveFirstParameter) throws HibernateException line: 286 The method validates parameters. It resolves the "positionalValueSpan" variable witch in my case gets the value of 2 (One for parent's idField1 and the other for parent's idField2). The method compares positionalValueSpan (2) with parameterMetadata.getOrdinalParameterCount() witch it is 1 (the quantity of "?" signs in the HQL statement". This bug only happens when: 1. composed keys are used (and) 2. having a parent-child relationship (and) 3. resolving children from certain parent. -- Hibernate user workaround ============================================================================ -- Not to use a parent instance variable in the Child class. Hope this helps. If you guys need the source code in order to check the bug, please let me know it. Good luck! Hernan -- 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, 3 months

4
6
0 / 0

[Hibernate-JIRA] Created: (EJB-287) Upload 3.3.1.GA to the Maven repository

by Aleksei Valikov (JIRA)

Upload 3.3.1.GA to the Maven repository --------------------------------------- Key: EJB-287 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-287 Project: Hibernate Entity Manager Issue Type: Improvement Components: EntityManager Affects Versions: 3.3.1.GA Reporter: Aleksei Valikov Priority: Minor Attachments: hibernate-entitymanager-3.3.1.ga.pom Would you please upload the entity manager as well as dependent artifacts to the Maven repository? This is quite important for Maven builds. Dependent artifacts are: hibernate-commons-annotations (3.0.0.ga) hibernate-validator (3.0.0.ga) jboss-archive-browsing (2.0.2.alpha) Below are the commands I used to deploy these artifacts, I hope this helps. I also attach the POM file for the entity manager. I hope you could reuse it in further versions. Thank you! mvn deploy:deploy-file -DgroupId=org.hibernate -DartifactId=hibernate-entitymanager -Dversion=3.3.1.ga -Dpackaging=jar -Dfile=hibernate-entitymanager-3.3.1.ga.jar -DpomFile=hibernate-entitymanager-3.3.1.ga.pom -Durl=file://C:/Projects/p2.external/maven2-repository/www/repository mvn deploy:deploy-file -DgroupId=org.hibernate -DartifactId=hibernate-commons-annotations -Dversion=3.0.0.ga -Dpackaging=jar -Dfile=hibernate-commons-annotations-3.0.0.ga.jar -Durl=file://C:/Projects/p2.external/maven2-repository/www/repository mvn deploy:deploy-file -DgroupId=org.hibernate -DartifactId=hibernate-validator -Dversion=3.0.0.ga -Dpackaging=jar -Dfile=hibernate-validator-3.0.0.ga.jar -Durl=file://C:/Projects/p2.external/maven2-repository/www/repository mvn deploy:deploy-file -DgroupId=jboss -DartifactId=jboss-archive-browsing -Dversion=2.0.2.alpha -Dpackaging=jar -Dfile=jboss-archive-browsing-2.0.2.alpha.jar -Durl=file://C:/Projects/p2.external/maven2-repository/www/repository -- 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, 3 months

4
10
0 / 0

[Hibernate-JIRA] Created: (EJB-279) Entity Listener defined in orm.xml does not work

by Gary Ip (JIRA)

Entity Listener defined in orm.xml does not work ------------------------------------------------ Key: EJB-279 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-279 Project: Hibernate Entity Manager Type: Bug Components: EntityManager Versions: 3.3.0.ga Environment: Hibernate core 3.2.2.GA, Hibernate Annotations 3.3.0.GA, Hibernate Entity Manager 3.3.0.GA, Spring 2.0.3, Tomcat 5.5.20, Oracle 9i Reporter: Gary Ip A default Entity Listener defined in orm.xml (this EJB3 deployment descriptor) worked in HEM and HAN 3.2.1 but not 3.3.0 http://forums.hibernate.org/viewtopic.php?t=972352&sid=95588b2c2391806158... -- 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, 3 months

4
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2592) force hibernate to generate use offset qeury when offset is zero

by Amir Pashazadeh (JIRA)

force hibernate to generate use offset qeury when offset is zero ---------------------------------------------------------------- Key: HHH-2592 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2592 Project: Hibernate3 Issue Type: Improvement Components: query-criteria, query-hql, query-sql Affects Versions: 3.2.3 Environment: Hibernate Core 3.2.3 + Hibernate Annotations 3.3.0 JDK 5.0 Oracle 10g r2 Reporter: Amir Pashazadeh Attachments: patch.zip I know this is mostly an Oracle issue, but believe me it is harder to fix it in Oracle! when the offset of a paged query is zero, Hibernate does not append offset part to query, but the result which is returned by oracle without the offset part, and result returned when offset is zero is different. so some records are retrieved in different pages, and some records (which must be in first page) are not retrieved at all. ---- the patch is included. (I've only included Oracle9Dialect which I used) -- 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, 3 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2674) Query using Escape syntax in LIKE expression with PostgresSQL 8.2 results in PSQLException: The column index is out of range

by Shelly McGowan (JIRA)

Query using Escape syntax in LIKE expression with PostgresSQL 8.2 results in PSQLException: The column index is out of range ----------------------------------------------------------------------------------------------------------------------------- Key: HHH-2674 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2674 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.4.sp1 Environment: JBEAP RC6 - 3.2.4.SP1_CP01 Reporter: Shelly McGowan JPQL: createQuery( "select distinct Object(c) FROM Customer c, in(c.aliases) a WHERE a.alias LIKE 'sh\\_ll' escape '\\'") .setMaxResults(NUMOFCUSTOMERS) .getResultList(); HIBERNATE: select distinct customer0_.ID as ID3_, customer0_.NAME as NAME3_, customer0_.country as country3_, customer0_.code as code3_, customer0_.FK6_FOR_CUSTOMER_TABLE as FK5_3_, customer0_.FK5_FOR_CUSTOMER_TABLE as FK6_3_ from CUSTOMER_TABLE customer0_ inner join FKS_ALIAS_CUSTOMER aliases1_ on customer0_.ID=aliases1_.FK_FOR_CUSTOMER_TABLE inner join ALIAS_TABLE alias2_ on aliases1_.FK_FOR_ALIAS_TABLE=alias2_.ID where alias2_.ALIAS like 'sh\_ll' escape '\' limit ? ERROR: javax.persistence.PersistenceException: org.hibernate.exception.DataException: could not execute query . . . Caused by: org.postgresql.util.PSQLException: The column index is out of range: 1, number of columns: 0. at org.postgresql.core.v3.SimpleParameterList.bind(SimpleParameterList.java:52) at org.postgresql.core.v3.SimpleParameterList.setLiteralParameter(SimpleParameterList.java:113) at org.postgresql.jdbc2.AbstractJdbc2Statement.bindLiteral(AbstractJdbc2Statement.java:2106) at org.postgresql.jdbc2.AbstractJdbc2Statement.setInt(AbstractJdbc2Statement.java:1151) at org.hibernate.loader.Loader.bindLimitParameters(Loader.java:1646) at org.hibernate.loader.Loader.prepareQueryStatement(Loader.java:1566) at org.hibernate.loader.Loader.doQuery(Loader.java:673) at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:236) at org.hibernate.loader.Loader.doList(Loader.java:2220) -- 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, 3 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2586) Hibernate Serializable classes do not declare serialVersionUID

by Manuel Dominguez Sarmiento (JIRA)

Hibernate Serializable classes do not declare serialVersionUID -------------------------------------------------------------- Key: HHH-2586 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2586 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.3, 3.2.2, 3.2.1, 3.2.0.ga, 3.2.0.cr5, 3.2.0.cr4, 3.2.0.cr3, 3.2.0.cr2, 3.2.0 cr1, 3.1.3, 3.2.0.alpha2, 3.2.0.alpha1, 3.1.2, 3.1.1, 3.1, 3.1 rc3, 3.1 rc2, 3.1 rc 1, 3.1 beta 2, 3.1 beta 1, 3.0.5, 3.0.4, 3.0.3, 3.0.2, 3.0.1, 3.0 final, 3.0 rc 1, 3.0 beta 4, 3.0 beta 3, 3.0 beta 2, 3.0 beta 1, 3.0 alpha Environment: Not specific to any database, platform or Hibernate version. Reporter: Manuel Dominguez Sarmiento None of the Serializable classes in Hibernate declare serialVersionUID (see http://www.hibernate.org/hib_docs/v3/api/serialized-form.html#org.hiberna...). This is recommended practice for ALL classes that implement the Serializable interface (see Joshua Bloch's Effective Java - Item #54). Adding these fields is trivial and takes little effort, but is a great enhancement if you are serializing Hibernate classes. For instance, we upgraded from Hibernate 3.2.2 to 3.2.3 in our production servers. We serialize process state (which sometimes includes references to Hibernate-managed entities) every 30 seconds or so and on shutdown, so in the event of failures or re-deployment, the processes can continue where they left off. We had a huge surprise when deserialization failed completely because AbstractPersistentCollection had slightly changed between the 3.2.2 and 3.2.3 releases, and this caused the automatically-generated default serialVersionUID to change, even though the changes in the serialized form are compatible as far as we can tell. -- 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, 3 months

4
5
0 / 0

[Hibernate-JIRA] Created: (HHH-2625) allow DetachedCriteria to work with StatelessSession

by Mario Ivankovits (JIRA)

allow DetachedCriteria to work with StatelessSession ---------------------------------------------------- Key: HHH-2625 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2625 Project: Hibernate3 Issue Type: Improvement Components: query-criteria Affects Versions: 3.2.4.sp1 Reporter: Mario Ivankovits Attachments: DetachedCriteriaWithStatelessSession.diff The attached patch add a new method to DetachedCriteria to make it work with StatelessSession. -- 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, 3 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HBX-729) boolean types mapped to bit in MySQL 5 not working with EJB3 in JBoss 4.0.4.GA

by Daniel Pocock (JIRA)

boolean types mapped to bit in MySQL 5 not working with EJB3 in JBoss 4.0.4.GA ------------------------------------------------------------------------------ Key: HBX-729 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-729 Project: Hibernate Tools Type: Bug Versions: 3.2beta6 Environment: Debian Reporter: Daniel Pocock I define a property with type="boolean" in my .hbm.xml The generated SQL column defaults to bit(1). However, when using JBoss 4.0.4.GA and MySQL 5.0.22, reading the property (getXXX()) always return false If I force hbm2sql to generate a tinyint column, the boolean works as I would have expected: <column name="myColumn" sql-type="tinyint"/> -- 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, 3 months

4
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues July 2007