You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
To reproduce
CREATE TABLE
with aSHORT
datatype.INSERT INTO
aNULL
into theSHORT
column.Expected:
Actual:
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?
Additional context
No response
The text was updated successfully, but these errors were encountered: