July 2011 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-6499) Implementation of Helper.ValueSourcesAdapter in PropertyAttributeSourceImpl does not handle null returned by XMLPropertyElement.isInsert() or isUpdate()

by Gail Badner (JIRA)

Implementation of Helper.ValueSourcesAdapter in PropertyAttributeSourceImpl does not handle null returned by XMLPropertyElement.isInsert() or isUpdate() --------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HHH-6499 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6499 Project: Hibernate Core Issue Type: Bug Components: metamodel Reporter: Gail Badner Assignee: Gail Badner Fix For: 4.0.0.next -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
4
0 / 0

[Hibernate-JIRA] Created: (HHH-2449) Lazy loading for one-to-one asociations

by jose (JIRA)

Lazy loading for one-to-one asociations --------------------------------------- Key: HHH-2449 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2449 Project: Hibernate3 Type: New Feature Components: core Versions: 3.2.2 Environment: Hibernate 3.2.2 Reporter: jose After read "Some explanations on lazy loading" and my tests I found a lossing feature in Hibernate (3.2.2). one-to-one with lazy="proxy"_____________________________________________ Hibernate ALWAYS launch selects to know if one-to-one is null or can be proxied. one-to-one with lazy="no-proxy"__________________________________________ Instrumentation allows to hibernate modify the getter to allows lazy loading on demand: * but allways initialize ALL no-proxy relations (with first getter call) -> must initialize ONLY the requested property * never auto-initialize FETCH joins, ALWAYS doit on demand (if opened session) -> must auto-initialize ONLY the FETCHED property note: Can submit a fix for this? How? NEW FEATURE: one-to-one with lazy="proxy" without multiple SELECTS______ If Hibernate adds join, for all one-to-one relations, to get the foreign-key of other tables, can check it to create a proxy or null. note: that hibernate adds joins for hierarchy, why not for one-to-one relations? This solution avoids: * 'multiple subselects' after first select * 'instrumentation' of bytecode -- 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, 8 months

3
2
0 / 0

[Hibernate-JIRA] Created: (ANN-614) @WhereJoinTable doesn't work with @ManyToOne

by Victor (JIRA)

@WhereJoinTable doesn't work with @ManyToOne -------------------------------------------- Key: ANN-614 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-614 Project: Hibernate Annotations Issue Type: Bug Affects Versions: 3.3.0.ga Reporter: Victor @ManyToOne( fetch=FetchType.LAZY ) @JoinTable(name="CATEGORY_PRODUCT", uniqueConstraints = @UniqueConstraint(columnNames = {"PDID", "CATID"}), joinColumns = @JoinColumn(name="PDID"), inverseJoinColumns = @JoinColumn(name="CATID") ) @WhereJoinTable(clause="CATMAIN=1") protected Category getMainCategory() { return mainCategory; } protected void setMainCategories(Category mainCategory) { this.mainCategory = mainCategory; } Best regards, Victor -- 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, 8 months

5
5
0 / 0

[Hibernate-JIRA] Resolved: (HHH-1780) negation of EXISTS in hql query does not work

by Strong Liu (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1780?page=c... ] Strong Liu resolved HHH-1780. ----------------------------- Resolution: Fixed Fix Version/s: 3.6.7 4.0.0.next patch applied, nice work Igor, thanks > negation of EXISTS in hql query does not work > --------------------------------------------- > > Key: HHH-1780 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1780 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2 > Reporter: Marton Papp > Assignee: Strong Liu > Fix For: 4.0.0.next, 3.6.7 > > Attachments: hibernate-HHH-1780-fix.patch, hibernate-HHH-1780-fix.patch, hibernate-HHH-1780-test.patch > > > Hello! > I think I found a bug in Hibernate, in class org.hibernate.hql.ast.HqlParser. > It is in the methtod: > public AST negateNode(AST x) > The switch lacks the node type: EXISTS. > The default negateNode() implementation in org.hibernate.hql.antlr.HqlBaseParser seems to be broken by me, since it does not actually inverts the node but returns a node that is inverted. Or, to be more exact, the negation of OR and AND types are buggy, since they seem to assume that negateNode() will change the node itself, and so they simply discard its return value. > I wish the branch for NOT was not commented out, since it would provide a workaround, but now i'm stuck. > Regards, > Marton -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] Assigned: (HHH-1780) negation of EXISTS in hql query does not work

