[Hibernate-JIRA] Commented: (HHH-1889) LockMode.UPGRADE not applied in all cases for SQL Server / Sybase
by Steve Finch (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1889?page=c... ]
Steve Finch commented on HHH-1889:
----------------------------------
You are correct. The Syntax is "from table_name [ [AS] table_alias ] [ WITH ( <table_hint> [,...n]) ]".
> LockMode.UPGRADE not applied in all cases for SQL Server / Sybase
> -----------------------------------------------------------------
>
> Key: HHH-1889
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1889
> Project: Hibernate3
> Type: Bug
> Components: core
> Versions: 3.2.0.cr2, 3.2.0.cr3
> Environment: Windows XP, Hibernate 3.2.cr3
> Reporter: Matthias Germann
> Assignee: Steve Ebersole
> Fix For: 3.2.2
> Attachments: AbstractEntityJoinWalker.java.patch, SQLServerDialect.applyLocks.patch
>
>
> Passing a LockMode parameter to the get(), load() or refresh() method of the Session class has no effect on MS SQL Server.
> The statement
> session.load(ProcessInstance.class, 33l, LockMode.UPGRADE)
> produces this SQL Statement with the SQLServerDialect:
> select
> processins0_.ID_ as ID1_20_0_,
> processins0_.VERSION_ as VERSION2_20_0_,
> processins0_.START_ as START3_20_0_,
> processins0_.END_ as END4_20_0_,
> processins0_.ISSUSPENDED_ as ISSUSPEN5_20_0_,
> processins0_.PROCESSDEFINITION_ as PROCESSD6_20_0_,
> processins0_.ROOTTOKEN_ as ROOTTOKEN7_20_0_,
> processins0_.SUPERPROCESSTOKEN_ as SUPERPRO8_20_0_
> from
> JBPM_PROCESSINSTANCE processins0_
> where
> processins0_.ID_=?
> This Statement does not contain the requested locking hint. The FROM claus should look like this:
> from JBPM_PROCESSINSTANCE processins0_ with (updlock, rowlock)
> The OracleDialect produces a correct statement with a FOR UPDATE clause
> select
> processins0_.ID_ as ID1_20_0_,
> processins0_.VERSION_ as VERSION2_20_0_,
> processins0_.START_ as START3_20_0_,
> processins0_.END_ as END4_20_0_,
> processins0_.ISSUSPENDED_ as ISSUSPEN5_20_0_,
> processins0_.PROCESSDEFINITION_ as PROCESSD6_20_0_,
> processins0_.ROOTTOKEN_ as ROOTTOKEN7_20_0_,
> processins0_.SUPERPROCESSTOKEN_ as SUPERPRO8_20_0_
> from
> JBPM_PROCESSINSTANCE processins0_
> where
> processins0_.ID_=? for update
> The lock() method works correctly.
> IMHO, the problem is that only the SimpleSelect class uses the appendLockHint() method of the Dialect class. The Select class does not seam to use the appendLockHint() method.
--
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, 4 months
[Hibernate-JIRA] Commented: (HHH-1889) LockMode.UPGRADE not applied in all cases for SQL Server / Sybase
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1889?page=c... ]
Steve Ebersole commented on HHH-1889:
-------------------------------------
I ended up needing to make a few changes to your patch, nothing to major:
1) StringBuffer#indexOf is JDK 1.4 specific, so I ended up writing another way to perform this replacement which will work with 1.3
2) I actually ended up overriding Dialect#applyLocksToSql in the SybaseDialect instead since both use the same approach of lock-hints and because SQLServerDialect extends SybaseDialect
> LockMode.UPGRADE not applied in all cases for SQL Server / Sybase
> -----------------------------------------------------------------
>
> Key: HHH-1889
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1889
> Project: Hibernate3
> Type: Bug
> Components: core
> Versions: 3.2.0.cr2, 3.2.0.cr3
> Environment: Windows XP, Hibernate 3.2.cr3
> Reporter: Matthias Germann
> Assignee: Steve Ebersole
> Fix For: 3.2.2
> Attachments: AbstractEntityJoinWalker.java.patch, SQLServerDialect.applyLocks.patch
>
>
> Passing a LockMode parameter to the get(), load() or refresh() method of the Session class has no effect on MS SQL Server.
> The statement
> session.load(ProcessInstance.class, 33l, LockMode.UPGRADE)
> produces this SQL Statement with the SQLServerDialect:
> select
> processins0_.ID_ as ID1_20_0_,
> processins0_.VERSION_ as VERSION2_20_0_,
> processins0_.START_ as START3_20_0_,
> processins0_.END_ as END4_20_0_,
> processins0_.ISSUSPENDED_ as ISSUSPEN5_20_0_,
> processins0_.PROCESSDEFINITION_ as PROCESSD6_20_0_,
> processins0_.ROOTTOKEN_ as ROOTTOKEN7_20_0_,
> processins0_.SUPERPROCESSTOKEN_ as SUPERPRO8_20_0_
> from
> JBPM_PROCESSINSTANCE processins0_
> where
> processins0_.ID_=?
> This Statement does not contain the requested locking hint. The FROM claus should look like this:
> from JBPM_PROCESSINSTANCE processins0_ with (updlock, rowlock)
> The OracleDialect produces a correct statement with a FOR UPDATE clause
> select
> processins0_.ID_ as ID1_20_0_,
> processins0_.VERSION_ as VERSION2_20_0_,
> processins0_.START_ as START3_20_0_,
> processins0_.END_ as END4_20_0_,
> processins0_.ISSUSPENDED_ as ISSUSPEN5_20_0_,
> processins0_.PROCESSDEFINITION_ as PROCESSD6_20_0_,
> processins0_.ROOTTOKEN_ as ROOTTOKEN7_20_0_,
> processins0_.SUPERPROCESSTOKEN_ as SUPERPRO8_20_0_
> from
> JBPM_PROCESSINSTANCE processins0_
> where
> processins0_.ID_=? for update
> The lock() method works correctly.
> IMHO, the problem is that only the SimpleSelect class uses the appendLockHint() method of the Dialect class. The Select class does not seam to use the appendLockHint() method.
--
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, 4 months
[Hibernate-JIRA] Updated: (HHH-1889) LockMode.UPGRADE not applied in all cases for SQL Server / Sybase
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1889?page=all ]
Steve Ebersole updated HHH-1889:
--------------------------------
Summary: LockMode.UPGRADE not applied in all cases for SQL Server / Sybase (was: LockMode.UPGRADE not applied in all cases for SQL Server)
> LockMode.UPGRADE not applied in all cases for SQL Server / Sybase
> -----------------------------------------------------------------
>
> Key: HHH-1889
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1889
> Project: Hibernate3
> Type: Bug
> Components: core
> Versions: 3.2.0.cr2, 3.2.0.cr3
> Environment: Windows XP, Hibernate 3.2.cr3
> Reporter: Matthias Germann
> Assignee: Steve Ebersole
> Fix For: 3.2.2
> Attachments: AbstractEntityJoinWalker.java.patch, SQLServerDialect.applyLocks.patch
>
>
> Passing a LockMode parameter to the get(), load() or refresh() method of the Session class has no effect on MS SQL Server.
> The statement
> session.load(ProcessInstance.class, 33l, LockMode.UPGRADE)
> produces this SQL Statement with the SQLServerDialect:
> select
> processins0_.ID_ as ID1_20_0_,
> processins0_.VERSION_ as VERSION2_20_0_,
> processins0_.START_ as START3_20_0_,
> processins0_.END_ as END4_20_0_,
> processins0_.ISSUSPENDED_ as ISSUSPEN5_20_0_,
> processins0_.PROCESSDEFINITION_ as PROCESSD6_20_0_,
> processins0_.ROOTTOKEN_ as ROOTTOKEN7_20_0_,
> processins0_.SUPERPROCESSTOKEN_ as SUPERPRO8_20_0_
> from
> JBPM_PROCESSINSTANCE processins0_
> where
> processins0_.ID_=?
> This Statement does not contain the requested locking hint. The FROM claus should look like this:
> from JBPM_PROCESSINSTANCE processins0_ with (updlock, rowlock)
> The OracleDialect produces a correct statement with a FOR UPDATE clause
> select
> processins0_.ID_ as ID1_20_0_,
> processins0_.VERSION_ as VERSION2_20_0_,
> processins0_.START_ as START3_20_0_,
> processins0_.END_ as END4_20_0_,
> processins0_.ISSUSPENDED_ as ISSUSPEN5_20_0_,
> processins0_.PROCESSDEFINITION_ as PROCESSD6_20_0_,
> processins0_.ROOTTOKEN_ as ROOTTOKEN7_20_0_,
> processins0_.SUPERPROCESSTOKEN_ as SUPERPRO8_20_0_
> from
> JBPM_PROCESSINSTANCE processins0_
> where
> processins0_.ID_=? for update
> The lock() method works correctly.
> IMHO, the problem is that only the SimpleSelect class uses the appendLockHint() method of the Dialect class. The Select class does not seam to use the appendLockHint() method.
--
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, 4 months
[Hibernate-JIRA] Commented: (HHH-1889) LockMode.UPGRADE not applied in all cases for SQL Server
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1889?page=c... ]
Steve Ebersole commented on HHH-1889:
-------------------------------------
No worries. I do not use eclipse and so I have no idea.
Just so I understand the correct syntax here... Say I have a query like 'select abc from xyz x' and want to apply a lock hint. The correct syntax for that is 'select abc from xyz x with (updlock, rowlock)'. Correct? Specifically the hint comes after the alias?
> LockMode.UPGRADE not applied in all cases for SQL Server
> --------------------------------------------------------
>
> Key: HHH-1889
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1889
> Project: Hibernate3
> Type: Bug
> Components: core
> Versions: 3.2.0.cr2, 3.2.0.cr3
> Environment: Windows XP, Hibernate 3.2.cr3
> Reporter: Matthias Germann
> Assignee: Steve Ebersole
> Fix For: 3.2.2
> Attachments: AbstractEntityJoinWalker.java.patch, SQLServerDialect.applyLocks.patch
>
>
> Passing a LockMode parameter to the get(), load() or refresh() method of the Session class has no effect on MS SQL Server.
> The statement
> session.load(ProcessInstance.class, 33l, LockMode.UPGRADE)
> produces this SQL Statement with the SQLServerDialect:
> select
> processins0_.ID_ as ID1_20_0_,
> processins0_.VERSION_ as VERSION2_20_0_,
> processins0_.START_ as START3_20_0_,
> processins0_.END_ as END4_20_0_,
> processins0_.ISSUSPENDED_ as ISSUSPEN5_20_0_,
> processins0_.PROCESSDEFINITION_ as PROCESSD6_20_0_,
> processins0_.ROOTTOKEN_ as ROOTTOKEN7_20_0_,
> processins0_.SUPERPROCESSTOKEN_ as SUPERPRO8_20_0_
> from
> JBPM_PROCESSINSTANCE processins0_
> where
> processins0_.ID_=?
> This Statement does not contain the requested locking hint. The FROM claus should look like this:
> from JBPM_PROCESSINSTANCE processins0_ with (updlock, rowlock)
> The OracleDialect produces a correct statement with a FOR UPDATE clause
> select
> processins0_.ID_ as ID1_20_0_,
> processins0_.VERSION_ as VERSION2_20_0_,
> processins0_.START_ as START3_20_0_,
> processins0_.END_ as END4_20_0_,
> processins0_.ISSUSPENDED_ as ISSUSPEN5_20_0_,
> processins0_.PROCESSDEFINITION_ as PROCESSD6_20_0_,
> processins0_.ROOTTOKEN_ as ROOTTOKEN7_20_0_,
> processins0_.SUPERPROCESSTOKEN_ as SUPERPRO8_20_0_
> from
> JBPM_PROCESSINSTANCE processins0_
> where
> processins0_.ID_=? for update
> The lock() method works correctly.
> IMHO, the problem is that only the SimpleSelect class uses the appendLockHint() method of the Dialect class. The Select class does not seam to use the appendLockHint() method.
--
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, 4 months
[Hibernate-JIRA] Commented: (HHH-1889) LockMode.UPGRADE not applied in all cases for SQL Server
by Steve Finch (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1889?page=c... ]
Steve Finch commented on HHH-1889:
----------------------------------
Sorry 'bout that. I agree with you that relative paths would be correct. It would be great if the SVN plugin for Eclipse did that automatically.
I wonder how I got it to do that?
> LockMode.UPGRADE not applied in all cases for SQL Server
> --------------------------------------------------------
>
> Key: HHH-1889
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1889
> Project: Hibernate3
> Type: Bug
> Components: core
> Versions: 3.2.0.cr2, 3.2.0.cr3
> Environment: Windows XP, Hibernate 3.2.cr3
> Reporter: Matthias Germann
> Assignee: Steve Ebersole
> Fix For: 3.2.2
> Attachments: AbstractEntityJoinWalker.java.patch, SQLServerDialect.applyLocks.patch
>
>
> Passing a LockMode parameter to the get(), load() or refresh() method of the Session class has no effect on MS SQL Server.
> The statement
> session.load(ProcessInstance.class, 33l, LockMode.UPGRADE)
> produces this SQL Statement with the SQLServerDialect:
> select
> processins0_.ID_ as ID1_20_0_,
> processins0_.VERSION_ as VERSION2_20_0_,
> processins0_.START_ as START3_20_0_,
> processins0_.END_ as END4_20_0_,
> processins0_.ISSUSPENDED_ as ISSUSPEN5_20_0_,
> processins0_.PROCESSDEFINITION_ as PROCESSD6_20_0_,
> processins0_.ROOTTOKEN_ as ROOTTOKEN7_20_0_,
> processins0_.SUPERPROCESSTOKEN_ as SUPERPRO8_20_0_
> from
> JBPM_PROCESSINSTANCE processins0_
> where
> processins0_.ID_=?
> This Statement does not contain the requested locking hint. The FROM claus should look like this:
> from JBPM_PROCESSINSTANCE processins0_ with (updlock, rowlock)
> The OracleDialect produces a correct statement with a FOR UPDATE clause
> select
> processins0_.ID_ as ID1_20_0_,
> processins0_.VERSION_ as VERSION2_20_0_,
> processins0_.START_ as START3_20_0_,
> processins0_.END_ as END4_20_0_,
> processins0_.ISSUSPENDED_ as ISSUSPEN5_20_0_,
> processins0_.PROCESSDEFINITION_ as PROCESSD6_20_0_,
> processins0_.ROOTTOKEN_ as ROOTTOKEN7_20_0_,
> processins0_.SUPERPROCESSTOKEN_ as SUPERPRO8_20_0_
> from
> JBPM_PROCESSINSTANCE processins0_
> where
> processins0_.ID_=? for update
> The lock() method works correctly.
> IMHO, the problem is that only the SimpleSelect class uses the appendLockHint() method of the Dialect class. The Select class does not seam to use the appendLockHint() method.
--
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, 4 months
[Hibernate-JIRA] Commented: (HHH-1889) LockMode.UPGRADE not applied in all cases for SQL Server
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1889?page=c... ]
Steve Ebersole commented on HHH-1889:
-------------------------------------
In the future it would be great if the patches were not based on absolute paths, but rather paths relative to the project structure....
> LockMode.UPGRADE not applied in all cases for SQL Server
> --------------------------------------------------------
>
> Key: HHH-1889
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1889
> Project: Hibernate3
> Type: Bug
> Components: core
> Versions: 3.2.0.cr2, 3.2.0.cr3
> Environment: Windows XP, Hibernate 3.2.cr3
> Reporter: Matthias Germann
> Assignee: Steve Ebersole
> Fix For: 3.2.2
> Attachments: AbstractEntityJoinWalker.java.patch, SQLServerDialect.applyLocks.patch
>
>
> Passing a LockMode parameter to the get(), load() or refresh() method of the Session class has no effect on MS SQL Server.
> The statement
> session.load(ProcessInstance.class, 33l, LockMode.UPGRADE)
> produces this SQL Statement with the SQLServerDialect:
> select
> processins0_.ID_ as ID1_20_0_,
> processins0_.VERSION_ as VERSION2_20_0_,
> processins0_.START_ as START3_20_0_,
> processins0_.END_ as END4_20_0_,
> processins0_.ISSUSPENDED_ as ISSUSPEN5_20_0_,
> processins0_.PROCESSDEFINITION_ as PROCESSD6_20_0_,
> processins0_.ROOTTOKEN_ as ROOTTOKEN7_20_0_,
> processins0_.SUPERPROCESSTOKEN_ as SUPERPRO8_20_0_
> from
> JBPM_PROCESSINSTANCE processins0_
> where
> processins0_.ID_=?
> This Statement does not contain the requested locking hint. The FROM claus should look like this:
> from JBPM_PROCESSINSTANCE processins0_ with (updlock, rowlock)
> The OracleDialect produces a correct statement with a FOR UPDATE clause
> select
> processins0_.ID_ as ID1_20_0_,
> processins0_.VERSION_ as VERSION2_20_0_,
> processins0_.START_ as START3_20_0_,
> processins0_.END_ as END4_20_0_,
> processins0_.ISSUSPENDED_ as ISSUSPEN5_20_0_,
> processins0_.PROCESSDEFINITION_ as PROCESSD6_20_0_,
> processins0_.ROOTTOKEN_ as ROOTTOKEN7_20_0_,
> processins0_.SUPERPROCESSTOKEN_ as SUPERPRO8_20_0_
> from
> JBPM_PROCESSINSTANCE processins0_
> where
> processins0_.ID_=? for update
> The lock() method works correctly.
> IMHO, the problem is that only the SimpleSelect class uses the appendLockHint() method of the Dialect class. The Select class does not seam to use the appendLockHint() method.
--
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, 4 months
[Hibernate-JIRA] Updated: (HHH-1819) Invalid SQL generated for mapping with property-ref
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1819?page=all ]
Steve Ebersole updated HHH-1819:
--------------------------------
Fix Version: 3.3
Assign To: Steve Ebersole
Priority: Minor (was: Critical)
initially scheduling this for 3.3 because my gut tells me this will need the SQL rendering changes targetted for 3.3 to resolve this issue. This may get moved up to 3.2.3 or 3.2.4 if that is found to not be the case.
> Invalid SQL generated for mapping with property-ref
> ---------------------------------------------------
>
> Key: HHH-1819
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1819
> Project: Hibernate3
> Type: Bug
> Components: query-hql
> Versions: 3.1.3
> Environment: Oracle 8.1.7
> Reporter: Jakub Mendys
> Assignee: Steve Ebersole
> Priority: Minor
> Fix For: 3.3
>
>
> Consider mappings:
> <class name="MedDRATerm" table="MBROW_MEDDRA_TERMS" mutable="false"
> batch-size="50">
> <cache usage="read-only" region="dictionary" />
> <id name="medDRATermId" type="long" column="TERM_ID">
> <generator class="assigned" />
> </id>
> <map name="termNames" table="MBROW_TERM_NAMES" lazy="true"
> batch-size="50">
> <cache usage="read-only" region="dictionary" />
> <key column="MEDDRA_CODE" property-ref="medDRACode" />
> <index column="LANGUAGE_ID"
> type="com.roche.dss.meddra.dao.type.LanguageType" />
> <element column="NAME" type="string" />
> </map>
> <property name="medDRACode" column="MEDDRA_CODE"
> type="com.roche.dss.meddra.dao.type.MedDRACodeType" />
> </class>
> <class name="MedDRATermInstance" table="MBROW_MEDDRA_TREES"
> mutable="false">
> <cache usage="read-only" region="dictionary" />
> <id name="medDRATermInstanceId" type="long" column="NODE_ID">
> <generator class="assigned" />
> </id>
> <many-to-one name="medDRATerm" class="MedDRATerm"
> column="TERM_ID" fetch="join" not-null="true" insert="false"
> update="false" />
> </class>
> and a HQL query:
> from MedDRATermInstance i where i.medDRATermInstanceId is not null and i.medDRATerm.termNames[1] like 'headache'
> Having this Hibernate will generate following SQL:
> SELECT ...
> FROM orcl_gthes.mbrow_meddra_trees meddraterm0_,
> orcl_gthes.mbrow_term_names termnames2_
> WHERE meddraterm1_.meddra_code = termnames2_.meddra_code
> AND termnames2_.language_id = 1
> AND meddraterm0_.term_id = meddraterm1_.term_id
> AND (termnames2_.NAME LIKE 'headache')
> Please note that WHERE clause refers to alias meddraterm1_ which is not mentioned in FROM section!!!!
--
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, 4 months
[Hibernate-JIRA] Updated: (HHH-1889) LockMode.UPGRADE not applied in all cases for SQL Server
by Steve Ebersole (JIRA)
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1889?page=all ]
Steve Ebersole updated HHH-1889:
--------------------------------
Summary: LockMode.UPGRADE not applied in all cases for SQL Server (was: LockMode.UPGRADE does not work for get(), load() and refresh() on SQL Server)
Fix Version: 3.2.2
Assign To: Steve Ebersole
Priority: Major (was: Critical)
> LockMode.UPGRADE not applied in all cases for SQL Server
> --------------------------------------------------------
>
> Key: HHH-1889
> URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-1889
> Project: Hibernate3
> Type: Bug
> Components: core
> Versions: 3.2.0.cr2, 3.2.0.cr3
> Environment: Windows XP, Hibernate 3.2.cr3
> Reporter: Matthias Germann
> Assignee: Steve Ebersole
> Fix For: 3.2.2
> Attachments: AbstractEntityJoinWalker.java.patch, SQLServerDialect.applyLocks.patch
>
>
> Passing a LockMode parameter to the get(), load() or refresh() method of the Session class has no effect on MS SQL Server.
> The statement
> session.load(ProcessInstance.class, 33l, LockMode.UPGRADE)
> produces this SQL Statement with the SQLServerDialect:
> select
> processins0_.ID_ as ID1_20_0_,
> processins0_.VERSION_ as VERSION2_20_0_,
> processins0_.START_ as START3_20_0_,
> processins0_.END_ as END4_20_0_,
> processins0_.ISSUSPENDED_ as ISSUSPEN5_20_0_,
> processins0_.PROCESSDEFINITION_ as PROCESSD6_20_0_,
> processins0_.ROOTTOKEN_ as ROOTTOKEN7_20_0_,
> processins0_.SUPERPROCESSTOKEN_ as SUPERPRO8_20_0_
> from
> JBPM_PROCESSINSTANCE processins0_
> where
> processins0_.ID_=?
> This Statement does not contain the requested locking hint. The FROM claus should look like this:
> from JBPM_PROCESSINSTANCE processins0_ with (updlock, rowlock)
> The OracleDialect produces a correct statement with a FOR UPDATE clause
> select
> processins0_.ID_ as ID1_20_0_,
> processins0_.VERSION_ as VERSION2_20_0_,
> processins0_.START_ as START3_20_0_,
> processins0_.END_ as END4_20_0_,
> processins0_.ISSUSPENDED_ as ISSUSPEN5_20_0_,
> processins0_.PROCESSDEFINITION_ as PROCESSD6_20_0_,
> processins0_.ROOTTOKEN_ as ROOTTOKEN7_20_0_,
> processins0_.SUPERPROCESSTOKEN_ as SUPERPRO8_20_0_
> from
> JBPM_PROCESSINSTANCE processins0_
> where
> processins0_.ID_=? for update
> The lock() method works correctly.
> IMHO, the problem is that only the SimpleSelect class uses the appendLockHint() method of the Dialect class. The Select class does not seam to use the appendLockHint() method.
--
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, 4 months