You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/05/04 17:59:07 UTC
[jira] [Commented] (SYNCOPE-664) Empty string values not allowed
with Oracle DB
[ https://issues.apache.org/jira/browse/SYNCOPE-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14526777#comment-14526777 ]
ASF subversion and git services commented on SYNCOPE-664:
---------------------------------------------------------
Commit b81cea711945ea7e5133371d9f06c42c398650b2 in syncope's branch refs/heads/master from [~ilgrosso]
[ https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=b81cea7 ]
[SYNCOPE-664] Hiding Oracle behavior in AbstractAttrValue#getStringValue
> 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)