by Strong Liu (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1780?page=c... ] Strong Liu reassigned HHH-1780: ------------------------------- Assignee: Strong Liu > negation of EXISTS in hql query does not work > --------------------------------------------- > > Key: HHH-1780 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1780 > Project: Hibernate Core > Issue Type: Bug > Affects Versions: 3.1.3, 3.2.0 cr1, 3.2.0.cr2 > Reporter: Marton Papp > Assignee: Strong Liu > Attachments: hibernate-HHH-1780-fix.patch, hibernate-HHH-1780-fix.patch, hibernate-HHH-1780-test.patch > > > Hello! > I think I found a bug in Hibernate, in class org.hibernate.hql.ast.HqlParser. > It is in the methtod: > public AST negateNode(AST x) > The switch lacks the node type: EXISTS. > The default negateNode() implementation in org.hibernate.hql.antlr.HqlBaseParser seems to be broken by me, since it does not actually inverts the node but returns a node that is inverted. Or, to be more exact, the negation of OR and AND types are buggy, since they seem to assume that negateNode() will change the node itself, and so they simply discard its return value. > I wish the branch for NOT was not commented out, since it would provide a workaround, but now i'm stuck. > Regards, > Marton -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-6485) Add support for @DiscriminatorFormula

by Hardy Ferentschik (JIRA)

Add support for @DiscriminatorFormula ------------------------------------- Key: HHH-6485 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6485 Project: Hibernate Core Issue Type: Sub-task Reporter: Hardy Ferentschik -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
3
0 / 0

[Hibernate-JIRA] Created: (HHH-6500) EntityBinding.getEntity().getSuperType() is null for subclass EntityBinding

by Gail Badner (JIRA)

EntityBinding.getEntity().getSuperType() is null for subclass EntityBinding --------------------------------------------------------------------------- Key: HHH-6500 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6500 Project: Hibernate Core Issue Type: Bug Components: metamodel Reporter: Gail Badner Fix For: 4.0.0.next For a subclass EntityBinding, EntityBinding.getSuperEntityBinding() is non-null (as expected), but EntityBinding.getEntity().getSuperType() is null. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-6497) Update AbstractEntityPersister to use AssociationAttributeBinding.getCascadeStyle()

by Gail Badner (JIRA)

Update AbstractEntityPersister to use AssociationAttributeBinding.getCascadeStyle() ----------------------------------------------------------------------------------- Key: HHH-6497 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6497 Project: Hibernate Core Issue Type: Task Components: core Reporter: Gail Badner Assignee: Gail Badner -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
3
0 / 0

[Hibernate-JIRA] Created: (HHH-6362) EntityBindingStateImpl.getOptimisticLockMode() returns org.hibernate.annotations.OptimisticLockType.ordinal()

by Gail Badner (JIRA)

EntityBindingStateImpl.getOptimisticLockMode() returns org.hibernate.annotations.OptimisticLockType.ordinal() ------------------------------------------------------------------------------------------------------------- Key: HHH-6362 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6362 Project: Hibernate Core Issue Type: Bug Components: metamodel Reporter: Gail Badner Assignee: Gail Badner Fix For: 4.0.0.next The ordinal values for org.hibernate.annotations.OptimisticLockType are not consistent with org.hibernate.engine.internal.Versioning constants, resulting in the incorrect value being returned by EntityBinding.getOptimisticLockMode(). -- 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, 8 months

2
5
0 / 0

[Hibernate-JIRA] Created: (HHH-6480) Develop component binding for new metamodel

by Steve Ebersole (JIRA)

Develop component binding for new metamodel ------------------------------------------- Key: HHH-6480 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6480 Project: Hibernate Core Issue Type: Bug Components: core, metamodel Reporter: Steve Ebersole Assignee: Steve Ebersole -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

1
1
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 July 2011