You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ofbiz.apache.org by "Pierre Smits (JIRA)" <ji...@apache.org> on 2016/04/07 20:35:25 UTC

[jira] [Commented] (OFBIZ-6992) Field 'maxRetry' is typed as 'numeric' in entity 'JobSandbox'

    [ https://issues.apache.org/jira/browse/OFBIZ-6992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230784#comment-15230784 ] 

Pierre Smits commented on OFBIZ-6992:
-------------------------------------

Changing this to the SMALLINT variant (-32768 to +32767) should do the trick.

> Field 'maxRetry' is typed as 'numeric' in entity 'JobSandbox'
> -------------------------------------------------------------
>
>                 Key: OFBIZ-6992
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-6992
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: Trunk
>            Reporter: Pierre Smits
>              Labels: datatype, fieldtype
>
> Currently the field 'maxRetry' in entity 'JobSandbox' in the entitydef of the service component in the Framework stack is typed as 'numeric'.
> This should be typed in accordance with the various integer types (INT, INTEGER, SMALLINT, BIGINT, LARGEINT, etc), as it doesn't make sense to associate it with a type that is normally used for numbers with decimals. 
> Some connectors to DBMSes and/or the databases themselves are very picky about this. As I have experienced when trying to have OFBiz persist on HBase.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)