-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution:
Won't Fix
-
Affects Version/s: EAP 5.0.0.CR1, EAP 5.0.0.BETA, EAP 5.0.0.CR2, EAP 5.0.0.CR3, EAP 5.0.0.CR4 (FCS and BETA2), EAP 5.0.0.CR5, EAP 5.0.0, EAP 5.0.1.CR1, EAP_EWP 5.1.0
-
Fix Version/s: TBD
-
Component/s: Hibernate
-
Labels:None
-
Affects:Release Notes
-
Workaround:Workaround Exists
-
Workaround Description:
-
Release Notes Docs Status:Not Required
http://opensource.atlassian.com/projects/hibernate/browse/HHH-2388
A workaround is that the application validate entity properties to ensure they do not overflow what is defined for the underlying column.
Because Sybase does not throw an exception, it does indicate an update count of 0. Hibernate does not check the update count so it does not detect that the insert failed.
According to HHH-2388, Hibernate sets the ID to 0. HHH-2830 (a duplicate issue) says that the ID in the (still) transient entity is set to the previous ID that was generated.
- blocks
-
JBPAPP-2731 HHH-4568 - Core - Sybase - Test "BatchTest" fails due to "unexpected row count from update"
-
- Closed
-
- cloned to
-
JBPAPP-5549 Document HHH-2388 : Insert w/ identity column fails on Sybase but no exception occurs
-
- Closed
-
- is duplicated by
-
JBPAPP-5549 Document HHH-2388 : Insert w/ identity column fails on Sybase but no exception occurs
-
- Closed
-