March 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-779) Test EmbeddedGenericsTest generates a table name "too long" for DB2

by Juraci Paixao Krohling (JIRA)

Test EmbeddedGenericsTest generates a table name "too long" for DB2 ------------------------------------------------------------------- Key: ANN-779 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-779 Project: Hibernate Annotations Issue Type: Bug Environment: Annotations Trunk / DB2 v9.1 Reporter: Juraci Paixao Krohling Annotations test EmbeddedGenericsTest#testWorksWithGenericCollectionOfElements generates the table name "EmbeddedGenericsTest$PopularBook_editions", but DB2 complains about its lengh: DB2 SQL error: SQLCODE: -107, SQLSTATE: 42622, SQLERRMC: EMBEDDEDGENERICSTEST$POPULARBOOK_ID;30 This error message says that the name exceeds the 30 characters limit. -- 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

15 years, 8 months

2
5
0 / 0

[Hibernate-JIRA] Created: (BVAL-103) Support XML Configuration and merge of configuration metadata

by Emmanuel Bernard (JIRA)

Support XML Configuration and merge of configuration metadata ------------------------------------------------------------- Key: BVAL-103 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-103 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard Priority: Minor -- 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

15 years, 8 months

2
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-101) Support for XML mapping

by Emmanuel Bernard (JIRA)

Support for XML mapping ------------------------ Key: BVAL-101 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-101 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard Priority: Minor -- 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

15 years, 8 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-353) hibernate search + indexing with transaction issue

by Yan Falken (JIRA)

hibernate search + indexing with transaction issue -------------------------------------------------- Key: HSEARCH-353 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-353 Project: Hibernate Search Issue Type: Bug Components: engine Affects Versions: 3.1.0.GA Reporter: Yan Falken Hi, I have the following problem with indexing in transaction with hibernate search: in case the transaction is opened and I want to perform multiple work types - only one type is actually performed after the commit and the others are ignored; example: TransactionManager tm = new DummyTransactionManager(); tm.begin(); SEntity se1 = new SEntity(10, "first", "second", true); Work delete = new Work(se1, "100", WorkType.DELETE); Work add = new Work(se1, "100", WorkType.ADD); Ctx ctx = new Ctx(tm.getTransaction()); searchFactory.getWorker().performWork(delete, ctx); searchFactory.getWorker().performWork(add, ctx); tm.commit(); only DELETE is performed - ADD is ignored log: 2009-03-23 13:45:02,195 TRACE main| MaskedProperty| found a match for key: [hibernate.search.default.indexBase] value: /tmp/c1idx 2009-03-23 13:45:02,195 TRACE main| MaskedProperty| found a match for key: [default.indexBase] value: /tmp/c1idx 2009-03-23 13:45:02,341 DEBUG main| BuilderIndexedEntity| Field selection in projections is set to false for entity problems.SEntity. 2009-03-23 13:45:02,502 DEBUG pool-1-thread-1| PerDPQueueProcessor| Skipping usage of an IndexWriter for updates 2009-03-23 13:45:02,503 TRACE pool-1-thread-1| PerDPQueueProcessor| Locking Workspace (or waiting to...) 2009-03-23 13:45:02,503 TRACE pool-1-thread-1| PerDPQueueProcessor| Workspace lock aquired. // opened 2009-03-23 13:45:02,503 DEBUG pool-1-thread-1| PerDPQueueProcessor| Opening an IndexReader for update 2009-03-23 13:45:02,503 TRACE pool-1-thread-1| Workspace| IndexReader opened // only remove 2009-03-23 13:45:02,503 TRACE pool-1-thread-1| eleteExtWorkDelegate| Removing class problems.SEntity#100 by id using an IndexReader. 2009-03-23 13:45:02,539 TRACE pool-1-thread-1| Workspace| IndexReader closed 2009-03-23 13:45:02,539 TRACE pool-1-thread-1| PerDPQueueProcessor| Unlocking Workspace I digged into the code a little bit and there is class method: org.hibernate.search.engine.DocumentBuilderIndexedEntity.addWorkToQueue() which is in it's beginning iterating the existing queue to avoid unecessary duplicated works if ( workType == WorkType.DELETE ) { //TODO add PURGE? //DELETE should have precedence over any update before (HSEARCH-257) //if an Add work is here, remove it //if an other delete is here remember but still search for Add if ( luceneWork instanceof AddLuceneWork ) { toDelete.add( luceneWork ); } else if ( luceneWork instanceof DeleteLuceneWork ) { duplicateDelete = true; } } else { //we can safely say we are out, the other work is an ADD return; } I believe that return should be changed to continue. I did several tests and after the change it can handle ADD/DELETE works in one queue. There should be ability to in single transaction perform multiple work types as there is no way how to control the client to perform just one work type. -- 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

