[
https://issues.apache.org/jira/browse/SYNCOPE-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fabio martelli closed SYNCOPE-664.
----------------------------------
Release 1.2.4
> Empty string values not allowed with Oracle DB
> ----------------------------------------------
>
> Key: SYNCOPE-664
> URL: https://issues.apache.org/jira/browse/SYNCOPE-664
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 1.2.3
> Environment: Oracle DB
> Reporter: Francesco Chicchiriccò
> Assignee: Francesco Chicchiriccò
> Priority: Critical
> Fix For: 1.2.4, 2.0.0
>
>
> Due to a [known
> (mis)behavior|http://stackoverflow.com/questions/13278773/null-vs-empty-string-in-oracle]
> of Oracle DB, empty values for VARCHAR columns are treated as {{NULL}}.
> This means that no {{""}} values are allowed for any attribute value.
> This problem was discovered when attempting to set the configuration
> parameter {{notificationjob.cronExpression}} to an empty string, in order to
> disable the {{NotificationJobs}}, but has a wider impact.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
