[hibernate-issues] [Hibernate-JIRA] Resolved: (HHH-2238) SQLQuery executeUpdate doesn't respect Query.setFlushMode()

Steve Ebersole (JIRA) noreply at atlassian.com
Tue Nov 21 19:12:05 EST 2006


     [ http://opensource.atlassian.com/projects/hibernate/browse/HHH-2238?page=all ]
     
Steve Ebersole resolved HHH-2238:
---------------------------------

    Fix Version: 3.2.2
     Resolution: Fixed
      Assign To: Steve Ebersole

trunk / 3.2

> SQLQuery executeUpdate doesn't respect Query.setFlushMode()
> -----------------------------------------------------------
>
>          Key: HHH-2238
>          URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-2238
>      Project: Hibernate3
>         Type: Bug

>     Versions: 3.2.0.cr5
>  Environment: Windows/Oracle 10g
>     Reporter: Tim Downey
>     Assignee: Steve Ebersole
>     Priority: Minor
>      Fix For: 3.2.2

>
>
> Setting the flush mode manual on a SQLQuery is not respected when executeUpdate() is called.  Under a standard Query, a call to before() is made prior to running executeUpdate().  The call to before() handles the query specific flush mode.
> This same behavior seems necessary for SQLQuery.
> Here is a fix for SQLQuery#executeUpdate
> 	public int executeUpdate() throws HibernateException {
> 		Map namedParams = getNamedParams();
> 		before();
> 		try {
> 		    return getSession().executeNativeUpdate(generateQuerySpecification( namedParams ),  getQueryParameters( namedParams ));
> 		finally {
> 			after();
> 		}                
> 	}

-- 
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
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira




More information about the hibernate-issues mailing list