October 2009 - hibernate-issues - Jboss List Archives

[Hibernate-JIRA] Created: (HHH-4121) DB2 Projection with paging and ordering generates illegal SQL. sqlerror -206

by Nick Wiedenbrück (JIRA)

DB2 Projection with paging and ordering generates illegal SQL. sqlerror -206 ---------------------------------------------------------------------------- Key: HHH-4121 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4121 Project: Hibernate Core Issue Type: Bug Affects Versions: 3.2.6 Reporter: Nick Wiedenbrück We're using DB2 8.1 and we have a projection query with paging and sorting. The generated SQL looks like this: select * from ( select rownumber() over(order by y5_ asc) as rownumber_, [...] , this_.beginn as y5_, [...] from [...] order by y5_ asc ) as temp_ where rownumber_ <= ? This results in an error, because the query uses the alias in the over() part. If instead this_.beginn would be used it would possibly work. -- 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, 2 months

1
1
0 / 0

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

by Anthony Patricio (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1829?page=c... ] Anthony Patricio commented on HHH-1829: --------------------------------------- Robert, Mathieu... could you upload the svn diff please? > 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-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

15 years, 2 months

1
0
0 / 0

[Hibernate-JIRA] Commented: (HHH-1595) SQL syntax error on delete statement with subselect

by strong liu (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1595?page=c... ] strong liu commented on HHH-1595: --------------------------------- Georgios, do you have a valid test case? if so, please attach it > SQL syntax error on delete statement with subselect > --------------------------------------------------- > > Key: HHH-1595 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1595 > Project: Hibernate Core > Issue Type: Bug > Components: query-hql > Affects Versions: 3.1.3 > Environment: Hibernate 3.1.3, Oracle 10g > Reporter: Georgios Skempes > Assignee: strong liu > > After upgrading from Hibernate 3.1.2 to 3.1.3 I get an SQL syntax error for the HQL statement below. It's a bulk delete containing a subselect. The code is working for Hibernate 3.1.2 > Code between session.open() and session.close(): > ------------------------------------------------------------------------ > String queryString = "delete from Contact con where con.Id.ConpId IN (select conp.Id from con.ContactpersonSet conp where conp.ParId=4711) > Query queryObject = session.createQuery(queryString); > queryObject.executeUpdate(); > SQL code generated with Hibernate 3.1.2 (correct): > ---------------------------------------------------------------------- > delete from CONTACTS where CONP_ID in (select contactper1_.Id from CONTACTPERSONS contactper1_ where CONP_ID=contactper1_.Id and PAR_ID=4711) > SQL code generated with Hibernate 3.1.3 (error): > ----------------------------------------------------------------------- > delete from CONTACTS where CONP_ID in (select contactper1_.Id from CONTAKTPERSONS contactper1_ where contact0_.CONP_ID=contactper1_.Id and contactper1_.PAR_ID=?) > Error log: > ----------------------------------------------------------------------- > [08:43:01,591] (ERROR) org.hibernate.util.JDBCExceptionReporter.logExceptions(JDBCExceptionReporter.java:72) - ORA-00904: "CONTACT0_"."CONP_ID": invalid identifier -- 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, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (ANN-833) Integrate new long string and binary property types in core with annotations

by Gail Badner (JIRA)

Integrate new long string and binary property types in core with annotations ------------------------------------------------------------------------------ Key: ANN-833 URL: http://opensource.atlassian.com/projects/hibernate/browse/ANN-833 Project: Hibernate Annotations Issue Type: Improvement Reporter: Gail Badner Assignee: Emmanuel Bernard Fix For: 3.5 The following types have been added to core by HHH-3892: - ImageType (image) - MaterializedBlobType (materialized_clob) - MaterializedClobType (materialized_blob) Annotations has its own version of some (or all?) of these types. Annotations should start using these new types instead. -- 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, 2 months

3
5
0 / 0

[Hibernate-JIRA] Created: (HHH-4105) SessionFactory mispells method to obtain fetch profile definition

by Paul Benedict (JIRA)

SessionFactory mispells method to obtain fetch profile definition ----------------------------------------------------------------- Key: HHH-4105 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4105 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.5.0.Beta-1 Reporter: Paul Benedict Line 255: containsFetchProfileDefition Definition is mispelled. -- 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, 2 months

2
2
0 / 0

[Hibernate-JIRA] Resolved: (HHH-4382) @ManyToOne not working wth @Formula

by Emmanuel Bernard (JIRA)

