|
From: Sergey V. (JIRA) <no...@at...> - 2006-05-06 10:00:26
|
[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-870?page=comments#action_23028 ] Sergey Vladimirov commented on HHH-870: --------------------------------------- Max, I'm sure you need to make it an optional. For example, my application knwo when to clear caches, and when just remove one entity from the cache. So, please, make an option to disable clearing all caches. But clearing all caches should be default behavior for sql update queries, IMO. > support SQL updates in named queries > ------------------------------------ > > Key: HHH-870 > URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-870 > Project: Hibernate3 > Type: New Feature > Components: core > Environment: Hibernate 3.0.5, SQL Server 2000 > Reporter: Nathan Moon > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 3.2.0.cr2 > Attachments: NativeSQLQueryPlan_withNamedParameters.java.txt, patch.txt > > > currently attempting to execute a named <sql-query> that is an update statement throws java.lang.UnsupportedOperationException: Update queries only supported through HQL. > In order to execute sql updates, the Session.connection() must be used directly. > (see forum topic http://forum.hibernate.org/viewtopic.php?t=940281) > It would be very nice to be able to be able to externalize SQL update statements and be able to run them with Session.getNamedQuery(). -- 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 |