May 2010 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (ANN-687) orm.xml - cleanup respecting column names

by darren hartford (JIRA)

orm.xml - cleanup respecting column names ----------------------------------------- Key: ANN-687 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-687 Project: Hibernate Annotations Issue Type: Bug Components: binder Affects Versions: 3.3.0.ga Environment: mysql 5, MS SQL 2000, Win2000, hibernate 3.2.4 Reporter: darren hartford couple of issues with orm.xml mapping file that is not fully implemented and needs cleanup. many-to-many table mapping not respecting column names. http://forum.hibernate.org/viewtopic.php?t=982330 id-class not respecting column names (end of an old issue, repeated with different scenario). http://opensource.atlassian.com/projects/hibernate/browse/ANN-361 <id-class class="MyTestId"/> <attributes> <id name="compoundOne"> <column name="COMPOUND_ONE"/> </id> <id name="compoundTwo"> <column name="COMPOUND_TWO"/> </id> ... WARNING: Preparing the statement failed: Invalid column name 'compoundOne'. WARNING: Preparing the statement failed: Invalid column name 'compoundTwo'. ========== Use case and urgency of issue related to external technology integration. -DTO should not require hibernate-annotations to be used in client-code, but is required when using annotations. orm.xml approach removes this limitation. -GWT 1.4 does not work with java 1.5/annotated DTO. Although everyone keeps pushing it off saying 'GWT 1.5 is on the way', it is not and solutions that should have been working to work around that limitation need to be working correctly. -- 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

13 years, 10 months

3
3
0 / 0

[Hibernate-JIRA] Created: (HHH-5056) Criteria API with ProjectionList and Unique result

by Ahmed Ali Elsayed Ali Soliman (JIRA)

Criteria API with ProjectionList and Unique result -------------------------------------------------- Key: HHH-5056 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5056 Project: Hibernate Core Issue Type: Bug Components: query-criteria Affects Versions: 3.5.0-CR-2 Environment: Hibernate 3.3.2, Oracel 11g Reporter: Ahmed Ali Elsayed Ali Soliman Priority: Critical when you make a select statement with Criteria API & use ProjectionList to retrieve some columns then use the unique result make at least 2 projection list (2 columns or more) ProjectionList projectionList = Projections.projectionList() .add(Projections.property("ColumnA")) .add(Projections.property("ColumnB")); criteria.setResultTransformer(CriteriaSpecification.DISTINCT_ROOT_ENTITY); the result must be retrieved in 2 dimensional array of Object(Object[][]) but the result are one dimensional array with one column only. Note:- when you remove the unique result it works fine but when you add it, it make this behavior. -- 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

13 years, 10 months

2
13
0 / 0

[Hibernate-JIRA] Created: (ANN-472) @UniqueConstraint declaration is not friendly towards inheritance or reflection

by Ted Bergeron (JIRA)

@UniqueConstraint declaration is not friendly towards inheritance or reflection ------------------------------------------------------------------------------- Key: ANN-472 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-472 Project: Hibernate Annotations Type: Improvement Versions: 3.2.0.ga Environment: Hibernate 3.2 GA Reporter: Ted Bergeron The current way to define a composite unique constraint is limiting. @Table(name="tbl_sky", uniqueConstraints = {@UniqueConstraint(columnNames={"month", "day"})} ) Suppose I have an abstract base class called A that gives me Id and Name, subclassed by abstract class B that gives me Customer. Then I have many concrete classes that subclass B. For all of these, I'd want the combination of Name and Customer to be unique. As I do not use @Table with abstract base classes, I currently have to repeat: uniqueConstraints = {@UniqueConstraint(columnNames={"name", "customer_id"})} on all concrete classes. If we had an alternate way to define these constraints at the property level (as XDoclet did with hibernate 2), I could define this in the base classes and inherit the constraint declaration. The other need is that I would like to use reflection to scan the properties and apply proper validations in the view layer. With @Column(unique = true) this is easy to do. The view layer makes an AJAX call and all is well. For a composite constraint, it does not work well currently. -- 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

13 years, 10 months

5
9
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-430) Use multiple threads for text analysis in MassIndexer

by Sanne Grinovero (JIRA)

Use multiple threads for text analysis in MassIndexer ----------------------------------------------------- Key: HSEARCH-430 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-430 Project: Hibernate Search Issue Type: New Feature Components: documentation, engine Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0.Beta3 org.hibernate.search.MassIndexer is defining the API already, it's commented. Implementor also has a sketch already, currently commented out. -- 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

13 years, 10 months

2
6
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-370) Monitoring of batch indexer state and progress

by Sanne Grinovero (JIRA)

Monitoring of batch indexer state and progress ---------------------------------------------- Key: HSEARCH-370 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-370 Project: Hibernate Search Issue Type: New Feature Reporter: Sanne Grinovero Assignee: Sanne Grinovero Fix For: 3.2.0 -- 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

13 years, 10 months

2
12
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-361) Only index an entity if an indexed property has changed

by Emmanuel Bernard (JIRA)

Only index an entity if an indexed property has changed ------------------------------------------------------- Key: HSEARCH-361 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-361 Project: Hibernate Search Issue Type: New Feature Reporter: Emmanuel Bernard Fix For: 3.2.0 PostUpdateEvent has state and oldState and EntityPersister has getPropertyNames() and findDirty() -- 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

13 years, 10 months

7
32
0 / 0

