August 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Updated: (HHH-1480) JOIN precendence rules per SQL-99

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1480?page=c... ] Steve Ebersole updated HHH-1480: -------------------------------- Fix Version/s: (was: 3.5.0.Beta-1) 3.5-tmp > JOIN precendence rules per SQL-99 > --------------------------------- > > Key: HHH-1480 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1480 > Project: Hibernate Core > Issue Type: New Feature > Components: query-hql > Affects Versions: 3.1.2 > Reporter: trebor iksrazal > Assignee: Steve Ebersole > Fix For: 3.2.x, 3.3.x, 3.5 > > > In SQL-92 joins performed in the where clause (comma operator in from clause) and joins performed in the from clause (join keyword) had the same precedence. SQL-99 clarified this such that the from clause joins had higher precedence. > Hibernate currently treats these as having the same precedence. > A good explanation comes from the MySQL docs ( http://dev.mysql.com/doc/refman/5.0/en/join.html ) : > # > Previously, the comma operator (,) and JOIN both had the same precedence, so the join expression t1, t2 JOIN t3 was interpreted as ((t1, t2) JOIN t3). Now JOIN has higher precedence, so the expression is interpreted as (t1, (t2 JOIN t3)). This change affects statements that use an ON clause, because that clause can refer only to columns in the operands of the join, and the change in precedence changes interpretation of what those operands are. > Example: > CREATE TABLE t1 (i1 INT, j1 INT); > CREATE TABLE t2 (i2 INT, j2 INT); > CREATE TABLE t3 (i3 INT, j3 INT); > INSERT INTO t1 VALUES(1,1); > INSERT INTO t2 VALUES(1,1); > INSERT INTO t3 VALUES(1,1); > SELECT * FROM t1, t2 JOIN t3 ON (t1.i1 = t3.i3); > Previously, the SELECT was legal due to the implicit grouping of t1,t2 as (t1,t2). Now the JOIN takes precedence, so the operands for the ON clause are t2 and t3. Because t1.i1 is not a column in either of the operands, the result is an Unknown column 't1.i1' in 'on clause' error. To allow the join to be processed, group the first two tables explicitly with parentheses so that the operands for the ON clause are (t1,t2) and t3: > SELECT * FROM (t1, t2) JOIN t3 ON (t1.i1 = t3.i3); > Alternatively, avoid the use of the comma operator and use JOIN instead: > SELECT * FROM t1 JOIN t2 JOIN t3 ON (t1.i1 = t3.i3); > This change also applies to statements that mix the comma operator with INNER JOIN, CROSS JOIN, LEFT JOIN, and RIGHT JOIN, all of which now have higher precedence than the comma operator. -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1907) offload metadata information from ComponentType to SessionFactory

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1907?page=c... ] Steve Ebersole updated HHH-1907: -------------------------------- Fix Version/s: (was: 3.5.0.Beta-1) 3.5-tmp > offload metadata information from ComponentType to SessionFactory > ----------------------------------------------------------------- > > Key: HHH-1907 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1907 > Project: Hibernate Core > Issue Type: Improvement > Components: core > Reporter: Steve Ebersole > Assignee: Steve Ebersole > Fix For: 3.5 > > > Specifically, we need to move all the code directly dealing with property-access, instantiation, etc out of here. So where do we move it? Well, EntityType for example moves this stuff off to the persisters; the type then just looks up the persister when needed. Not sure we actually need a persister per-se for handling components; perhaps just ComponentMetamodel is enough... > Why is this important? Well the way ComponentType is currently structured leads to the need for certain configuration properties to be classloader scoped (static on Environment) instead of SessionFactory scoped. This is painful for two in particular: 1) whether to use reflection optimization and 2) bytecode provider. > Also, this change should allow us to cleanup how property accessors are built -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1851) relax special handling of 'id' property

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1851?page=c... ] Steve Ebersole updated HHH-1851: -------------------------------- Fix Version/s: (was: 3.5.0.Beta-1) 3.5-tmp > relax special handling of 'id' property > --------------------------------------- > > Key: HHH-1851 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1851 > Project: Hibernate Core > Issue Type: Improvement > Components: query-hql > Environment: independent, all versions all databases. > Reporter: Gunther Schadow > Assignee: Steve Ebersole > Fix For: 3.5 > > Attachments: IdClassAndAnotherPropertyNamedId.zip > > > Hibernate has long treated 'id' in a special manner in HQL and Criteria queries. The drawback to this has always been that it effectively means users cannot define non-identifier properties named id and refer to those properties in HQL/Criteria queries. > Thus, I will change this such that: > (1) 'id' can still be used to refer to the identifier property, whatever the property's actual name, as long as the entity does not define a non-identitifer property named id. > (2) if the entity defines a non-identifier property named 'id', using 'id' in HQL or Criteria queries will refer to this non-identifier property; users would need to refer to the identifier property by its actual name. > FYI, the original reason for this feature was to support entity's which did not define an identifier property at all (users were responsible for managing the ids seperately. That feature was never really recommended and has been deprecated since early in the 3.x development. -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1824) Write an Java Agent to avoid the build time enhancement operation

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1824?page=c... ] Steve Ebersole updated HHH-1824: -------------------------------- Fix Version/s: (was: 3.5.0.Beta-1) 3.5-tmp > Write an Java Agent to avoid the build time enhancement operation > ----------------------------------------------------------------- > > Key: HHH-1824 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1824 > Project: Hibernate Core > Issue Type: New Feature > Components: build, core > Reporter: Emmanuel Bernard > Assignee: Steve Ebersole > Priority: Minor > Fix For: 3.5 > > > requires JDK 5 -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-1724) Critieria needs to be aligned with new aggreation type rules

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1724?page=c... ] Steve Ebersole updated HHH-1724: -------------------------------- Fix Version/s: (was: 3.5.0.Beta-1) 3.5-tmp > Critieria needs to be aligned with new aggreation type rules > ------------------------------------------------------------ > > Key: HHH-1724 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1724 > Project: Hibernate Core > Issue Type: Bug > Components: core > Reporter: Max Rydahl Andersen > Assignee: Steve Ebersole > Priority: Blocker > Fix For: 3.5 > > > Criteria does not ask the dialect about the type + it does not always seem to know what the underlying field type is..... > created as blocker to make sure we either document or fix it. -- 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, 1 month

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4092) ParentChildTest#testProxyReuse regression

