Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Invalid SQL query generated starting form a Criteria containing two restrictions about class type.

Description

The hibernate criteria causes an error in DB2
Issue: the SQL query contains 2 parameters, not qualified, both named "clazz_" for the two restictions.
DB2Error: SEVERE: DB2 SQL Error: SQLCODE=-203, SQLSTATE=42702, SQLERRMC=CLAZZ_, DRIVER=3.58.82

Details are attached

Attachments

2
  • 31 Mar 2010, 03:13 PM
  • 31 Mar 2010, 11:46 AM

Activity

Brett MeyerJuly 8, 2014 at 3:11 PM

Bulk rejecting stale issues. If this is still a legitimate issue on ORM 4, feel free to comment and attach a test case. I'll address responses case-by-case. Thanks!

Brett MeyerApril 7, 2014 at 5:43 PM

In an effort to clean up, in bulk, tickets that are most likely out of date, we're transitioning all ORM 3 tickets to an "Awaiting Test Case" state. Please see http://in.relation.to/Bloggers/HibernateORMJIRAPoliciesAndCleanUpTactics for more information.

If this is still a legitimate bug in ORM 4, please provide either a test case that reproduces it or enough detail (entities, mappings, snippets, etc.) to show that it still fails on 4. If nothing is received within 3 months or so, we'll be automatically closing them.

Thank you!

Former userApril 21, 2010 at 7:31 PM

Thanks for checking!

alessandro.faraottiApril 21, 2010 at 4:24 PM

Yes the issue persists with the version 3.5.1 final

Former userApril 21, 2010 at 12:21 AM

Is this still an issue using 3.5.1?

Rejected

Details

Assignee

Reporter

Original estimate

Time tracking

No time logged16h remaining

Components

Affects versions

Priority

Created March 31, 2010 at 11:46 AM
Updated July 8, 2014 at 3:11 PM
Resolved July 8, 2014 at 3:11 PM

Flag notifications