[
https://issues.apache.org/jira/browse/DERBY-3969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-3969:
---------------------------------
Description:
The following script shows the problem for CHECK constraints. Other NPEs occur
for PRIMARY, FOREIGN KEY, and NOT NULL constraints.
drop table t_ccnd_1;
-- raises a null pointer exception
create table t_ccnd_1( a int, b generated always as ( -a ) check ( b < 0 ) );
was:
The following script shows this problem:
drop table t_ccnd_1;
-- raises a null pointer exception
create table t_ccnd_1( a int, b generated always as ( -a ) check ( b < 0 ) );
Summary: NPE if you declare a constraint on a generated column and omit
the datatype (was: NPE if you declare a CHECK constraint on a generated column
and omit the datatype)
> NPE if you declare a constraint on a generated column and omit the datatype
> ---------------------------------------------------------------------------
>
> Key: DERBY-3969
> URL: https://issues.apache.org/jira/browse/DERBY-3969
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.5.0.0
> Reporter: Rick Hillegas
>
> The following script shows the problem for CHECK constraints. Other NPEs
> occur for PRIMARY, FOREIGN KEY, and NOT NULL constraints.
> drop table t_ccnd_1;
> -- raises a null pointer exception
> create table t_ccnd_1( a int, b generated always as ( -a ) check ( b < 0 ) );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
