[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4568?page=c...
]
Strong Liu commented on HHH-4568:
---------------------------------
actually Sybase throws an SQLWarning with a message "Truncation error occurred."
and a nest SQLWarning with a message "Command has been aborted.", so the object
does not be stored into DB, but hibernate does not aware of that and assumes the storing
is successful.
and then in the NonBatchingBatcher.addToBatch(), expectation.verifyOutcome(rowCount,
statement, 0) will throw an org.hibernate.StaleStateException: Batch update returned
unexpected row count from update [0]; actual row count: 0; expected: 1
Sybase - Test "BatchTest" fails due to "unexpected row
count from update"
-------------------------------------------------------------------------
Key: HHH-4568
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4568
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.2.4.sp1, 3.3.2, 3.5.0.Beta-1, 3.5.0-Beta-2
Environment: Sybase
Reporter: Strong Liu
Assignee: Strong Liu
Fix For: 3.2.4.sp1, 3.2.x, 3.3.0.GA, 3.3.x, 3.5
The test "BatchTest" fails due to "org.hibernate.StaleStateException:
Batch update returned unexpected row count from update [0]; actual row count: 0; expected:
1". The database server seems configured properly, as the "BatchUpdates"
sample from jConnect 6 works correctly.
The problem specifically occurs with a table that has a numeric column with precision
(e.g. numeric(10,4))
Sybase does not thrown any SQLException when you try and persist a numeric value whose
scale exceeds that defined on the column. Instead, it returns an updateCount of zero
--
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