You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Stamatis Zampetakis (Jira)" <ji...@apache.org> on 2020/06/20 00:29:00 UTC
[jira] [Assigned] (CALCITE-4075) Mock table 'EMPNULLABLES' should
allow nulls in all non-pk columns
[ https://issues.apache.org/jira/browse/CALCITE-4075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stamatis Zampetakis reassigned CALCITE-4075:
--------------------------------------------
Assignee: Stamatis Zampetakis
> Mock table 'EMPNULLABLES' should allow nulls in all non-pk columns
> ------------------------------------------------------------------
>
> Key: CALCITE-4075
> URL: https://issues.apache.org/jira/browse/CALCITE-4075
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: Stamatis Zampetakis
> Assignee: Stamatis Zampetakis
> Priority: Trivial
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently Mock table 'EMPNULLABLES' allows nulls in almost every column. It does not allow nulls in the primary key which is expected and the column 'ENAME' that is unexpected.
> I realized that 'ENAME' column was declared as not nullable after debugging for quite some time a test where I was wrongly assuming that all columns of the table were nullable.
> To avoid this kind of confusion in the future I propose to make 'ENAME' also nullable. The impact on existing tests is minimal.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)