Menu
▾
▴
hibernate-issues
|
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
|
|
From: <leg...@at...> - 2003-11-06 00:52:14
|
The following comment has been added to this issue:
Author: John Kristian
Created: Wed, 5 Nov 2003 6:51 PM
Body:
See also http://forum.hibernate.org/old//890970.html
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-11-07 14:32:26
|
The following comment has been added to this issue:
Author: Joseph Fifield
Created: Fri, 7 Nov 2003 8:31 AM
Body:
Not sure if this helps, but the following code returns the right update count for me using the jTDS driver on SQL Server 2000. SQL Server appears to return multiple update counts when a trigger is fired, and the last one is the update count for the statement you actually executed.
ps.executeUpdate();
int updateCount = ps.getUpdateCount();
while (!ps.getMoreResults() && (ps.getUpdateCount() != -1)) {
updateCount = ps.getUpdateCount();
}
---------------------------------------------------------------------
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
|
|
From: <leg...@at...> - 2003-12-11 06:47:19
|
The following comment has been added to this issue:
Author: Gavin King
Created: Thu, 11 Dec 2003 12:45 AM
Body:
Actually, the original suggested fix doesn't help much since it could still fail if the triggered SQL returns a rowcout of 0, as some users have occasionally observed.
---------------------------------------------------------------------
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: Open
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: Thu, 11 Dec 2003 12:45 AM
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
|
|
From: <leg...@at...> - 2004-06-30 02:55:46
|
The following comment has been added to this issue:
Author: Vladimir Goncharov
Created: Tue, 29 Jun 2004 10:13 PM
Body:
Actually, it is better not to check rowcount at all or to have some global property to skip checking the row count. We need to delete all the records and then insert regardless of what the current db state is. Currently I need to extend the EntityPersister to eat the exception, but it is not a clean solution.
---------------------------------------------------------------------
View this comment:
http://opensource.atlassian.com/projects/hibernate/browse/HB-139?page=comments#action_13545
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/hibernate/browse/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: Closed
Priority: Major
Resolution: WON'T FIX
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: Hibernate2
Components:
core
Versions:
2.0 final
Assignee: Gavin King
Reporter: Don Eddleman
Created: Tue, 17 Jun 2003 10:15 AM
Updated: Tue, 29 Jun 2004 10:13 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
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X