June 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-3352) HQL bulk update on JOINED inheritance tree improvement

by Anthony Patricio (JIRA)

HQL bulk update on JOINED inheritance tree improvement ------------------------------------------------------ Key: HHH-3352 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3352 Project: Hibernate3 Issue Type: Improvement Components: query-hql Affects Versions: 3.2.4.sp1 Reporter: Anthony Patricio Priority: Minor Updating of entities in an inheritance hierarchy with the JOINED strategy. Trying to update all entities of this hierarchy using a hql statement that affects attributes/columns of the base entity only doesn't need the insert into TEMP / Update BASE_TABLE / delete TEMP logic Update BASE_TABLE is sufficient and more efficient. -- 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, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HBX-895) Content assist doesn't work when an entity alias is not preceded by whitespace

by Joseph Marques (JIRA)

Content assist doesn't work when an entity alias is not preceded by whitespace ------------------------------------------------------------------------------ Key: HBX-895 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-895 Project: Hibernate Tools Type: Bug Versions: 3.2beta8 Reporter: Joseph Marques In an HQL editor: If I type - "count(col." - and press ctrl+space, I don't get the content assist for col If I type - "count( col." - and press ctrl+space, I do Similarly, If I type - "select a,b." - and press ctrl+space, I don't get the content assist for b If I type - "select a, b." - and press ctrl+space, I do It's pretty clear that the lexing is a little bit too tight here, and that for better usability it should be relaxed. The second case isn't as big a deal as the first (because I don't know a single person that doesn't comma-space delimit the select clause, but I'm thinking that some people that don't realize that they have to put a space in front of it might think that the tools simply can't auto-complete inside functions. -- 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, 6 months

2
1
0 / 0

[Hibernate-JIRA] Created: (HV-163) Add [] to non-indexed iterable in paths

by Emmanuel Bernard (JIRA)

Add [] to non-indexed iterable in paths --------------------------------------- Key: HV-163 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-163 Project: Hibernate Validator Issue Type: New Feature Affects Versions: 4.0.0.Beta1 Reporter: Emmanuel Bernard Fix For: 4.0.0.Beta2 -- 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, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HBX-858) wizard does not enable cfg.xml when it should

by Max Rydahl Andersen (JIRA)

wizard does not enable cfg.xml when it should --------------------------------------------- Key: HBX-858 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-858 Project: Hibernate Tools Type: Bug Components: consoleconfiguration Versions: 3.2beta9 Reporter: Max Rydahl Andersen when creating cfg.xml and afterwards in same wizard console config and etc/persistence.xml exists the cfg.xml cannot be enabled again...(jpa is chosen automatically) -- 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, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HBX-880) Support sorting/grouping of the items in the Session Factory section of the Hiberate Configurations view

by Joseph Marques (JIRA)

Support sorting/grouping of the items in the Session Factory section of the Hiberate Configurations view -------------------------------------------------------------------------------------------------------- Key: HBX-880 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-880 Project: Hibernate Tools Type: New Feature Versions: 3.2beta8 Reporter: Joseph Marques I'm working with a domain model that has over 100 entities. It would be nice to have a consistent ordering of these items...maybe based off of the fully-qualified class name? It would be even nicer if they could be grouped by their different packages, which is how I've more naturally navigated to them in the past. Of course the packages should also be alpha-sorted, and each each of entities within a package sorted as well. -- 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, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (HSEARCH-381) Compile Error by Usage FiledBridge (Hibernate Search 3.1.1)

by Mario (JIRA)

Compile Error by Usage FiledBridge (Hibernate Search 3.1.1) ----------------------------------------------------------- Key: HSEARCH-381 URL: http://opensource.atlassian.com/projects/hibernate/browse/HSEARCH-381 Project: Hibernate Search Issue Type: Bug Reporter: Mario I use the FieldBridge and the method set is not in the correct form. set(String name, Object value, Document document, LuceneOptions options) compiler error means i should use set(String name, Object value, Document document, Store store, Index index, Float valueF) What i make wrong? -- 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, 6 months

2
2
0 / 0

[Hibernate-JIRA] Created: (BVAL-164) Validation.byProvider now accept the provider implementation class

by Emmanuel Bernard (JIRA)

Validation.byProvider now accept the provider implementation class ------------------------------------------------------------------ Key: BVAL-164 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-164 Project: Bean Validation Issue Type: Improvement Components: spec-general Reporter: Emmanuel Bernard Fix For: 1.0 final also simplifies the contract between the bootstrap module and the providers -- 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, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-3445) Single Table Inheritence Broken for non table-unique keys

by Todd Tidwell (JIRA)

