December 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HSEARCH-726) Facetted search on embedded collections takes only first element from collection

by Elmer van Chastelet (JIRA)

Facetted search on embedded collections takes only first element from collection -------------------------------------------------------------------------------- Key: HSEARCH-726 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-726 Project: Hibernate Search Issue Type: Bug Components: query Affects Versions: 3.4.0.CR2, 3.4.0.CR1, 3.4.0.Beta1, 3.4.0.Alpha1 Environment: Any valid config I suppose, tested using Hibernate Core 3.6.3 + Search 3.4.0.CR2, mysql and in Hibernate Search test environment Reporter: Elmer van Chastelet Attachments: EmbeddedCollectionsFacetsTest.zip >From [Hibernate Search Forum: Bug or not? Faceted search + embedded fields (*tomany)|https://forum.hibernate.org/viewtopic.php?f=9&t=1010472&start=0]. Faceted search won't work correctly when used on collections. For the cause I quote Hardy Ferentschik : ??The current faceting implementation utilizes the Lucene FieldCache which has a limitation that each document must have a single value for the specified field.?? I can think of many use cases in which faceted search on collections is really needed, some examples: Facetting on authors when searching for publications Facetting on ingredients when searching for recipes Facetting on actors when searching for movies ... Attached is a hibernate search test case. It fails on retrieving the right amount of matched authors. Currently I don't have the needed insight to suggest an improvement on current implementation to make it compatible with collections. Hopefully it can be achieved with small changes. Good luck :) -- 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

12 years

5
9
0 / 0

[Hibernate-JIRA] Created: (HHH-2776) Restrictons.in(..) generates invalid SQL if list of values is empty

by Adrian Smith (JIRA)

Restrictons.in(..) generates invalid SQL if list of values is empty ------------------------------------------------------------------- Key: HHH-2776 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2776 Project: Hibernate3 Issue Type: Bug Components: query-criteria Affects Versions: 3.2.2 Environment: Hibernate 3.2.2.ga, MySQL 4.1.18, Windows XP Reporter: Adrian Smith I have classes called A and B. There is a 1:n relationship from A to B. Class B has the following in its mapping file: <many-to-one name="a" class="A" column="fk_a_id" not-null="true" /> If I write the following code: List<B> foo() { List<A> aList = .... Session session = .... Criteria query = session.createCriteria(B.class); query.add(Restrictions.in("a", aList)); return query.list(); } Then all works fine and the results I want are returned. However, if aList is empty (i.e. aList.size()==0) then the query.list function generates and executes invalid SQL for MySQL. java.sql.SQLException: Syntax error or access violation message from server: "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')' at line 1" I imagine that it is generating SQL like IN () which isn't valid. I realize it's a bit ridiculous to want to find the rows where a field is IN the empty list. Nothing will ever be returned. However, in my opinion it should still be allowed, and return no rows, just as saying "WHERE 1=2" is allowed, just doesn't return any 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

12 years

6
12
0 / 0

[Hibernate-JIRA] Created: (HCANN-17) SecondaryTable JoinColumn cannot reference a non primary key

by Krashan Brahmanjara (JIRA)

SecondaryTable JoinColumn cannot reference a non primary key ------------------------------------------------------------ Key: HCANN-17 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-17 Project: Hibernate Commons Annotations Issue Type: Bug Affects Versions: 3.1.0.GA Environment: Hibernate libraries added to jboss-6.0.0.20100216-M2(3.5) and jboss-5.1.0.GA(3.3.1) used with postgresql-8.3.7-1 database and jdbc driver postgresql-8.3-603.jdbc4.jar Reporter: Krashan Brahmanjara Hibertate annotations reject correct annotations with an error Full exception org.hibernate.AnnotationException: SecondaryTable JoinColumn cannot reference a non primary key at org.hibernate.cfg.annotations.TableBinder.bindFk(TableBinder.java:243) at org.hibernate.cfg.annotations.EntityBinder.bindJoinToPersistentClass(EntityBinder.java:520) at org.hibernate.cfg.annotations.EntityBinder.createPrimaryColumnsToSecondaryTable(EntityBinder.java:510) at org.hibernate.cfg.annotations.EntityBinder.finalSecondaryTableBinding(EntityBinder.java:441) at org.hibernate.cfg.SecondaryTableSecondPass.doSecondPass(SecondaryTableSecondPass.java:25) Example Three entity, two connected to main 'dokument' by their id columns @Entity @Table(name = "dokument") @SecondaryTables(value = { @SecondaryTable(name = "dokument_status", pkJoinColumns = @PrimaryKeyJoinColumn(name = "id_status", referencedColumnName = "id_status")), @SecondaryTable(name = "typ_dok", pkJoinColumns = @PrimaryKeyJoinColumn(name = "id_type", referencedColumnName = "id_type")) }) public class PosrDokument implements Serializable { @Id @Column(name="id_dokumentu", unique=true, nullable=false) private int id_dokumentu; @Column(name = "status", table = "dokument_status", nullable = false, insertable = false, updatable = false) private String status; @Column(name = "name", table = "typ_dok", nullable = false, insertable = false, updatable = false) private String name; (...) -- 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

12 years

6
7
0 / 0

[Hibernate-JIRA] Created: (HHH-2831) Native SQL queries with addJoin or <return-join/> return object arrays instead of single Entities

by Jeremy Grodberg (JIRA)

Native SQL queries with addJoin or <return-join/> return object arrays instead of single Entities ------------------------------------------------------------------------------------------------- Key: HHH-2831 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2831 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.5, 3.2.4 Environment: Hibernate 3.2.4.ga and 3.2.5.ga with hsqldb on Win XP Reporter: Jeremy Grodberg Attachments: NativeSQLQueriesTest.patch Although the documentation is not crystal clear, I read it to say that using addJoin should eagerly fetch an associated object but should NOT return it as a separate value. In section 16.1.3. "Handling associations and collections" of the online documentation it says: "It is possible to eagerly join in the Dog to avoid the possible extra roundtrip for initializing the proxy. This is done via the addJoin() method, which allows you to join in an association or collection." This comes BEFORE the section on returning multiple entities, so I say the documentation at least implies it will only return a single entity at the top level. Also, if the intention is to return multiple entities, addEntity() works fine for that, so what then would be the difference of addJoin()? If I'm wrong about what addJoin() should do, please clarify that in the documentation and also clarify how, if it is possible, one could eagerly fetch the association without changing the return type of the quer y. I have reproduced this problem in the Hibernate JUnit tests in 3.2.4.ga and 3.2.5.ga, specifically NativeSQLQueriesTest.testSQLQueryInterface(). I'm attaching a patch to the Hibernate junit test org.hibernate.test.sql.hand.query.NativeSQLQueriesTest.java released in 3.2.5.ga that adds a test to ensure that a query with addJoin only returns a (list of) entities, not a list of Object arrays containing entities. Currently, the assertion fails because instead of returning a list of Organizations we get a list of Object[3] = { Organization, Employment, Person }, which is exactly what we get when the addJoin()s are replaced with appropriate addEntity() calls. -- 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

12 years

14
15
0 / 0

[Hibernate-JIRA] Created: (HHH-6551) HBM XML does not process subclasses within <subclass> tags

by Gail Badner (JIRA)

HBM XML does not process subclasses within <subclass> tags ---------------------------------------------------------- Key: HHH-6551 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6551 Project: Hibernate Core Issue Type: Bug Components: metamodel Reporter: Gail Badner Assignee: Steve Ebersole Fix For: 4.0.0.next In the following, PartTimeEmployee is not processed because it is embedded within Employee: <subclass name="Employee" discriminator-value="E"> <property name="title" length="20"/> <property name="salary" /> <subclass name="PartTimeEmployee" discriminator-value="M"> <property name="percent"/> </subclass> </subclass> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years

3
4
0 / 0

[Hibernate-JIRA] Created: (BVAL-198) Simplify creation of ConstraintViolationExceptions

by Gunnar Morling (JIRA)

Simplify creation of ConstraintViolationExceptions -------------------------------------------------- Key: BVAL-198 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-198 Project: Bean Validation Issue Type: Improvement Components: spec-general Affects Versions: 1.1 Reporter: Gunnar Morling javax.validation.ConstraintViolationException wraps a set of constraint violations, currently in the following form: Set<ConstraintViolation<?>> constraintViolations As the exception's constructors have a parameter of the same type, instantiating it is not as easy as expected: Validator validator = ...; DomainObject domainObject = new DomainObject(); Set<ConstraintViolation<DomainObject>> constraintViolations = validator.validate(domainObject); //compiler error: ("The constructor ConstraintViolationException(Set<ConstraintViolation<DomainObject>>) is undefined") throw new ConstraintViolationException(constraintViolations); //this works throw new ConstraintViolationException(new HashSet<ConstraintViolation<?>>(constraintViolations)); This problem can be solved by changing the collection type to Set<? extends ConstraintViolation<?>> The exception then would read as follows: public class ConstraintViolationException extends ValidationException { private final Set<? extends ConstraintViolation<?>> constraintViolations; public ConstraintViolationException(String message, Set<? extends ConstraintViolation<?>> constraintViolations) { super( message ); this.constraintViolations = constraintViolations; } public ConstraintViolationException(Set<? extends ConstraintViolation<?>> constraintViolations) { super(); this.constraintViolations = constraintViolations; } public Set<ConstraintViolation<?>> getConstraintViolations() { return new HashSet<ConstraintViolation<?>>(constraintViolations); } } This makes the exception easier to use for producers, while maintaining simplicity for clients (since getConstraintViolations() still returns a Set<ConstraintViolation<?>>, clients don't have to do deal with the bound wildcard expression). -- 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

12 years

3
10
0 / 0

[Hibernate-JIRA] Created: (HHH-6127) Wrong save or read unicode value on @Lob String field in PostgreSQL 8.4

by Mihail Slobodyanuk (JIRA)

Wrong save or read unicode value on @Lob String field in PostgreSQL 8.4 ----------------------------------------------------------------------- Key: HHH-6127 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6127 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.6.3 Environment: PostgreSQL 8.4.5 on Ubuntu 32, Hibernate 3.6.0 - 3.6.3, jdbc driver: postgresql-8.3-603.jdbc3 Reporter: Mihail Slobodyanuk Priority: Critical <hibernate-configuration> <session-factory> <property name="hibernate.connection.driver_class">org.postgresql.Driver</property> <property name="hibernate.connection.url">jdbc:postgresql://localhost/test</property> <property name="hibernate.dialect">org.hibernate.dialect.PostgreSQLDialect</property> <property name="hibernate.connection.username">postgres</property> <property name="hibernate.connection.password">postgres</property> <property name="hbm2ddl.auto">update</property> <property name="hibernate.connection.charSet">UTF-8</property> <property name="hibernate.show_sql">true</property> <property name="hibernate.current_session_context_class">thread</property> </session-factory> </hibernate-configuration> @Entity public class ReportTemplate{ @Id @GeneratedValue private Integer id; @Lob private String body; ... } At save (or at read) operation with 'body' field value is broken. In DB stored Blob's OID. The next code throw AssertionError: String str="Русский текст";//Unicode string rt = new ReportTemplate(); rt.setBody(str); Serializable id = hsm.getSession().save(rt); hsm.commit(); hsm.getSession().clear(); rt = (ReportTemplate) hsm.getSession().get(ReportTemplate.class, id); assert str.equals(rt.getBody()); -- 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

12 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6075) registerVarcharTypes in MySQL5Dialect creates varchar for up to a length of 65535

by Thomas Einwaller (JIRA)

registerVarcharTypes in MySQL5Dialect creates varchar for up to a length of 65535 ---------------------------------------------------------------------------------- Key: HHH-6075 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6075 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.0.SP1 Environment: MySQL 5.1.52 Reporter: Thomas Einwaller while the registerVarcharTypes in the MySQLDialect only creates varchar columns with a length up to 255 seems like a regression caused by this commit: https://github.com/hibernate/hibernate-core/commit/d8d6d82e30960e0c255950... MySQL throws the following error: Error Code: 1118 Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs when trying to create a table with 3 varchar (20000) colums -- 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

12 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3606) Can't use distinct in Oracle with BLOB/CLOB column

by Julien HENRY (JIRA)

Can't use distinct in Oracle with BLOB/CLOB column -------------------------------------------------- Key: HHH-3606 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3606 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.2.6 Environment: Oracle 9i Reporter: Julien HENRY Problem: Oracle doesn't support distinct when a row is BLOB/CLOB. The resulting error is: ORA-00932: inconsistent datatypes: expected - got CLOB I got this error when trying to filter root entity (see FAQ: http://www.hibernate.org/117.html#A12). It is not really an Hibernate bug, much likely an Oracle limitation. But perhaps an entry may be added in the FAQ, or perhaps some workaround may be found to not use SQL distinct keyword when a BLOB/CLOB is involved in the query. Some related links: http://drupal.org/node/48435 (FR) http://www.developpez.net/forums/d553106/java/general-java/persistance/hi... http://www.dbasupport.com/forums/showthread.php?t=46785 (possible rewriting of the query) -- 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

12 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2969) DB2Dialect Clob SchemaExport uses default length even if no length set

by Philippe Mouawad (JIRA)

DB2Dialect Clob SchemaExport uses default length even if no length set ---------------------------------------------------------------------- Key: HHH-2969 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2969 Project: Hibernate3 Issue Type: Bug Components: core Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, DB2 8, DB2 9 Reporter: Philippe Mouawad Attachments: db2-clob-schemaExport-patch.txt I have this property in my mapping: <property name="argumentsValues" column="cte_arguments_values" type="text" not-null="true" /> Notice no length is set. Hibernate schema Export generates: cte_arguments_names clob(255) not null, Same problem occurs for Clob and Blob. This is due to the following lines in org.hibernate.dialect.DB2Dialect: registerColumnType( Types.BLOB, "blob($l)" ); registerColumnType( Types.CLOB, "clob($l)" ); Attached is the patch. There would be another solution to test that Column has no length set. Philippe. www.ubik-ingenierie.com -- 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

12 years

3
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2011