December 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4450) MapKey with key as entity not working

by shay (JIRA)

MapKey with key as entity not working -------------------------------------- Key: HHH-4450 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4450 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: hibernate annotations 3.4.0 , Hibernate-core 3.3.2 , Postgres 1.8.4 Reporter: shay Priority: Blocker Attachments: testbug.zip when using an entity as key , map is inaccessible(NullPointerException for items) . Its seems that when HashCode is called on the Key , the properties in key have not been populated, which prevents the map from loading properly Test case attached Thank you for your help Shay Matasaro -- 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
2
0 / 0

[Hibernate-JIRA] Commented: (HHH-1599) ConstraintViolationException returns null with PostgresDialect

by Tiago Rinck Caveden (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1599?page=c... ] Tiago Rinck Caveden commented on HHH-1599: ------------------------------------------ Any chances of getting this bug fixed on an official release? Patches have been provided to it years ago, and the bug is still there... > ConstraintViolationException returns null with PostgresDialect > -------------------------------------------------------------- > > Key: HHH-1599 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1599 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1.3 > Environment: Hibernate 3.1.3 , Postgres 8.1.2 (i686), postgresql-8.2dev-501.jdbc.jar > Reporter: Niclas Lindberg > Assignee: Diego Plentz > Priority: Minor > Attachments: HHH-1599.patch, HHH-1599-postgres-only.patch, PostgreSQLDialect.java > > Original Estimate: 0.05h > Remaining Estimate: 0.05h > > ConstraintViolationException.getConstraintName() returns null. The problem is that the message being parsed comes from the SqlException that is the inputparameter to extractConstraintName(SqlException) in ViolatedConstraintNameExtracter. > Solution. The message provided by sqlException.getMessage() is "batch bla bla something" but the correct Exception message to parse is sqlException.getNextException().getMessage() -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-5235) MultipleHiLoPerTableGenerator infers catalogs and schemas where none should be inferred

by Laird Nelson (JIRA)