[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-4382?page=c... ] Emmanuel Bernard resolved HHH-4382. ----------------------------------- Resolution: Fixed Fix Version/s: 3.5 > @ManyToOne not working wth @Formula > ----------------------------------- > > Key: HHH-4382 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4382 > Project: Hibernate Core > Issue Type: Improvement > Components: annotations > Environment: Hibernate 3.1, PostgreSQL 8.1.1 > Reporter: Steve Ebersole > Fix For: 3.5 > > > This type of mapping fails: > @ManyToOne > @Formula(value="( select v_pipe_offerprice.offerprice_fk from v_pipe_offerprice where v_pipe_offerprice.id = id )") > public OfferPrice getOfferPrice() { return offerPrice; } > While the following mapping works as expected: > <class name="Pipe" table="t_pipe"> > ... > <many-to-one name="offerPrice" > class="pipetracker.model.price.OfferPrice" > formula="( select v_pipe_offerprice.offerprice_fk > from v_pipe_offerprice > where v_pipe_offerprice.id = id )"/> > ... > </class> > This is not being treated as a formula because the generated SQL included a referece to the field pipe.offerprice_id which does not exsist because this is a virtual column calculated from a view. -- 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, 2 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4484) When JBoss Cache is configured for INVALIDATION don't send cluster message on entity insert

by Brian Stansberry (JIRA)

When JBoss Cache is configured for INVALIDATION don't send cluster message on entity insert ------------------------------------------------------------------------------------------- Key: HHH-4484 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4484 Project: Hibernate Core Issue Type: Improvement Components: caching (L2) Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.5 In the Hibernate/JBC integration, when EntityRegionAccessStrategy.insert is invoked and JBC is configured for INVALIDATION, the cache put should have the local-only option set. No other node is going to have this brand new entity cached, so sending out the invalidation message is a waste. This makes clustered 2nd level caching viable (i.e. performant) for a large category of entity types where it currently isn't; i.e. those that have a large number of inserts but not many updates after insert. -- 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, 3 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4475) Constants point to non-existing default JBC/JGroups config file locations

by Brian Stansberry (JIRA)

Constants point to non-existing default JBC/JGroups config file locations ------------------------------------------------------------------------- Key: HHH-4475 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4475 Project: Hibernate Core Issue Type: Bug Components: caching (L2) Affects Versions: 3.5.0.Beta-1 Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 3.5 The code for the Hibernate/JBC integration was repackaged for 3.5, but some constants used as configuration defaults are still pointing to the old packages; e.g in SharedCacheInstanceManager: public static final String DEF_JGROUPS_RESOURCE = "org/hibernate/cache/jbc2/builder/jgroups-stacks.xml"; should be "org/hibernate/cache/jbc/..." Related is the org/hibernate/cache/jbc/builder/jbc2-configs.xml file should be renamed to "jbc-configs.xml". -- 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, 3 months

1
1
0 / 0

[Hibernate-JIRA] Created: (HHH-4483) LocaleType parses locales incorrect

by Willi Schönborn (JIRA)

LocaleType parses locales incorrect ----------------------------------- Key: HHH-4483 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4483 Project: Hibernate Core Issue Type: Bug Components: core Affects Versions: 3.3.2 Environment: Version 3.3.2, MySQL 5.0 Reporter: Willi Schönborn Priority: Trivial Attachments: LocaleType.java According to Locale#toString() (see http://java.sun.com/j2se/1.4.2/docs/api/java/util/Locale.html#toString%28%29) LocaleType parses Locales wrong, if they do not contain a language. E.g.: I have new Locale("", "GB"), which according to Sun's Javadoc should produce "_GB", when calling toString(). Hibernate correctly saves this value to the db, but incorrectly restores new Locale("gb") which results in a language code instead of a country code. The StringTokenizer eats the first part, if the String starts with a _. Bugfix attached. -- 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, 3 months

1
0
0 / 0

[Hibernate-JIRA] Created: (HHH-4482) certain forms of HQL generate errors if your package names contain a sql reserved word

by Karl Palsson (JIRA)

certain forms of HQL generate errors if your package names contain a sql reserved word -------------------------------------------------------------------------------------- Key: HHH-4482 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4482 Project: Hibernate Core Issue Type: Bug Components: query-hql Affects Versions: 3.3.2, 3.2.6 Environment: oracle and hsqldb, tested both 3.3.2GA and 3.2.6GA Reporter: Karl Palsson The following queries generates the invalid sql below, if your java package name starts with a sql reserved word, but work just fine if they don't. session.createQuery("delete Usergroup where userName = :userName")... session.createQuery("delete Usergroup u where u.userName = :userName") The following sql is generated "delete is.vf.nip.provision.handlers.radius.entities.Usergroup where userName = :userName" which fails with the message: org.hibernate.hql.ast.QuerySyntaxException: unexpected token: is near line 1, column 8 If you change the query to "delete from Usergroup where userName = :userName" you get more normal looking sql like, "delete from usergroup where UserName=?" All of these forms worked when my packages didn't start with "is" I've tried to use the ClassicQueryTranslator, but my settings don't seem to take hold for that. I can work around this by changing the queries, but my package names should have no bearing on generated sql :( This is probably the same as: HHH-3213 -- 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, 3 months

1
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 October 2009