The following comment has been added to this issue:
Author: Gavin King
Created: Mon, 23 Jun 2003 9:11 AM
Body:
SQL server does not support SELECT ... FOR UPDATE. On the other hand, Hibernate should not have *tried* to use FOR UPDATE with SQL server. Might be a problem in the dialect.
The message in Oracle only occurs *sometimes* when you do something Oracle doesn't like.
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-149
Here is an overview of the issue:
---------------------------------------------------------------------
Key: HB-149
Summary: when trying to set an update lock on an object I get a crash in Oracle and SQL Server
Type: Bug
Status: Unassigned
Priority: Major
Project: Hibernate2
Versions:
2.0 final
Assignee:
Reporter: Hrituc Ovidiu
Created: Mon, 23 Jun 2003 5:21 AM
Updated: Mon, 23 Jun 2003 5:21 AM
Environment: W2k, OC4J, Oracle 9i, Sql Server 2k
Description:
when trying to do this:
dac = (MyClass)session.load(MyClass.class,Clazz,LockMode.UPGRADE );
or this
dac = (MyClass)session.load(MyClass.class);
session.lock(dac,LockMode.UPGRADE );
in a stateless session EJB I get with SQL Server:
"FOR UPDATE clause allowed only for DECLARE CURSOR."
and with Oracle: "Could not load object: ORA-01002: fetch out of sequence"
---------------------------------------------------------------------
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/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
|
