November 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Commented: (HHH-1829) Allow join on any property using property-ref

by Mathieu Gervais (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829?page=c... ] Mathieu Gervais commented on HHH-1829: -------------------------------------- Thanks Anthony for testing the patch. What is your best guest at the time frame for availability of the new metadata API? > Did you think of other ways this could be implemented or was it the only option available? As originally stated, we are not the original patch author. Our expertise in hibernate internals is limited, but we will take a look to see if a simpler patch could be suggested. > Allow join on any property using property-ref > --------------------------------------------- > > Key: HHH-1829 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829 > Project: Hibernate Core > Issue Type: New Feature > Components: metamodel > Affects Versions: 3.2.0 cr1, 3.2.0.cr2 > Reporter: Maarten Winkels > Assignee: Anthony Patricio > Attachments: AbstractJoinTest.java, HHH-1829-3.2.8-SNAPSHOT.patch, HHH-1829-mwinkels.patch, hhh-1829.patch, JoinNoPropertyRefTest.java, JoinPropertyRefTest.java, Person.hbm.xml, Person.java, PersonNoPropertyRef.hbm.xml > > > Currently joining tables for one class (uing the <join...> tag) is only supported for the id property. The property-ref is allowed on the <key..> tag inside the <join..> tag, but this is 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, 6 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1352) Session.setReadOnly(Object, boolean) fails for proxies

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1352?page=c... ] Steve Ebersole commented on HHH-1352: ------------------------------------- There are internal details, but the basic difficulty here is that "read only" is tracked on the o.h.engine.EntityEntry class. EntityEntry is only created and tracked for *initialized* entities. Proxies currently have no way to track there "read only" state. Your patch is making the assumption that the whole entire session will be in "read only" (at least when the proxy data is being fetched). So either we need to decide if it is better to: 1) add an "entry" object that describes proxies (largely it would be a placeholder for data that needs to transfer over to the EntityEntry after fetch). 2) create an entity entry instance for proxies. > Session.setReadOnly(Object, boolean) fails for proxies > ------------------------------------------------------ > > Key: HHH-1352 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1352 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 > Environment: Hibernate 3.1, MySQL 5.0.15-nt > Reporter: Stewart Cambridge > Assignee: Steve Ebersole > Priority: Minor > Original Estimate: 1 day > Remaining Estimate: 1 day > > Session.setReadOnly(Object, boolean) is broken. It throws a TransientObjectException with the message "Instance was not associated with the session" when the object is quite obvious associated with the current session, because we only just loaded it using Session.load(Class, Serializable) > Here is a simple JUnit test, for an arbitrary entity: > public void testReadOnly() > throws Exception > { > User user = (User) session.load(User.class, new Long(7)); > System.out.println("\n=== " + user + " ==="); > session.setReadOnly(user, true); > } > This is the exception stack trace: > org.hibernate.TransientObjectException: Instance was not associated with the session at org.hibernate.engine.StatefulPersistenceContext.setReadOnly(StatefulPersistenceContext.java:1167) at org.hibernate.impl.SessionImpl.setReadOnly(SessionImpl.java:1740) at > test.persistence.HibernateObjectTest.testReadOnly(HibernateObjectTest.java:30) .... -- 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, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-328) Add a builtin bridge for Calendar

by Sanne Grinovero (JIRA)

Add a builtin bridge for Calendar --------------------------------- Key: HSEARCH-328 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-328 Project: Hibernate Search Issue Type: Improvement Components: mapping Reporter: Sanne Grinovero Priority: Minor Fix For: 3.1.1 http://forum.hibernate.org/viewtopic.php?p=2401654 Calendar is a supported Hibernate attribute, but Search is missing a built-in stringbridge: this is causing an ugly stacktrace. Should probably support the same features as date, like "resolution". -- 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, 6 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HHH-4576) Tests in MySQL using different case for objects as defined in configuration

by Strong Liu (JIRA)

Tests in MySQL using different case for objects as defined in configuration --------------------------------------------------------------------------- Key: HHH-4576 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4576 Project: Hibernate Core Issue Type: Bug Components: testsuite Affects Versions: 3.5.0-Beta-2, 3.3.0.GA Environment: mysql Reporter: Strong Liu Assignee: Strong Liu The test below uses different case for object names than defined in XML files. In standard MySQL configuration, it causes a failure, as the object names are case sensitive. Test: BulkManipulationTest#testSimpleNativeSQLInsert - Pickup x PICKUP Same for: MySQLCustomSQLTest.testEntityStoredProcedure MySQLCustomSQLTest.testHandSQL -- 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, 6 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-3486) Include one ore more SLF4J "adapters"

by Chris Bredesen (JIRA)

Include one ore more SLF4J "adapters" ------------------------------------- Key: HHH-3486 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3486 Project: Hibernate Core Issue Type: Improvement Components: build Affects Versions: 3.3.1, 3.3.0.SP1, 3.3.0.GA Reporter: Chris Bredesen Assignee: Steve Ebersole Hibernate, as of 3.3, no longer distributes all jars needed to run the framework. SLF4J requires the inclusion of the SLF4J library as well as either a native or a wrapped implementation. The manual vaguely references such a need but it's never quite clear that the user must visit the SLF4J website and obtain these jars himself. Maven users are of course unaffected since the additional SLF4J jars are published in the central repo. "Adapter" may be the wrong term here but I think the point has been made :) -- 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, 6 months

6
46
0 / 0

[Hibernate-JIRA] Commented: (HHH-1268) Unidirection OneToMany causes duplicate key entry violation when removing from list

