December 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-5756) Envers creates new revisions when only collection changed for entity

by Svyatoslav Reyentenko (JIRA)

Envers creates new revisions when only collection changed for entity -------------------------------------------------------------------- Key: HHH-5756 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5756 Project: Hibernate Core Issue Type: Bug Components: envers Affects Versions: 3.6.0 Environment: Hibernate 3.6.0, H2 database Reporter: Svyatoslav Reyentenko Attachments: audit.zip When a new element is adding to collection, entity that holds this collection gets new revision even with the property org.hibernate.envers.revision_on_collection_change set to false. Look at test case in project attached. -- 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

2
2
0 / 0

[Hibernate-JIRA] Created: (HHH-5721) Script for migrating database to new validity audit strategy

by Stephan Pabinger (JIRA)

Script for migrating database to new validity audit strategy ------------------------------------------------------------ Key: HHH-5721 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5721 Project: Hibernate Core Issue Type: Patch Components: envers Reporter: Stephan Pabinger Attachments: validityMigrationScript.zip Perl script for migrating database tables to new validity audit strategy. Provided is a readme file that explains necessary configuration steps. -- 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

2
5
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-577) IllegalArgumentException when trying to delete proxy class

by Tom (JIRA)

IllegalArgumentException when trying to delete proxy class ---------------------------------------------------------- Key: HSEARCH-577 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-577 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.1 Environment: Hibernate Search 3.2.1 Hibernate Core 3.5.2 Reporter: Tom Attachments: ProxyTestCase.zip I'm receiving an IllegalArgumentException while trying to delete an entity that is a part of a @ContainedIn/@IndexedEmbedded relationship. I created a testcase to reproduce the error i'm seeing. The original issue that prompted this was actually a ClassCastException as discussed in this thread https://forum.hibernate.org/viewtopic.php?f=9&t=1006381 however in creating the test case i was unable to replicate that particular error, but ran into this one, which seemed similar. -- 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
8
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-513) Hibernate Search 3.2.0.CR1 listeners cause long delays when indexing entities saved in different transactions

by Florin Haizea (JIRA)

Hibernate Search 3.2.0.CR1 listeners cause long delays when indexing entities saved in different transactions ------------------------------------------------------------------------------------------------------------- Key: HSEARCH-513 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-513 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.2.0.CR1 Environment: Hibernate 3.5.1-Final Spring 3.0.2 MySQL Connector 5.1.6 Reporter: Florin Haizea Attachments: HibernateSearchJira.zip I have 3 entities Person, Event and ParentOfBirthEvent. I save about 8000 Person objects in batches of 20, each batch is being saved in a different transaction. After a sufficient number of entities have been persisted (the saving and indexing of initial batches takes between150ms and 500ms) the indexing of the entities that are saved in some of the following batches takes a very large amount of time (sometime even minutes for a whole batch). The problem is that in order for these delays to appear there has to be a certain relationship between the objects saved in the current batch and objects saved in previous batches. The only way in which I can reproduce this 100% is by importing a file (which was submitted by one of the users of our app), creating entities based on the data in that file and saving the entities in batches of 20. When I reach batch number 273 or so the indexing starts taking a lot of time. If I removed the @IndexedEmbedded annotation from the "parent" field in the ParentOfBirthEvent class the problem is solved. Also, if I removed all the hibernate search listeners from the sessionFactory the problem is solved. -- 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

7
68
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-570) Optimize the o^2 loop in DocumentBuilderIndexedEntity.addWorkToQueue

by Sanne Grinovero (JIRA)

Optimize the o^2 loop in DocumentBuilderIndexedEntity.addWorkToQueue -------------------------------------------------------------------- Key: HSEARCH-570 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-570 Project: Hibernate Search Issue Type: Improvement Affects Versions: 3.3.0.Alpha1, 3.2.1, 3.2.0.Final Reporter: Sanne Grinovero Fix For: 3.3.0 there's a long-standing comment in the method: bq. //TODO with the caller loop we are in a n^2: optimize it using a HashMap for work recognition Apparently it has a critical impact in some scenarios: [this forum post|https://forum.hibernate.org/viewtopic.php?f=9&t=1006054] mentions the algorithm "running for days" in a 1000 elements change in a single transaction. -- 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

2
8
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-641) idProvided flag in DocumentBuilderIndexedEntity is always false

by Sanne Grinovero (JIRA)

idProvided flag in DocumentBuilderIndexedEntity is always false --------------------------------------------------------------- Key: HSEARCH-641 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-641 Project: Hibernate Search Issue Type: Bug Affects Versions: 3.3.0.CR1 Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 3.3.0 This doesn't affect any functionality as it's actually preventing a bug, if it was set to true the StringBridge for the provided id would have been ignored. -- 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

