March 2007 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-2534) better error message for illegal 'collection dereference' in HQL query

by Steve Ebersole (JIRA)

better error message for illegal 'collection dereference' in HQL query ---------------------------------------------------------------------- Key: HHH-2534 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2534 Project: Hibernate3 Issue Type: Improvement Components: query-hql Reporter: Steve Ebersole Assignee: Steve Ebersole Priority: Minor Fix For: 3.2.3 Currently, when a user dereferences a collection improperly in an HQL query, a sorta cryptic error message is given which is a hold-over from the classic parser days (kept for regression testing in HQLTest). The error just says "illegal syntax near collection: ${propertyName}". Use a delegate in DotNode to allow a better error message by default, but for HQLTest to plugin a "classic" style error message generator. -- 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

17 years, 9 months

1
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2529) HQL resulting in incorrect SQL caused by ORDER BY

by Marc Luce (JIRA)

HQL resulting in incorrect SQL caused by ORDER BY ------------------------------------------------- Key: HHH-2529 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2529 Project: Hibernate3 Issue Type: Bug Components: query-hql Affects Versions: 3.2.2 Environment: hibernate-3.2.2, Sybase Adaptive Server 12.5 Reporter: Marc Luce Priority: Minor Attachments: SimpleHibernateTest.zip I have written a HQL query that retrieves a set of objects that are mapped from a parent object. The SQL that is generated from it is incorrect. I have discovered that the ORDER BY clause is causing the problem. I will include the HQL that generates the incorrect join in SQL and the HQL that generates the correct join in SQL (without an ORDER BY). The first query results in a query that returns each object 3 times. If I remove the ORDER BY clause, I will receive the correct result set, but obviously, it would be unordered. The HQL: SELECT b.loans FROM Batch AS b WHERE b.id = :id ORDER BY b.loans.loanNumber DESC The SQL that is generated: select loan2_.id as id2_, loan2_.name as name2_ from dbo.TestBatch batch0_ inner join TestMapping loans1_ on batch0_.id=loans1_.batchId inner join dbo.TestLoan loan2_ on loans1_.loanId=loan2_.id, TestMapping loans3_, dbo.TestLoan loan4_ where batch0_.id=loans3_.batchId and loans3_.loanId=loan4_.id and batch0_.id=? order by loan4_.name DESC The mapping: <class name="testHibernate.Batch" table="TestBatch" schema="dbo" dynamic-insert="true" dynamic-update="true"> <id name="id" type="java.lang.Integer" column="id" > <generator class="increment" /> </id> <property name="name" type="java.lang.String" column="name" length="80" not-null="true" /> <set name="loans" table="TestMapping"> <key column="batchId"/> <many-to-many column="loanId" unique="true" class="testHibernate.Loan" lazy="proxy"/> </set> </class> <class name="testHibernate.Loan" table="TestLoan" schema="dbo" dynamic-insert="true" dynamic-update="true"> <id name="id" type="java.lang.Integer" column="id" > <generator class="increment" /> </id> <property name="loanNumber" type="java.lang.String" column="name" length="80" not-null="true" /> </class> I will also attach a zip of my very simple eclipse project that illustrates the problem. -- 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

17 years, 9 months

2
1
0 / 0

[Hibernate-JIRA] Updated: (HHH-16) Explicit joins on unrelated classes

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-16?page=com... ] Steve Ebersole updated HHH-16: ------------------------------ Fix Version/s: (was: 3.3) antlr-rework > Explicit joins on unrelated classes > ----------------------------------- > > Key: HHH-16 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-16 > Project: Hibernate3 > Issue Type: New Feature > Components: core > Affects Versions: antlr-rework > Environment: Any > Reporter: David Lloyd > Assignee: Steve Ebersole > Fix For: antlr-rework > > > It would be nice to be able to do explicit joins on unrelated classes with HQL: > (hope this renders correctly) > select empl, phone > from org.example.Employee empl > left outer join org.example.PhoneBook phone > on phone.lastName = empl.lastName > and phone.firstName = empl.firstName > where empl.salaryGrade > 10 > Note that this would also implicity solve HB-1089 because you could list join criteria that match what Hibernate would have chosen anyway (i.e., list a many-to-one relationship as a criteria explicitly). > Syntactically this could be disambiguated from the existing join syntax because the token after "join" is a class name rather than a property name. -- 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