15 years, 8 months

3
9
0 / 0

[Hibernate-JIRA] Created: (HHH-3554) Investigate how bulk updates can be supported

by Adam Warski (JIRA)

Investigate how bulk updates can be supported --------------------------------------------- Key: HHH-3554 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3554 Project: Hibernate Core Issue Type: Task Components: envers Reporter: Adam Warski -- 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

15 years, 8 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2317) CGLIB unable to lazy load classes in diff. classloader than hibernate jars

by Jason Novotny (JIRA)

CGLIB unable to lazy load classes in diff. classloader than hibernate jars --------------------------------------------------------------------------- Key: HHH-2317 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2317 Project: Hibernate3 Type: Bug Components: core Versions: 3.2.1 Reporter: Jason Novotny Please see http://forum.hibernate.org/viewtopic.php?p=2334617#2334617 for more details and possible fix -- 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

15 years, 8 months

5
8
0 / 0

[Hibernate-JIRA] Created: (HHH-3229) Make cascade rules more transparent/explicit/deterministic

by Chris Bredesen (JIRA)

Make cascade rules more transparent/explicit/deterministic ---------------------------------------------------------- Key: HHH-3229 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3229 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.6, 3.2.5, 3.2.4.sp1 Reporter: Chris Bredesen Cascade rules are prone to different behavior based on the order in which properties appear in mapping XML. It is possible that an unexpected TransientObjectException may arise from certain operations when an object graph with circular references is merged (and possibly persisted/updated, etc). For example, if a transient instance is reachable through more than once path from a root entity, it is not clear whether operations will be cascaded to it. The order in which the properties are mapped plays a part in determining cascade paths, but the rules are not documented. Possible resolutions include: 1. Documenting the rules so that a programmer can make educated decisions about mapping. 2. Enhancing the algorithm such that order no longer matters and the rules are deterministic. 3. ??? -- 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

15 years, 8 months

6
12
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-329) Workers ThreadPools breaks ThreadLocals

by Grégoire Rolland (JIRA)

Workers ThreadPools breaks ThreadLocals --------------------------------------- Key: HSEARCH-329 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-329 Project: Hibernate Search Issue Type: Bug Components: directory provider Affects Versions: 3.1.0.GA Reporter: Grégoire Rolland When Implementing multi-domains (multi-databases) FSDirectory based on thread local (to get the thread environment, database name, etc...), the threadpool used by workers "forgot" the thread local variables on the second call (for searching, indexing). Works great with 3.0.1 release, but not with 3.1.0.GA. -- 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

15 years, 8 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3095) Invalid queries when using subclasses and one-to-many associations

by Sebastien Blind (JIRA)

Invalid queries when using subclasses and one-to-many associations ------------------------------------------------------------------ Key: HHH-3095 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3095 Project: Hibernate3 Issue Type: Bug Components: query-sql Affects Versions: 3.2.5 Environment: Hibernate 3.2.5, bug identified on sybase Reporter: Sebastien Blind Priority: Blocker Attachments: src-cat.zip This bug report builds on top of the topic found in the forum at http://forum.hibernate.org/viewtopic.php?t=977453 Basically, there seems to be an issue in the way hibernate treats a collections of objects that extend a base class. The attached example has: a Cat class a DomesticCat class (extends Cat) a Cage class (can contain multiple DomesticCat) The generated SQL is below - the filter cats0_.CAGE_ID=? should really be cats0_1_.CAGE_ID=? select cats0_.CAGE_ID as CAGE3_1_, cats0_.CAT_ID as CAT1_1_, cats0_.CAT_ID as CAT1_0_0_, cats0_1_.CAGE_ID as CAGE2_2_0_ from CAT cats0_ inner join DCAT cats0_1_ on cats0_.CAT_ID=cats0_1_.CAT_ID where cats0_.CAGE_ID=? As of now, I am not aware of any configuration that would work around this problem. Please let me know if you know otherwise. Thanks, Sebastien -- 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

15 years, 8 months

2
1
0 / 0

[Hibernate-JIRA] Created: (ANN-790) ImmutableTest leaves an active transaction

by Juraci Paixao Krohling (JIRA)

ImmutableTest leaves an active transaction ------------------------------------------ Key: ANN-790 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-790 Project: Hibernate Annotations Issue Type: Patch Environment: PostgreSQL 8.2.3 and Annotations from trunk Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Attachments: ImmutableTest.java.diff ImmutableTest leaves an active transaction and makes PostgreSQL waits until it is finished (which never occurs). The attached patch fixes it. -- 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

15 years, 8 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2009