February 2008 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-695) Transparent integration of the new Hibernate Search collection event listeners

by Emmanuel Bernard (JIRA)

Transparent integration of the new Hibernate Search collection event listeners ------------------------------------------------------------------------------ Key: ANN-695 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-695 Project: Hibernate Annotations Issue Type: New Feature Components: binder Reporter: Emmanuel Bernard Fix For: 3.3.1 -- 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, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-150) Migrate to Lucene 2.3

by Emmanuel Bernard (JIRA)

Migrate to Lucene 2.3 --------------------- Key: HSEARCH-150 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-150 Project: Hibernate Search Issue Type: New Feature Components: engine Reporter: Emmanuel Bernard Fix For: 3.0.1 -- 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, 10 months

1
1
0 / 0

[Hibernate-JIRA] Created: (EJB-334) Space in path result in error during deployment in JBoss AS

by Emmanuel Bernard (JIRA)

Space in path result in error during deployment in JBoss AS ----------------------------------------------------------- Key: EJB-334 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-334 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.2.Beta3 Reporter: Emmanuel Bernard Fix For: 3.3.2.ga The space issue appears to still be present in the latest release. Using the latest build (EntityManager 3.3.2Beta3, run against JBoss 4.2.0), the relevant portions of the stack trace are: java.lang.RuntimeException: error trying to scan <jar-file>: file:/C:/Program Files/JBoss/lh3_d_jb_420/jboss-as/server/production/tmp/deploy/tmp31846Archive-PerformanceTestDriver.sar-contents/Archive-PerformanceTestData.jar at org.hibernate.ejb.Ejb3Configuration.scanForClasses(Ejb3Configuration.java:616) at org.hibernate.ejb.Ejb3Configuration.configure(Ejb3Configuration.java:359) .... Caused by: java.lang.IllegalArgumentException: Unable to visit JAR file:/C:/Program Files/JBoss/lh3_d_jb_420/jboss-as/server/production/tmp/deploy/tmp31846Archive-PerformanceTestDriver.sar-contents/Archive-PerformanceTestData.jar. Cause: Illegal character in path at index 16: file:/C:/Program Files/JBoss/lh3_d_jb_420/jboss-as/server/production/tmp/deploy/tmp31846Archive-PerformanceTestDriver.sar-contents/Archive-PerformanceTestData.jar at org.hibernate.ejb.packaging.JarVisitorFactory.getVisitor(JarVisitorFactory.java:113) .... Caused by: java.net.URISyntaxException: Illegal character in path at index 16: file:/C:/Program Files/JBoss/lh3_d_jb_420/jboss-as/server/production/tmp/deploy/tmp31846Archive-PerformanceTestDriver.sar-contents/Archive-PerformanceTestData.jar at java.net.URI$Parser.fail(URI.java:2816) at java.net.URI$Parser.checkChars(URI.java:2989) at java.net.URI$Parser.parseHierarchical(URI.java:3073) at java.net.URI$Parser.parse(URI.java:3021) at java.net.URI.<init>(URI.java:578) at java.net.URL.toURI(URL.java:916) at org.hibernate.ejb.packaging.JarVisitorFactory.getVisitor(JarVisitorFactory.java:110) -- 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, 10 months

1
1
0 / 0

[Hibernate-JIRA] Commented: (HHH-1582) PostInsertListener + "post-commit-insert"

