SQL INSERT allows NULL on non-nullable SHORT column

[amunra]

To reproduce

1. CREATE TABLE with a SHORT datatype.
2. INSERT INTO a NULL into the SHORT column.
3. Query back.

Expected:

• The SQL Insert statement (step 2) should have failed.

Actual:

• All statements pass, the actual value returned is 0 instead instead of NULL.

QuestDB version:

7.4.0

OS, in case of Docker specify Docker and the Host OS:

MacOS

File System, in case of Docker specify Host File System:

APFS

Full Name:

Adam Cimarosti

Affiliation:

QuestDB

Have you followed Linux, MacOs kernel configuration steps to increase Maximum open files and Maximum virtual memory areas limit?

• Yes, I have

Additional context

No response

[ideoma]

There are no non-nullable types in QuestDB. You cannot specify NOT NULL when you create table.

[Rushichaudhari2003]

Based on the information provided, it appears that you are using QuestDB, which might have different behavior compared to traditional SQL databases. QuestDB version 7.4.0 seems to be automatically converting NULL values to 0 for SHORT columns, even if they are defined as non-nullable.

Regarding the kernel configuration, increasing the maximum open files and maximum virtual memory areas limits is generally recommended for running databases on Linux and MacOS systems. However, this issue seems to be specific to QuestDB's handling of NULL values in non-nullable SHORT columns, and it is not directly related to the kernel configuration.

[nwoolmer]

It's just an implicit cast, I think.