From: <leg...@at...> - 2003-11-06 00:42:14
|
The following comment has been added to this issue: Author: John Kristian Created: Wed, 5 Nov 2003 6:41 PM Body: With NetDirect's JSQLConnect driver, one can avoid this problem by setting the driver property lastUpdateCount=true (which prevents triggers from affecting the returned row count). For doco see http://www.j-netdirect.com/JSQLConnect/TechnicalReference.html#ConnectSettings --------------------------------------------------------------------- View the issue: http://opensource.atlassian.com/projects/hibernate/secure/ViewIssue.jspa?key=HB-139 Here is an overview of the issue: --------------------------------------------------------------------- Key: HB-139 Summary: Relax rowcount to be > instead of equal to account for triggers. Type: Improvement Status: Assigned Priority: Major Project: Hibernate2 Components: core Versions: 2.0 final Assignee: Gavin King Reporter: Don Eddleman Created: Tue, 17 Jun 2003 10:15 AM Updated: Tue, 4 Nov 2003 5:48 PM Environment: All OSs, SQLServer and more than likely any other DB that supports triggers. Description: Within the NonBatchingBatcher class the check for row count to determine success should be relaxed to rowCount >= expected so that any triggers defined on tables affected by the insert/update will not cause a txn to fail just because they fired. --------------------------------------------------------------------- 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 |