17 years, 9 months

1
0
0 / 0

[Hibernate-JIRA] Updated: (HHH-16) Explicit joins on unrelated classes

by Steve Ebersole (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-16?page=com... ] Steve Ebersole updated HHH-16: ------------------------------ Affects Version/s: antlr-rework > Explicit joins on unrelated classes > ----------------------------------- > > Key: HHH-16 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-16 > Project: Hibernate3 > Issue Type: New Feature > Components: core > Affects Versions: antlr-rework > Environment: Any > Reporter: David Lloyd > Assignee: Steve Ebersole > Fix For: antlr-rework > > > It would be nice to be able to do explicit joins on unrelated classes with HQL: > (hope this renders correctly) > select empl, phone > from org.example.Employee empl > left outer join org.example.PhoneBook phone > on phone.lastName = empl.lastName > and phone.firstName = empl.firstName > where empl.salaryGrade > 10 > Note that this would also implicity solve HB-1089 because you could list join criteria that match what Hibernate would have chosen anyway (i.e., list a many-to-one relationship as a criteria explicitly). > Syntactically this could be disambiguated from the existing join syntax because the token after "join" is a class name rather than a property name. -- 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

17 years, 9 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-2531) Remove "experiemental" warning from XML Mapping chapter in manual

by Chris Bredesen (JIRA)

Remove "experiemental" warning from XML Mapping chapter in manual ----------------------------------------------------------------- Key: HHH-2531 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2531 Project: Hibernate3 Issue Type: Improvement Components: documentation Affects Versions: 3.2.2 Reporter: Chris Bredesen Priority: Minor Chapter 18. XML Mapping Remove this line: "Note that this is an experimental feature in Hibernate 3.0 and is under extremely active 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

17 years, 9 months

3
2
0 / 0

[Hibernate-JIRA] Created: (HHH-2530) Filter and Join together BUG -attachments included for example of reproduction

by SK (JIRA)

Filter and Join together BUG -attachments included for example of reproduction ------------------------------------------------------------------------------ Key: HHH-2530 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2530 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.0.cr2 Environment: 3.2.0, Oracle 9 Reporter: SK Select a, b from TableA, TableB where TableA.id=TableB.id if i enable a filter, the query above works but when doing so with join it fails select a,b from TableA join TableB if i try to enable filter now, it will fail -- 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

17 years, 9 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-2526) Filter and Join together

by SK (JIRA)

Filter and Join together ------------------------ Key: HHH-2526 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2526 Project: Hibernate3 Issue Type: Improvement Components: core Affects Versions: 3.2.0.cr2 Environment: 3.2.0, Oracle 9 Reporter: SK Select a, b from TableA, TableB where TableA.id=TableB.id if i enable a filter, the query above works but when doing so with join it fails select a,b from TableA join TableB if i try to enable filter now, it will fail -- 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

17 years, 9 months

2
2
0 / 0

[Hibernate-JIRA] Created: (ANN-589) Need for clear @filter doccumentation

by vaughn preddy (JIRA)

Need for clear @filter doccumentation ------------------------------------- Key: ANN-589 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-589 Project: Hibernate Annotations Issue Type: Improvement Components: documentation Environment: N/A Reporter: vaughn preddy Limited @filter doccumentation is available. -- 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

17 years, 9 months

3
6
0 / 0

[Hibernate-JIRA] Created: (HHH-2492) Enable <generator> tag for non primary key columns that are autogenerated or is an identity

by Manoj Pallikkattil (JIRA)

