Feature: Change range defaults and add generate_series function

[prrao87]

Features

• Change the default stop argument for range to be non-inclusive (similar to DuckDB and many programming languages)
• Add a generate_series function to allow the user to generate series inclusively (where the stop argument is the last value of the series)

API

Other

Description

Kùzu's range function is currently inclusive of the stop argument.

kuzu> RETURN range(1,3) AS r ;
-----------
| r       |
-----------
| [1,2,3] |
-----------
(1 tuple)
(1 column)
Time: 0.15ms (compiling), 0.30ms (executing)

This is not the case in DuckDB:

D SELECT range(1,3) AS r;
┌─────────┐
│    r    │
│ int64[] │
├─────────┤
│ [1, 2]  │
└─────────┘

For inclusive range, DuckDB provides an additional function generate_series, which behaves like our current range function in Kùzu.

D SELECT * FROM generate_series(1,3);
┌─────────────────┐
│ generate_series │
│      int64      │
├─────────────────┤
│               1 │
│               2 │
│               3 │
└─────────────────┘

We should make the range behaviour more consistent with other systems and offer the convenience function generate_series, so new users don't have to rewire their thinking when coming from DuckDB.

[acquamarin]

I think we should follow neo4j style of range function which is inclusive on start and end instead of following SQL.
https://neo4j.com/docs/cypher-manual/current/functions/list/

[andyfengHKU]

There is still generate_series(). So I'm keeping this issue open.