MultipleHiLoPerTableGenerator infers catalogs and schemas where none should be inferred --------------------------------------------------------------------------------------- Key: HHH-5235 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5235 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.2 Environment: Hibernate 3.5.2-Final, H2 database version 1.2.134 Reporter: Laird Nelson I have a @TableGenerator annotation and an associated @GeneratedValue like this: @Entity(name = "PostalAddress") @TableGenerator( name = "PostalAddressEntityIDGenerator", table = "JPAGenerators", pkColumnName = "generatorName", pkColumnValue = "PostalAddressEntityIDGenerator", valueColumnName = "generatorValue", allocationSize = 1 ) public class PostalAddressEntity { @GeneratedValue(strategy = GenerationType.TABLE, generator = "PostalAddressEntityIDGenerator") @Id private long id; /* etc. */ } At runtime, the following SQL shows up: select generatorValue from JPAGenerators.JPAGenerators.JPAGenerators where generatorName = 'PostalAddressEntityIDGenerator' for update Note the table name repeated three times as though it is both the catalog, the schema and the table name. It seems that the MultipleHiLoPerTableGenerator, when asked to build its SQL strings for various operations, is told that the schema, the catalog and the table name are all the same. I was expecting that the catalog would default to "", per the TableGenerator documentation, and that the schema would default to whatever was present in orm.xml's persistence-unit-defaults element. I can work around this by explicitly spelling out the schema name in my @TableGenerator annotation, but I don't want to put it there (can't, actually). I can also work around this in a JPA-compliant manner by defining my table generator in my orm.xml file, but I don't want to do that either. -- 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
5
0 / 0

[Hibernate-JIRA] Created: (HHH-5817) Passing char[] or byte[] to equal function of CriteriaBuilder throws java.lang.ClassCastException.

by Vyacheslav Dimitrov (JIRA)

Passing char[] or byte[] to equal function of CriteriaBuilder throws java.lang.ClassCastException. -------------------------------------------------------------------------------------------------- Key: HHH-5817 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5817 Project: Hibernate Core Issue Type: Bug Components: entity-manager Affects Versions: 3.6.0 Environment: Hibernate 3.6.0-Finale, derby db, mysql db, hsqldb Reporter: Vyacheslav Dimitrov Priority: Minor Attachments: hibernate_3_6_0.patch We have byte[] field in one of our entity and we want to make query like this. {code} byte[] var = ...; Predicate p = builder.equal(root.get("ourByteField"), var); criteria.where(p); {code} But this code throws exception: [java] Exception in thread "main" java.lang.ClassCastException: [B cannot be cast to [Ljava.lang.Object; [java] at org.hibernate.ejb.AbstractQueryImpl.registerParameterBinding(AbstractQueryImpl.java:349) [java] at org.hibernate.ejb.QueryImpl.setParameter(QueryImpl.java:364) [java] at org.hibernate.ejb.criteria.CriteriaQueryCompiler$1$1.bind(CriteriaQueryCompiler.java:194) [java] at org.hibernate.ejb.criteria.CriteriaQueryCompiler.compile(CriteriaQueryCompiler.java:247) [java] at org.hibernate.ejb.AbstractEntityManagerImpl.createQuery(AbstractEntityManagerImpl.java:441) [java] at ru.petrsu.nest.oqlite.test.TestParser.main(TestParser.java:92) [java] Java Result: 1 because class AbstractQueryImpl has code: {code} ... else if ( value.getClass().isArray() ) { final Object[] array = (Object[]) value; ... {code} We offer to change this "if" like this {code} ... else if ( value.getClass().isArray() && value.getClass().equals(Object[].class)) { final Object[] array = (Object[]) value; ... {code} Due to this new condition we get what we want and our criteria works fine. (At least ClassCastExceptio isn't occured). Patch is attached (Also I can do pull request, if needed). -- 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

4
13
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-707) Expose faceting via annotations

by Hardy Ferentschik (JIRA)

Expose faceting via annotations ------------------------------- Key: HSEARCH-707 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-707 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.4.0.Alpha1 Reporter: Hardy Ferentschik Assignee: Hardy Ferentschik Fix For: 3.4.0.Beta1 -- 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
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-704) Loading objects leads to 1+n queries when JPA's @Id != @DocumentId property

by Emmanuel Bernard (JIRA)

Loading objects leads to 1+n queries when JPA's @Id != @DocumentId property --------------------------------------------------------------------------- Key: HSEARCH-704 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-704 Project: Hibernate Search Issue Type: Improvement Components: query Reporter: Emmanuel Bernard Fix For: 3.4.0 Today we load the objects once using a Criteria query. And to return the object by relevance, we call ObjectLoaderHelper.returnAlreadyLoadedObjectsInCorrectOrder which in the @DocumentId != @Id case, runs one criteria query per object again. That leads to 1+n queries which is not acceptable. To work around that we could (only in the @DocumentId != @Id) case: - run the first criteria query so that it returns a List of tuples { documentIdProperty, entity } - keep this List around - when loading entities ber relevant order, use this list to fetch the data from memory instead of this additional n Criteria queries) -- 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
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-950) Update documentation quick start to point to the latest lib versions (like Hibernate Core 4.0.0.Final

by Emmanuel Bernard (JIRA)

Update documentation quick start to point to the latest lib versions (like Hibernate Core 4.0.0.Final ----------------------------------------------------------------------------------------------------- Key: HSEARCH-950 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-950 Project: Hibernate Search Issue Type: Task Components: documentation Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik Fix For: 4.0 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-942) Accept configuration properties starting with "org." as well

by Sanne Grinovero (JIRA)

Accept configuration properties starting with "org." as well ------------------------------------------------------------ Key: HSEARCH-942 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-942 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Priority: Minor Fix For: 4.1 All configuration properties need to be prefixed with "hibernate.search."; it happens that people mistakenly write "org.hibernate.search." . It would be easy to accept this variant too, and log a warning about it. Or log just a warning if the code gets tricky. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-472) Runtime creation of new shards

by Dobes Vandermeer (JIRA)

Runtime creation of new shards ------------------------------ Key: HSEARCH-472 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-472 Project: Hibernate Search Issue Type: New Feature Components: query Affects Versions: 3.2.0.Beta1 Reporter: Dobes Vandermeer Priority: Minor Hibernate Search's shard support has added the ability to select a shard based on a parameter of the query; however, you must use a fixed number of shards. In order to best support our use case originally reported in http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-470 it would be necessary to add support for dynamically added shards at runtime. Also related: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-251 and http://www.opensubscriber.com/message/hibernate-dev@lists.jboss.org/97703... -- 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
28
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-899) Check for illegal usage of @IndexedEmbedded

by Sanne Grinovero (JIRA)

Check for illegal usage of @IndexedEmbedded ------------------------------------------- Key: HSEARCH-899 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-899 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Priority: Minor Fix For: 4.1 Apparently some people tend to assume that in indexed embedded classes all normal fields should use the @IndexedEmbedded annotation instead of @Field/.. like in: {code} @IndexedEmbedded String countryName {code} Might be nice to check for such unexpected usage, as it's currently silently ignored. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
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 December 2011