by Steve Ebersole (JIRA)

ParentChildTest#testProxyReuse regression ----------------------------------------- Key: HHH-4092 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4092 Project: Hibernate Core Issue Type: Bug Components: testsuite Reporter: Steve Ebersole Assignee: Steve Ebersole Unfortunately with CI down I have no clue when, how, etc but currently 2 tests on ParentChildTest are now failing (see also HHH-3852). This issue is for the testProxyReuse() test method. Somehow a Glarch instance is hanging around unexpectedly after all the deletes are performed and causes assertEquals( 2, doDelete( s, "from java.lang.Object" ) ) to fail (the result is 3). Temporarily marking this (along with HHH-3852) as FailureExpected to move forward with 3.5.0.Beta-1 -- 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, 1 month

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4091) HQLTest#testDuplicateImplicitJoinInSelect

by Steve Ebersole (JIRA)

HQLTest#testDuplicateImplicitJoinInSelect ----------------------------------------- Key: HHH-4091 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4091 Project: Hibernate Core Issue Type: Bug Components: testsuite Reporter: Steve Ebersole Assignee: Steve Ebersole An assertion in HQLTest#testDuplicateImplicitJoinInSelect is currently incorrect, because the classic translator does not handle it correctly: select an.mother.bodyWeight from Animal an join an.mother m where an.mother.bodyWeight > 10 The explicit join (join an.mother m) and the implicit join (an.mother.bodyWeight ) should result in separate SQL joins. The classic translator is using the same SQL join for all. -- 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, 1 month

1
2
0 / 0

[Hibernate-JIRA] Created: (HV-205) ValidationRequirementTest#testIgnoreStaticFieldsAndProperties I would disable this test, WDYT

by Emmanuel Bernard (JIRA)

ValidationRequirementTest#testIgnoreStaticFieldsAndProperties I would disable this test, WDYT --------------------------------------------------------------------------------------------- Key: HV-205 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-205 Project: Hibernate Validator Issue Type: Sub-task Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik -- 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, 1 month

2
3
0 / 0

[Hibernate-JIRA] Created: (HV-202) BootstrapTest#testCustomMessageInterpolatorViaConfiguration is not testing via configuration but via validator context (ie like testCustomMessageInterpolatorViaValidatorContext)

by Emmanuel Bernard (JIRA)

BootstrapTest#testCustomMessageInterpolatorViaConfiguration is not testing via configuration but via validator context (ie like testCustomMessageInterpolatorViaValidatorContext) --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: HV-202 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-202 Project: Hibernate Validator Issue Type: Sub-task Reporter: Emmanuel Bernard Assignee: Hardy Ferentschik -- 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, 1 month

2
2
0 / 0

[Hibernate-JIRA] Created: (HV-191) JPA 2 Dependency

by Stephan Bublava (JIRA)

JPA 2 Dependency ---------------- Key: HV-191 URL: http://opensource.atlassian.com/projects/hibernate/browse/HV-191 Project: Hibernate Validator Issue Type: Bug Affects Versions: 4.0.0.Beta2 Reporter: Stephan Bublava Hibernate Validator 4 Beta 2 depends on JPA 2. It would be great, if it remained compatible with version 1. In addition the dependency is declared a using non-standard group and package name: <groupId>org.hibernate.java-persistence</groupId> <artifactId>jpa-api</artifactId> instead of: <groupId>javax.persistence</groupId> <artifactId>persistence-api</artifactId> Somehow this breaks my build - "mvn test" works, but "mvn site" fails with java.lang.NoSuchMethodError: javax.persistence.Persistence.getPersistenceUtil() -- 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, 1 month

2
4
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues August 2009