by Marco Pozzato (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1582?page=c... ] Marco Pozzato commented on HHH-1582: ------------------------------------ The simpler way, to me, is adding a "success" boolean to Post-*-Event: Would you accept such a patch? Or are there some problem in such a solution? > PostInsertListener + "post-commit-insert" > ----------------------------------------- > > Key: HHH-1582 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1582 > Project: Hibernate3 > Issue Type: Bug > Affects Versions: 3.1.2 > Reporter: Daniel Gredler > Assignee: Emmanuel Bernard > Fix For: 3.3 > > Original Estimate: 3 hours > Remaining Estimate: 3 hours > > I'm using a custom PostInsertEventListener mapped to the "post-commit-insert" event to process domain objects. However, PostInsertEventListener's onPostInsert(PostInsertEvent) is getting called even when the insert was not successful (ie, due to a unique constraint in the database or some such). It looks to me like Hibernate should either a) not invoke the event listener if the insert failed or b) provide state (perhaps in the form of a boolean indicating success/failure). Personally I'd rather the method not be called on failure, but there may be use cases out there for the second option. > As an example, it looks like Hibernate's own LuceneEventListener will add a domain object to the index in onPostInsert(PostInsertEvent) even if the insert failed. > Note that this problem also seems to exist in EntityDeleteAction and EntityUpdateAction (which would mean that Hibernate's LuceneEventListener removes domain objects from the Lucene index even if the delete fails!). -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (ANN-160) Add default name support for @Index

by Anders Wallgren (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-160?page=co... ] Anders Wallgren commented on ANN-160: ------------------------------------- DB2 is even more limiting (18 characters, I think) -- once all the vowels are trimmmed out of the name to make it short enough, it may as well be a hash key ;-) > Add default name support for @Index > ------------------------------------ > > Key: ANN-160 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-160 > Project: Hibernate Annotations > Issue Type: Improvement > Components: binder > Affects Versions: 3.1beta6 > Reporter: Leonardo Quijano > Attachments: Index.patch > > > Currently the "name" parameter for @Index is required. A default naming strategy could be used with @Index annotations, though, allowing the app to pick default names if the parameter is not specified. > For example: > Foo.java { > @Index > public String getSomePropertyValue() > } > This would generate a DB index called "foo_some_property_value_index", for example. Of course, that would depend on the naming strategy. A useful approach would be to use "entity" + "propertyName" + "index_suffix" based on the current NamingStrategy object. > Specifying index names on all required properties is very verbose and could lead to errors. -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1615) GROUP BY entity does not work

by Giampaolo Tomassoni (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1615?page=c... ] Giampaolo Tomassoni commented on HHH-1615: ------------------------------------------ You mean, to fetch each single field with a subselect? Timings are also strongly tied to the number of fields to fetch, then. Right? I don't have an Oracle installation handy. I can only produce timings with PostgreSQL 8.2. Nor I have a suitable companies/products database handy. But I have an Italian provinces/localities database relating 15125 localities (towns) many-to-one with the corresponding province from a set of 104. Timings are this way: Case 1: explode attributes. SELECT p.idlocality, p.code, p.name, COUNT(*) FROM italy.provinces AS p INNER JOIN italy.cities AS c ON c.idprovince=p.idlocality WHERE p.code NOT LIKE '_A' GROUP BY p.idlocality, p.code, p.name HAVING COUNT(*) > 100 ORDER BY p.name ASC Output row count: 69 Total runtime: 36.062 ms Case 2: wrapping dereferencing query SELECT p1.idlocality, p1.code, p1.name, p2.cnt FROM italy.provinces AS p1 RIGHT OUTER JOIN ( SELECT p.idlocality, COUNT(*) AS cnt FROM italy.provinces AS p INNER JOIN italy.cities AS c ON c.idprovince=p.idlocality WHERE p.code NOT LIKE '_A' GROUP BY p.idlocality HAVING COUNT(*) > 100 ) AS p2 ON p1.idlocality=p2.idlocality ORDER BY p1.name ASC Output row count: 69 (of course, the same as case#1) Total runtime: 29.829 ms Now, I believe that in this examples timings differences mostly depend on attribute dereferencing, not on the "core" query. They depend on the count of output rows, then. Hoever, it seems to me that case#2 performs better and that this improvement in performances would be even more evident as the number of output rows increases. Finally, albeit all this performance tests aresomehow related to this issue, I think it would be better to open a thread in some forum. In this way we could even exange test datasets, don't you agree? > GROUP BY entity does not work > ----------------------------- > > Key: HHH-1615 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1615 > Project: Hibernate3 > Issue Type: Improvement > Components: query-hql > Affects Versions: 3.2.5 > Environment: PostgreSQL 8.1.3, Hibernate 3.1.3 > Reporter: Xavier Bugaud > Assignee: Anthony Patricio > Priority: Critical > Attachments: hibernate-group-by.diff > > > The query : "select cat, count(*) from Cat cat group by cat" does not work. > ERROR: column "xxxx" must appear in the GROUP BY clause or be used in an aggregate function > See : > - http://forum.hibernate.org/viewtopic.php?t=953716 > - http://jira.nhibernate.org/browse/NH-528 -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (ANN-160) Add default name support for @Index

