[Hibernate-issues] [Hibernate-JIRA] Updated: (HB-604) problems upgrading using a criteria with postgresql 7.4

[<leg...@at...>]

The following issue has been updated:

    Updater: Matt Ho (mailto:ma...@xt...)
       Date: Mon, 5 Jan 2004 11:51 AM
    Changes:
             Attachment changed to Account.hbm.xml
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-604&page=history

---------------------------------------------------------------------
View the issue:

  http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-604


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: HB-604
    Summary: problems upgrading using a criteria with postgresql 7.4
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Hibernate2
 Components: 
             core
   Versions:
             2.1.1

   Assignee: 
   Reporter: Matt Ho

    Created: Mon, 5 Jan 2004 11:49 AM
    Updated: Mon, 5 Jan 2004 11:51 AM
Environment: sun jdk 1.4.2_03, postgresql 7.4, hibernate 2.1.1

Description:
Using Hibernate 2.1.1 and PostgreSQL 7.4, I'm trying to use the Criteria API to do a SELECT ... FOR UPDATE on a given table. If I include a

criteria.setLockMode(LockMode.UPGRADE);


I get the following Exception

132531 [tcpConnection-8080-2] WARN util.JDBCExceptionReporter  - SQL Error: 0, SQLState: 0A000
132531 [tcpConnection-8080-2] ERROR util.JDBCExceptionReporter  - ERROR: DECLARE CURSOR ... FOR UPDATE is not supported

132531 [tcpConnection-8080-2] WARN util.JDBCExceptionReporter  - SQL Error: 0, SQLState: 0A000
132531 [tcpConnection-8080-2] ERROR util.JDBCExceptionReporter  - ERROR: DECLARE CURSOR ... FOR UPDATE is not supported


However, if I remove the criteria.setLockMode() statement, life is good. I used p6spy to check the SQL generated when the setLockMode(LockMode.UPGRADE) is used and it looks fine. I copied it into a SquirrelSQL window and the SQL executes fine. The problem appears to occur after the response comes back.

I've attached a test case that reproduces the problem.


---------------------------------------------------------------------
JIRA INFORMATION:
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.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira