insertingnull bug

[universalmind303]

Description

> create table test (value double);
> insert into test values (0.0), (null), (0.1), (2.0);
> select * from test;
┌─────────┐
│   value │
│      ── │
│ Float64 │
╞═════════╡
│ 0.00000 │
│ 0.10000 │
│ 0.10000 │
│ 2.00000 │
└─────────┘

Additional context

Clickhouse apparantly behaves similarly to ours and coerces the null to a zero, but we are inserting the wrong value all together.

If we wanted to mimic clickhouse behavior (which i think is also wrong), we should atleast have the correct values inserted 0.0 for row 2 instead of 0.1. (this may just be a display issue. IDK if we automatically coerce NULL to 0.0 when displaying.

I think duckdb's implementation has the most intuitive behavior here

D create table test (value double);
D insert into test values (0.0), (null), (0.1), (2.0);
D select * from test;
┌────────┐
│ value  │
│ double │
├────────┤
│    0.0 │
│        │
│    0.1 │
│    2.0 │
└────────┘