April 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

16 years, 11 months

2
5
0 / 0

[Hibernate-JIRA] Commented: (ANN-140) Discriminator column not supported with JOINED strategy

by Sergey Generalov (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/ANN-140?page=co... ] Sergey Generalov commented on ANN-140: -------------------------------------- 4 years passed since this issue was opened. Any changes? "Status: Resolved Resolved Resolution: Rejected " Rejected? Why? This is very important functionality. Can anyone tell why this issue was skipped, please. > Discriminator column not supported with JOINED strategy > ------------------------------------------------------- > > Key: ANN-140 > URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-140 > Project: Hibernate Annotations > Issue Type: Bug > Affects Versions: 3.1beta6 > Environment: Hibernate 3.1rc2, Hibernate Annotations 3.1b6 > Reporter: Steven Grimm > > Section 9.1.27 of the EJB3 persistence public draft says, "The DiscriminatorColumn annotation is used to define the discriminator column for SINGLE_TABLE and JOINED mapping strategies." But Hibernate ignores the DiscriminatorColumn annotation when the mapping strategy is JOINED; when a JOINED entity is persisted, its discriminator column is not included in the SQL "insert" statement, resulting in a not-null constraint violation if the discriminator column is marked NOT NULL in the database. > The JOINED strategy with discriminators is pretty ubiquitous in EJB3 sample code and tutorials out on the net, so lots of people are likely to run into this as they try out EJB3 for the first time. A few examples: > http://www.oracle.com/technology/tech/java/oc4j/ejb3/howtos-ejb3/howtoejb... > http://www.solarmetric.com/Software/Documentation/4.0.0EA/docs/full/html/... > http://www.caucho.com/resin-3.0/amber/tutorial/cmp-inherit/index.xtp -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-3883) Filter on List - null elements - very interesting

by Sandeep Vaid (JIRA)

Filter on List - null elements - very interesting ------------------------------------------------- Key: HHH-3883 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3883 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.3.1 Reporter: Sandeep Vaid Say i have one-to-many relationship between Product and ProductNames. So Product has a List of ProductNames. Actually we are using List for productNames.and for list, in order to maintain the sequence, it stores the sequence in extra seperate column in DB. Now say, after applying the filer conditions, 0th, 2nd and 5th element (out of 10 )of the list gets selected.. Returned list size will of size 6 with 1st,3rd and 4th element as null and 0th,2nd and 5th element properly populated. I guess this is done in hibernate for maitaining ordering of List. What should i do if i don't want these null elements in the returned List? -- 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, 11 months

1
0
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

16 years, 11 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

16 years, 11 months

2
4
0 / 0

[Hibernate-JIRA] Created: (HHH-3882) inner join fetch + Filters + one-to-many + Extra null value

by Sandeep Vaid (JIRA)

inner join fetch + Filters + one-to-many + Extra null value ----------------------------------------------------------- Key: HHH-3882 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3882 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.3.1 Reporter: Sandeep Vaid Specify relationship in mapping using some condition not just id's. Say i have one-to-many relationship between Product and ProductNames Product ----> PID (PK) ProductNames------> PID, USECODE, STARTTIME as composite ID and ENDTIME is another normal column. Now i want to fetch product with PID='1' and USECODE='100' and STARTTIME < CURRENTTIME < ENDTIME. CURRENTTIME value will be known at runtime. How to specify this in mapping and fetch Product & ProductNames using eager fetching? ANS: Using Filters, this problem can be resolved. Define filter, attach filter and enable filter. Filter supports specifying positional parameters value at runtime. but i got 1 problem with filters : Suppose i have 1 product with id as 100, it has 5 ProductNames..but when we apply filter only 2 productNames remains. When i use just "inner join fetch" with no filters, it returns me one Product object which contains List of productNames properly populated. BUT When i use "select distinct product" and inner join fetch" with filter, it returns one product populated with productNames list which contains 3 elements viz. null, first filtered productName, second filtered productName.. Why productNames list contains the first element as null? This seems to be a bug.. -- 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, 11 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HBX-575) Able to add meta information on the reveng.xml file (common configuration for all renerated classes)

by Tonté Pouncil (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HBX-575?page=co... ] Tonté Pouncil commented on HBX-575: ----------------------------------- Okay, since my last post I have check out the source code of hibernate tools and updated the hibernate-reverse-engineering-3.0.dtd; which is located under tools/src/java/org/hibernate. I have modified the DTD to accepted the <meta> tag for the <key-column> tag. I have also modified the PojoPropertyAccessors.ftl free-marker templates to use my table configuration defined in my reveng.xml file to be used in create the POJOs, in regards to set-scope and get-scope. Let me know if any of my customization can be of any use to you as I am more than willing to share what I have learned. How do I get my changes review and check into the source code? Thanks! Tonté > Able to add meta information on the reveng.xml file (common configuration for all renerated classes) > ---------------------------------------------------------------------------------------------------- > > Key: HBX-575 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-575 > Project: Hibernate Tools > Issue Type: Improvement > Components: reverse-engineer > Affects Versions: 3.1beta4 > Reporter: David Leal > Fix For: 3.2beta9 > > Attachments: svn-patch2.txt > > > Just to add the posibility to set some meta information common to all possible generated *.hbm files, for example to set that ALL generated file will implement toString method or equal/hash code. > A good solution whoud be to add some filter options in order to speficy the set of Tables it would apply, using regular expresion, like include nestede target from ant. Something like this: > <meta attribute name="theAttributeName" value="theValue"> > <include name="theListOfTableToInclude"/> > <exlude name="theListOfTablesToExclude"> > </meta> > If it is more complicated just to add the possibility to add meta information for all possible generated files. -- 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, 11 months

1
0
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

16 years, 11 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

16 years, 11 months

2
4
0 / 0

[Hibernate-JIRA] Created: (EJB-433) Test ProgrammaticConfTest fails due to lack of "create-drop"

by Juraci Paixao Krohling (JIRA)

Test ProgrammaticConfTest fails due to lack of "create-drop" ------------------------------------------------------------ Key: EJB-433 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-433 Project: Hibernate Entity Manager Issue Type: Bug Affects Versions: 3.3.3, 3.5 Reporter: Juraci Paixao Krohling Assignee: Juraci Paixao Krohling Fix For: 3.3.3, 3.5 The test ProgrammaticConfTest needs the property hibernate.hbm2ddl.auto to be set as create-drop, to create the tables before running the test. Most of the tests in EntityManager extends a test case which automatically sets this property. The test ProgrammaticConfTest also contains a method which explicitly sets this property, but this method is not being called. Either this test needs to call the getProperties() or the hibernate.properties must contain the property. In the branch v3_4_0_GA_CP, this property is set in the template of hibernate.properties. -- 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, 11 months

1
5
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 April 2009