by smadar t (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1268?page=c... ] smadar t commented on HHH-1268: ------------------------------- Hi, we are waiting for a resolution for this issue too. In our case a unique constraint is violated (using OneToMany relationship), so it will help if 'delete' operations will be performed before 'insert' or 'update'. Thanks. > Unidirection OneToMany causes duplicate key entry violation when removing from list > ----------------------------------------------------------------------------------- > > Key: HHH-1268 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1268 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.1 > Environment: 3.1 final > MySql 4.1.14 using MYISAM tables > Reporter: Rex Madden > Assignee: Gail Badner > Fix For: 3.2.x, 3.3.x > > Attachments: src.zip > > > Simple OneToMany parent/child relationship using the default table structure (2 tables and a join table) > Add 3 children to the parent. Flush. Remove the first child. Flush throws error: > Exception in thread "main" org.hibernate.exception.ConstraintViolationException: Could not execute JDBC batch update > at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:69) > at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) > at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:202) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:230) > at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:143) > at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:296) > at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) > at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:980) > at UnidirectionalOneToManyRemoveFromListBug.main(UnidirectionalOneToManyRemoveFromListBug.java:27) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:86) > Caused by: java.sql.BatchUpdateException: Duplicate key or integrity constraint violation, message from server: "Duplicate entry '5' for key 2" > at com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1461) > at org.hibernate.jdbc.BatchingBatcher.doExecuteBatch(BatchingBatcher.java:58) > at org.hibernate.jdbc.AbstractBatcher.executeBatch(AbstractBatcher.java:195) > ... 11 more > The problem is that there is a unique key on the relationship table that gets violated. The session removes the last row in the relationship table, then attempts to rewrite the child_id's. It fails since there is a uniqueness constraint on that column. -- 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, 6 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-733) @Immutable documentation improvement

by Emmanuel Bernard (JIRA)

@Immutable documentation improvement ------------------------------------ Key: ANN-733 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-733 Project: Hibernate Annotations Issue Type: Improvement Components: documentation Reporter: Emmanuel Bernard from Paul Benedict Documentation needs further clarification. @Immutable is also allowed on a method/field. If it is applied with a @ManyToOne, is it saying the association is immutable (you can set it but not update it), or the target entity is immutable? Should be defined and also in the API. -- 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, 6 months

4
11
0 / 0

[Hibernate-JIRA] Created: (HBX-1152) EntityPojo.getAllPropertiesIterator(PersistentClass) does not work correctly when the persistent class has a superclass

by Andreas Brieg (JIRA)

EntityPojo.getAllPropertiesIterator(PersistentClass) does not work correctly when the persistent class has a superclass ----------------------------------------------------------------------------------------------------------------------- Key: HBX-1152 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-1152 Project: Hibernate Tools Issue Type: Patch Affects Versions: 3.2.4.GA Environment: hibernate-tools revision 17926 Reporter: Andreas Brieg Priority: Minor Attachments: entitypojo_allpropertiesiterator_with_superclass_properties.patch If a persistent class A is a superclass of persistent class B and A has a property a then B inherits property a. But when iterating through the properties using getAllPropertiesIterator(someInstanceOfB) the property a is not included. For example you might want to have a natural identifier on the superclass and want to generate a finder for a derived class that uses the natural identifier. This isn't possible when getAllPropertiesIterator does not include the properties of the superclass. The patch adds the all-properties-iterator of the superclass to the joined iterator of the derived class. -- 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, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HV-271) HV does not take care "`" to avoid reserved keywords in the sql statements

by Strong Liu (JIRA)

HV does not take care "`" to avoid reserved keywords in the sql statements -------------------------------------------------------------------------- Key: HV-271 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-271 Project: Hibernate Validator Issue Type: Bug Affects Versions: 3.0.0.ga Reporter: Strong Liu Assignee: Hardy Ferentschik this can be reproduced by JPAValidateListenerTest on oracle Model org.hibernate.validator.test.jpa.Submarine contains a property named "size", which gets translated to column "size", but this word is reserved in Oracle, causing exceptions in SchemaExport (create table) and consequently the test fails. After quoting[1] the name of the column, the DDL for the table becomes incorrect, causing a failure in Oracle. When using a different[2] name, the test passes. Failure when using [1]: 17:45:44,631 ERROR SchemaExport:274 - Unsuccessful: create table Submarine (id number(19,0) not null, commander_name varchar2(255 char), name varchar2(255 char) not null, "size" number(19,0) check (size>=10), primary key (id)) 17:45:44,632 ERROR SchemaExport:275 - ORA-00936: missing expression [1] @Column(name="`size`") [2] @Column(name="xsize") -- 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, 6 months

2
2
0 / 0

[Hibernate-JIRA] Assigned: (HHH-1123) Cannot put more than 1000 elements in a InExpression

by Strong Liu (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1123?page=c... ] Strong Liu reassigned HHH-1123: ------------------------------- Assignee: Strong Liu > Cannot put more than 1000 elements in a InExpression > ---------------------------------------------------- > > Key: HHH-1123 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1123 > Project: Hibernate Core > Issue Type: Bug > Components: core > Affects Versions: 3.1 rc2, 3.2.0.alpha1 > Environment: Oracle 9i > Reporter: Alexis Seigneurin > Assignee: Strong Liu > Attachments: hibernate-inexpression-oracle-3.2.patch, patch.txt > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The number of elements that we can put in a "in" expression is limited to a certain amount (1000 for Oracle, for instance). When creating a criteria query, the org.hibernate.criterion.InExpression class should split the expression into several smaller ones. > Attached is a patch which splits the expression by slices of 500 elements. For example, if we have 1001 elements to put in the "in" expression, the result would be : > (entity.field in (?, ?, ?...) or entity.field in (?, ?, ?...) or entity.field in (?)) > The surrounding parantheses are useful to avoid problems with other conditions (a "and" condition taking over the one of the "or" conditions). -- 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, 6 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 November 2009