Enable <generator> tag for non primary key columns that are autogenerated or is an identity ------------------------------------------------------------------------------------------- Key: HHH-2492 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2492 Project: Hibernate3 Type: New Feature Versions: 3.2.2 Environment: 3.2.2, Oracle 9i, SQL Server 2000 Reporter: Manoj Pallikkattil Currently hibenate allow <generator> tag for primary keys, i.e inside the <id> tag. It would be good if we can use the generator tag for non primary key columns also. Our current datamodel has a UUID char 32 as the primary key and ID column which is a sequence for Oracle and an Identity for SQL Server is a unique key. I could get this to work with Oracle using Parameterized User Type but I have not been able to achieve this for SQL Server since the identity column is filled on the insert. If we could use the <generator> tag inside a <property> tag this would resolve this issue. -- 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

17 years, 9 months

3
7
0 / 0

[Hibernate-JIRA] Created: (HBX-819) NullPointerException in simple case with one configuration file and two console configurations

by Francois Granade (JIRA)

NullPointerException in simple case with one configuration file and two console configurations ---------------------------------------------------------------------------------------------- Key: HBX-819 URL: http://opensource.atlassian.com/projects/hibernate/browse/HBX-819 Project: Hibernate Tools Type: Bug Components: consoleconfiguration Versions: 3.2beta8 Environment: macos, hsqldb Reporter: Francois Granade Priority: Minor I'm having an NullPointerException (See the stack below), I'm not really able to understand what triggers it (it is not completely reproducible, it seems). My setup is very simple: just one Java project, one hibernate configuration file, two console configurations, nothing else. The only thing that's a little special, is that one of the console configuration is invalid (no driver jar file defined). I'll try to describe it as precisely as possible: - I have a very simple HSQLDB server, just out-of-the box. I have created only one table with: "create table x (a varchar(255), b int)". - I created an Hibernate configuration file for the HSQLDB database using "File > New > Others", "Hibernate > Hibernate configuration file"; I specified "create a console configuration", and I gave a name to the Console Configuration, but I didn't set any other property (in particular, I did not specify the .jar file for hsqldb: so it's not a correctly defined console configuration) - Then I created a second console configuration; That time, in the 'classpath' section at the bottom, I selected 'add external jar' and added my 'hsqldb.jar'. - I can now open the HSQL DB correctly in the Hibernate Configuration view, with this second console configuration (the first one is doing an error, which is normal). - now, time to time, when I right-click on the definition of my table ('X"), and select "HQL Editor", I sometimes get the NullPointerException (but not always). here's the stack trace: !MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench". !STACK 0 java.lang.NullPointerException at java.util.TreeMap.compare(TreeMap.java:1093) at java.util.TreeMap.getEntry(TreeMap.java:347) at java.util.TreeMap.get(TreeMap.java:265) at org.hibernate.console.KnownConfigurations.find(KnownConfigurations.java:225) at org.hibernate.eclipse.console.AbstractQueryEditor.getConsoleConfiguration(AbstractQueryEditor.java:51) at org.hibernate.eclipse.console.views.DynamicSQLPreviewView.updateText(DynamicSQLPreviewView.java:137) at org.hibernate.eclipse.console.views.DynamicSQLPreviewView.setCurrentEditor(DynamicSQLPreviewView.java:130) at org.hibernate.eclipse.console.views.DynamicSQLPreviewView.hookIntoEditor(DynamicSQLPreviewView.java:114) at org.hibernate.eclipse.console.views.DynamicSQLPreviewView.access$2(DynamicSQLPreviewView.java:107) at org.hibernate.eclipse.console.views.DynamicSQLPreviewView$1.partBroughtToTop(DynamicSQLPreviewView.java:92) at org.eclipse.ui.internal.PartListenerList2$2.run(PartListenerList2.java:83) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37) at org.eclipse.core.runtime.Platform.run(Platform.java:843) at org.eclipse.ui.internal.PartListenerList2.fireEvent(PartListenerList2.java:53) at org.eclipse.ui.internal.PartListenerList2.firePartBroughtToTop(PartListenerList2.java:81) at org.eclipse.ui.internal.PartService.firePartBroughtToTop(PartService.java:90) at org.eclipse.ui.internal.WWinPartService$1.partBroughtToTop(WWinPartService.java:40) at org.eclipse.ui.internal.PartListenerList2$2.run(PartListenerList2.java: -- 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

17 years, 9 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

hibernate-issues March 2007