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

Posted to dev@empire-db.apache.org by "Rainer Döbele (Jira)" <ji...@apache.org> on 2022/09/12 11:02:00 UTC

[jira] [Updated] (EMPIREDB-395) Field validation: allow min/max range constraints to be non-integers

     [ https://issues.apache.org/jira/browse/EMPIREDB-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rainer Döbele updated EMPIREDB-395:
-----------------------------------
    Summary: Field validation: allow min/max range constraints to be non-integers  (was: Field validation allow min/max range constraints to be non-integers)

> Field validation: allow min/max range constraints to be non-integers
> --------------------------------------------------------------------
>
>                 Key: EMPIREDB-395
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-395
>             Project: Empire-DB
>          Issue Type: Improvement
>          Components: JSF2 Extensions
>            Reporter: Rainer Döbele
>            Assignee: Rainer Döbele
>            Priority: Minor
>
> Currently range checking of Numeric columns based on given min/max values are limited to Integer values. Numeric validation should also allow non-integers (e.g. BigDecimals) as min/max values.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)