2
1
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-639) Update dependency to Lucene 3.0.3

by Sanne Grinovero (JIRA)

Update dependency to Lucene 3.0.3 --------------------------------- Key: HSEARCH-639 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-639 Project: Hibernate Search Issue Type: Improvement Reporter: Sanne Grinovero Assignee: Sanne Grinovero Priority: Minor Fix For: 3.3.0 [http://lucene.apache.org/java/3_0_3/changes/Changes.html#3.0.3.documentation] All tests seem to pass fine just changing the maven dependency. -- 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

2
1
0 / 0

[Hibernate-JIRA] Created: (METAGEN-29) Embedded generic types not supported by metamodel generator

by Adrian Hummel (JIRA)

Embedded generic types not supported by metamodel generator ----------------------------------------------------------- Key: METAGEN-29 URL: http://opensource.atlassian.com/projects/hibernate/browse/METAGEN-29 Project: Hibernate Metamodel Generator Issue Type: Bug Components: processor Affects Versions: 1.0.0-CR-1 Environment: Hibernate 3.5.0-CR-2 Reporter: Adrian Hummel Assignee: Hardy Ferentschik Priority: Critical Attachments: bugreport.zip Scenario: I have a @MappedSuperclass defining an abstract entity. This class has a technical primary key and a business identity. The business identity is realized by means of a generic embeddable (e.g. for a Customer class there is a corresponding CustomerId class for its business identity). The JPAMetaModelEntityProcessor does generate the AbstractEntity_ class but does only include the primary key field but omits the generic field for the business identity (which leads to subsequent errors when accessing this field using a CriteriaBuilder). Attached a mini project with a test case which illustrates the problem. -- 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

4
8
0 / 0

[Hibernate-JIRA] Created: (HCANN-31) Order of @JoinColumn annotations

by Rich McLaughlin (JIRA)

Order of @JoinColumn annotations -------------------------------- Key: HCANN-31 URL: http://opensource.atlassian.com/projects/hibernate/browse/HCANN-31 Project: Hibernate Commons Annotations Issue Type: Bug Reporter: Rich McLaughlin I have two entities that I'm trying to join on 3 columns. For some reason, the order of the @JoinColumn annotations affects the SQL that get produced. I double-check my classes and all the columns are named and annotated correctly. This annotation: @JoinColumns({ @JoinColumn (name = "ATTR_1"), @JoinColumn (name = "ATTR_2"), @JoinColumn (name = "ATTR_3") }) produces this SQL: on this_.ATTR_1=othertable_.ATTR_2 and this_.ATTR_2=othertable_.ATTR_1 and this_.ATTR_3=othertable_.ATTR_3 But when I switch the annotation: @JoinColumns({ @JoinColumn (name = "ATTR_2"), @JoinColumn (name = "ATTR_1"), @JoinColumn (name = "ATTR_3") }) Then it works on this_.ATTR_1=othertable_.ATTR_1 and this_.ATTR_2=othertable_.ATTR_2 and this_.ATTR_3=othertable_.ATTR_3 Any ideas? Thanks! -- 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

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-4413) Support interface inheritance mapping

by RynekMedyczny (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4413?page=c... ] RynekMedyczny commented on HHH-4413: ------------------------------------ Is there any progress on this issue? Are there any known workarounds? Not being able to use interfaces with Hibernate Annotations is really inconvenient for Hibernate users :( Kind Regards > Support interface inheritance mapping > ------------------------------------- > > Key: HHH-4413 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4413 > Project: Hibernate Core > Issue Type: Improvement > Components: annotations > Reporter: Steve Ebersole > Attachments: hibernate3-annotations-3.1beta5-3896-3948.diff, hibernate3-annotations-3.1beta5-3896-4138.diff > > > It should be possible to create a mapping with interfaces, as described by the documentation here: http://www.hibernate.org/hib_docs/v3/reference/en/html_single/#inheritanc... > Specifically right now it is impossible to annotate interfaces and according to HBX-231 even if you could @Entity is only meant to get used on classes so the question becomes "what do you annotate it with?" > As I pointed out here http://forum.hibernate.org/viewtopic.php?p=2238824#2238824 the additional problem seems to be that XDoclet doesn't support interface annotation either (http://opensource.atlassian.com/projects/xdoclet/browse/XDT-1345) so I'm left without a workaround. > I can't convert the interfaces to abstract classes because I implement multiple interfaces in my application and Java does not do multiple inheritance. > If you know of a nice workaround, please let me know :) -- 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

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues December 2010