[
https://issues.apache.org/jira/browse/EMPIREDB-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rainer Döbele closed EMPIREDB-485.
----------------------------------
Resolution: Fixed
> Oracle: Allow primary key with nullable column
> ----------------------------------------------
>
> Key: EMPIREDB-485
> URL: https://issues.apache.org/jira/browse/EMPIREDB-485
> Project: Empire-DB
> Issue Type: Improvement
> Reporter: Rainer Döbele
> Assignee: Rainer Döbele
> Priority: Minor
>
> Although Oracle allows a primary key column to be declared as nullable oracle
> silently treats it as non-null resulting in an error when trying to insert a
> record with a null value for the column.
> Instead the constraint should not be declared as "PRIMARY KEY" but as
> "UNIQUE" since for UNIQUE constraints null is handled correctly.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
