[jira] Commented: (OPENJPA-750) OptimisticLockException is thrown when numeric truncation occurs on Sybase

["Fay Wang (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OPENJPA-750?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12640684#action_12640684 ] 

Fay Wang commented on OPENJPA-750:
----------------------------------

Hi Jeremy, for your option (1), you might want to look at Sybase arithabort numeric_truncation flag. For compliance with the ANSI SQL standard, enter 
"set arithabort numeric_truncation on". For details, see http://manuals.sybase.com/onlinebooks/group-as/asg1250e/sqlug/@Generic__BookTextView/3524;pt=693/*

> OptimisticLockException is thrown when numeric truncation occurs on Sybase
> --------------------------------------------------------------------------
>
>                 Key: OPENJPA-750
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-750
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: jdbc
>    Affects Versions: 1.3.0
>         Environment: Sybase 15, jconn3.jar
>            Reporter: Jeremy Bauer
>
> OpenJPA throws an OptimisicLockException after an insert is issued to Sybase and there is no SQLException and the update count does not match the expected value.  The root cause is that the insert is trying to insert a numeric value which is larger than the numeric field.  Sybase issues a SQLWarning  (preparedStatement.getWarnings()) and the insert fails.  An OptimisticLockException is thrown with misleading statement text.
> I recommend we:
> 1) Add a config property to disable numeric truncation, if possible.
> 2) Check for SQLWarning's after an ps exec fails and minimally log them.  Or throw them as a more appropriate exception?
> This issue is very similar to OPENJPA-745, except 745 deals with character truncation.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.