by Geoffrey De Smet (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-160?page=co... ] Geoffrey De Smet commented on ANN-160: -------------------------------------- Doing this with the NamingStrategy would be great. Can we rename the issue title to "Support defaulting @Index name in the NamingStrategy"? > Add default name support for @Index > ------------------------------------ > > Key: ANN-160 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-160 > Project: Hibernate Annotations > Issue Type: Improvement > Components: binder > Affects Versions: 3.1beta6 > Reporter: Leonardo Quijano > Attachments: Index.patch > > > Currently the "name" parameter for @Index is required. A default naming strategy could be used with @Index annotations, though, allowing the app to pick default names if the parameter is not specified. > For example: > Foo.java { > @Index > public String getSomePropertyValue() > } > This would generate a DB index called "foo_some_property_value_index", for example. Of course, that would depend on the naming strategy. A useful approach would be to use "entity" + "propertyName" + "index_suffix" based on the current NamingStrategy object. > Specifying index names on all required properties is very verbose and could lead to errors. -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-693) org.hibernate.engine.query.sql.NativeSQLQueryScalarReturn not serializable

by Eugeniusz Neugebauer (JIRA)

org.hibernate.engine.query.sql.NativeSQLQueryScalarReturn not serializable -------------------------------------------------------------------------- Key: ANN-693 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-693 Project: Hibernate Annotations Issue Type: Bug Environment: jboss 4.2.2, HB 3.2.5 Reporter: Eugeniusz Neugebauer In my domain class I've NamedNativeQuery: @SqlResultSetMappings({@SqlResultSetMapping(name = "uir_suma_zbiorow_result", columns = @ColumnResult(name = "result"))}) @NamedNativeQueries({@NamedNativeQuery(name = "uir.uir_suma_zbiorow", query = "select uir_suma_zbiorow(:var1, :var2, :var3) as result", resultSetMapping = "uir_suma_zbiorow_result")}) During build session factory on jboss i have Exception: Caused by: javax.naming.CommunicationException [Root exception is java.io.NotSerializableException: org.hibernate.engine.query.sql.NativeSQLQueryScalarReturn] at org.jnp.interfaces.NamingContext.bind(NamingContext.java:618) at org.jnp.interfaces.NamingContext.bind(NamingContext.java:552) at org.jboss.util.naming.Util.bind(Util.java:102) at org.jboss.util.naming.Util.bind(Util.java:89) at pl.computerland.syriusz.std.hibernate.jmx.Hibernate2.bind(Hibernate2.java:429) -- 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, 10 months

2
3
0 / 0

[Hibernate-JIRA] Commented: (HHH-1615) GROUP BY entity does not work

by Tim Lüecke (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1615?page=c... ] Tim Lüecke commented on HHH-1615: --------------------------------- I only examined the first query, thinking the second query should be faster anyway. However, as it turns out the second query is even slower than the first in my example. The fastest way in this simple example seems to be to perform a subselect in the select clause instead. > GROUP BY entity does not work > ----------------------------- > > Key: HHH-1615 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1615 > Project: Hibernate3 > Issue Type: Improvement > Components: query-hql > Affects Versions: 3.2.5 > Environment: PostgreSQL 8.1.3, Hibernate 3.1.3 > Reporter: Xavier Bugaud > Assignee: Anthony Patricio > Priority: Critical > Attachments: hibernate-group-by.diff > > > The query : "select cat, count(*) from Cat cat group by cat" does not work. > ERROR: column "xxxx" must appear in the GROUP BY clause or be used in an aggregate function > See : > - http://forum.hibernate.org/viewtopic.php?t=953716 > - http://jira.nhibernate.org/browse/NH-528 -- 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, 10 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3099) Hibernate doesn't find an existing Sequence

by Luis Medalhas (JIRA)

Hibernate doesn't find an existing Sequence ------------------------------------------- Key: HHH-3099 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3099 Project: Hibernate3 Issue Type: Bug Components: core Environment: JBoss 4.2.2GA, JBoss Seam 2.0.1GA, Informix 10 Reporter: Luis Medalhas When i try to deploy my project it fails with this error: Reason: javax.persistence.PersistenceException: org.hibernate.HibernateException: Missing sequence or table: seq_ep4txt_atxtkey But sequence exists, below is definition of my Entity @Entity public class Ep4txt implements java.io.Serializable{ private int atxtkey; private String atxtfmt; private String atxtdoc; @Id @SequenceGenerator(name="Ep4txt_Gen", sequenceName="seq_ep4txt_atxtkey") @GeneratedValue(strategy=GenerationType.SEQUENCE, generator="Ep4txt_Gen") public int getAtxtkey() { return atxtkey; } -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues February 2008