[Hibernate-JIRA] Created: (EJB-397) native SQL queries in hibernate don't work when using aliases to differentiate columns that have the same name

by Alex McCarrier (JIRA)

native SQL queries in hibernate don't work when using aliases to differentiate columns that have the same name -------------------------------------------------------------------------------------------------------------- Key: EJB-397 URL: http://opensource.atlassian.com/projects/hibernate/browse/EJB-397 Project: Hibernate Entity Manager Issue Type: Bug Components: EntityManager Affects Versions: 3.3.2.GA Environment: jboss 4.2.2, mysql 5 Reporter: Alex McCarrier Basically same as HHH-2094, if you do something like this: select oldForm.data as oldData newForm.data as newData from form oldForm, join form newForm on oldForm.replaced_by_id = newForm.id then use entityManager.createNativeQuery(sql).getResultList() it will end up with an error that says column named oldData does not exist. If you take out the aliases, then it will just return the first value for "data" for every column. If you run this through straight JDBC with the alias, it works as expected. -- 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

13 years, 10 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-4939) Bidirectional OneToOne mapping with FK and composite PK sharing a column throws MappingException

by Chris Wilson (JIRA)

Bidirectional OneToOne mapping with FK and composite PK sharing a column throws MappingException ------------------------------------------------------------------------------------------------ Key: HHH-4939 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4939 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Reporter: Chris Wilson Attachments: HibernateAnnotationMappingOneToOneTest.java A bidirectional one-to-one mapping, where the owning side's column is part of a composite primary key, fails to configure, possibly because OneToOneType#getColumnSpan returns zero instead of the actual number of columns used by the join. When the foreign key column used is not also part of the primary key, or the composite primary key contains only a single column, then the mapping doesn't fail. {code} org.hibernate.MappingException: broken column mapping for: journeyComment.id of: org.wfp.rita.test.hibernate.HibernateAnnotationMappingOneToOneTest$Journey at org.hibernate.persister.entity.AbstractPropertyMapping.initPropertyPaths(AbstractPropertyMapping.java:143) at org.hibernate.persister.entity.AbstractPropertyMapping.initIdentifierPropertyPaths(AbstractPropertyMapping.java:206) at org.hibernate.persister.entity.AbstractPropertyMapping.initPropertyPaths(AbstractPropertyMapping.java:181) at org.hibernate.persister.entity.AbstractEntityPersister.initOrdinaryPropertyPaths(AbstractEntityPersister.java:1725) at org.hibernate.persister.entity.AbstractEntityPersister.initPropertyPaths(AbstractEntityPersister.java:1755) at org.hibernate.persister.entity.AbstractEntityPersister.postConstruct(AbstractEntityPersister.java:2932) at org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:431) at org.hibernate.persister.PersisterFactory.createClassPersister(PersisterFactory.java:84) at org.hibernate.impl.SessionFactoryImpl.<init>(SessionFactoryImpl.java:267) at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1341) at org.hibernate.cfg.AnnotationConfiguration.buildSessionFactory(AnnotationConfiguration.java:867) at org.wfp.rita.test.base.HibernateTestBase.buildSessionFactory(HibernateTestBase.java:93) at org.wfp.rita.test.base.HibernateTestBase.setUp(HibernateTestBase.java:106) at junit.framework.TestCase.runBare(TestCase.java:128) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:120) at junit.framework.TestSuite.runTest(TestSuite.java:230) at junit.framework.TestSuite.run(TestSuite.java:225) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:478) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:344) at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:196) {code} Test case attached. Change HibernateTestBase to org.hibernate.test.annotations.TestCase to run under Hibernate. -- 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

13 years, 10 months

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-85) Support dynamic default group sequence definition

by Emmanuel Bernard (JIRA)

Support dynamic default group sequence definition ------------------------------------------------- Key: BVAL-85 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-85 Project: Bean Validation Issue Type: New Feature Components: ri-general Reporter: Emmanuel Bernard Will probably not be spec'ed in the 1.0 JSR but can be added as a RI feature. -- 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

13 years, 10 months

4
22
0 / 0

[Hibernate-JIRA] Created: (HHH-2692) Insert Into Select command doesn't allow named parameter as select output (insert input)

by John Aylward (JIRA)

Insert Into Select command doesn't allow named parameter as select output (insert input) ---------------------------------------------------------------------------------------- Key: HHH-2692 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2692 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.4.sp1 Environment: Hibernate 3.2.4.sp1 with Annotations 3.3.0 And Validator 3.0.0 MySQL 5.0.42 Reporter: John Aylward receive exception: org.hibernate.QueryException: number of select types did not match those for insert [INSERT INTO ProviderInvoiceLineItem (amount,billingAccount,circuit,description,invoice,type) SELECT pili.amount, pili.billingAccount, pili.circuit, pili.description, :newInvoice, pili.type FROM com.cicat.bedrock.billing.model.ProviderInvoiceLineItem pili WHERE pili.invoice = :oldInvoice] Idea is to copy all line items from one invoice to another. In other words, only difference between data should be the invoice. easiest way to do this is with "insert into" command and passing parameter of changed value. * Trying to cast named parameter (:newInvoice) caused parsing error * Trying to replace invoice with invoice_id and repacing :newInvoice with actual invoice id resulted in a "property 'invoice_id' not found" exception Should be able to set a value through a named parameter -- 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

13 years, 10 months

5
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues May 2010