Single Table Inheritence Broken for non table-unique keys --------------------------------------------------------- Key: HHH-3445 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-3445 Project: Hibernate3 Issue Type: Bug Environment: Hibernate Core: 3.2.6.ga Hibernate Annotations: 3.3.1.ga Hibernate EntityManager: 3.3.2.ga DB2 Linux 9.1 Reporter: Todd Tidwell I have an interesting mapping case that is causing me some very odd low-level errors. In this particular case, I'm working with a table that contains multiple objects and I can use a DiscriminatorColumn to differentiate. However, the "primary key" for the child objects is not guaranteed to be uniqe table-wide. For example, DiscriminatorColumn value '013' may have a unique-key value of 'A', DiscriminatorColumn '014' may have the same unique-key value. To map this, I created a base class, gave it the DiscriminatorColumn annotation, and then extended it with my various types. Here are the classes: @Entity @Table(name="WTTBLE") @DiscriminatorColumn(name="PTBLE") public abstract class MetaData { @Id @Basic(fetch=FetchType.EAGER) @Column(name="PCODE", nullable=false, insertable=false, updatable=false) private String code = null; @Basic(fetch=FetchType.EAGER) @Column(name="DEF", nullable=false, insertable=false, updatable=false) private String value = null; .... } @Entity @DiscriminatorValue(value = "015") public class AddressType extends MetaData { // No fields here, they're all mapped in MetaData } @Entity @DiscriminatorValue(value = "016") public class CustomerType extends MetaData { // No fields here, they're all mapped in MetaData } Now, this works great until they both have the same value for the "code" property. At that point, I get the following logging and exception: org.hibernate.impl.SessionImpl - initializing proxy: [com.wiley.permissions.domain.persistence.wintouch.metadata.AddressType#A] .... org.hibernate.event.def.DefaultLoadEventListener - load request found matching entity in context, but the matched entity was of an inconsistent return type; returning null .... javax.persistence.EntityNotFoundException: Unable to find test.AddressType with id A at org.hibernate.ejb.Ejb3Configuration$Ejb3EntityNotFoundDelegate.handleEntityNotFound(Ejb3Configuration.java:107) at org.hibernate.proxy.AbstractLazyInitializer.checkTargetState(AbstractLazyInitializer.java:79) at org.hibernate.proxy.AbstractLazyInitializer.initialize(AbstractLazyInitializer.java:68) at org.hibernate.proxy.AbstractLazyInitializer.getImplementation(AbstractLazyInitializer.java:111) at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.invoke(CGLIBLazyInitializer.java:150) at test.AddressType$$EnhancerByCGLIB$$16d4c983.getValue(<generated>) After some serious research, I found that org.hibernate.engine.StatefulPersistenceContext is returning the wrong object from it's getEntity method. It's returning a CustomerType object, which was added to the session's cache after the address type. On furthur examination, this seems to be because org.hibernate.engine.EntityKey.equals() is returning the same value for both objects. EntityKey's code for lines 95 -99 is: public boolean equals(Object other) { EntityKey otherKey = (EntityKey) other; return otherKey.rootEntityName.equals(this.rootEntityName) && identifierType.isEqual(otherKey.identifier, this.identifier, entityMode, factory); } Examination of the values of EntityKey for my objects show that rootEntityName for both objects is test.MetaData. That means that this method is going to return true. That, in turn, means that StatefulPersistenceContext's entitiesByKey HashMap is going to return the first one that equals the one passed into the get() method. -- 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, 6 months

2
3
0 / 0

[Hibernate-JIRA] Created: (BVAL-163) Add support for constraint payload

by Emmanuel Bernard (JIRA)

Add support for constraint payload ---------------------------------- Key: BVAL-163 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-163 Project: Bean Validation Issue Type: New Feature Components: spec-general Affects Versions: 1.0 proposed final draft Reporter: Emmanuel Bernard Fix For: 1.0 final -- 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, 6 months

1
1
0 / 0

[Hibernate-JIRA] Created: (BVAL-162) Move metadata classes to the metadata package (BeanDescriptor, ElementDescriptor, PropertyDescriptor, ConstraintDescriptor)

by Emmanuel Bernard (JIRA)

Move metadata classes to the metadata package (BeanDescriptor, ElementDescriptor, PropertyDescriptor, ConstraintDescriptor) --------------------------------------------------------------------------------------------------------------------------- Key: BVAL-162 URL: http://opensource.atlassian.com/projects/hibernate/browse/BVAL-162 Project: Bean Validation Issue Type: Improvement Components: spec-general Affects Versions: 1.0 proposed final draft Reporter: Emmanuel Bernard Fix For: 1.0 final -- 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, 6 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues June 2009