You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@empire-db.apache.org by "Rainer Döbele (JIRA)" <em...@incubator.apache.org> on 2013/02/04 15:14:20 UTC
[jira] [Closed] (EMPIREDB-120) DBTableColumn checkValue(Object
value) for DataType.DATETIME and DataType.DATE throws
FieldIllegalValueException if the value is empty (but DBTableColumn is
nullable)
[ https://issues.apache.org/jira/browse/EMPIREDB-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rainer Döbele closed EMPIREDB-120.
----------------------------------
Cleanup of unclosed issues.
> DBTableColumn checkValue(Object value) for DataType.DATETIME and DataType.DATE throws FieldIllegalValueException if the value is empty (but DBTableColumn is nullable)
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: EMPIREDB-120
> URL: https://issues.apache.org/jira/browse/EMPIREDB-120
> Project: Empire-DB
> Issue Type: Bug
> Components: Core
> Affects Versions: empire-db-2.2.0-incubating
> Reporter: Jörg Reiher
> Assignee: Jörg Reiher
> Priority: Minor
> Fix For: empire-db-2.3.0
>
>
> DBTableColumn's method checkValue() tries to parse a given empty String to a DATE/DATETIME, if DBTableColumn is of type DATE or DATETIME.
> This leads to a FieldIllegalValueException, even if the DBTableColumn is nullable.
> This behaviour isn't consistent with the behaviour for all other data types: If the DBTableColumn's type is DECIMAL, FLOAT, and INTEGER, then the method checks for String length > 0 before trying to parse the value (and therefore excepts an empty string as a valid value for a nullable field).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira