Thank you for request! May I ask you to answer on the following questions:

Is it important to keep syntax of operations, like:

    SELECT numrange(11.1, 22.2) && numrange(20.0, 30.0); 
    SELECT int4range(10, 20) * int4range(15, 25);

Now Alasql expression compiler does not check operand types and delegates this work to JavaScript, so I need to create special range_*() functions for these operations, like:

    SELECT range_and(numrange(11.1, 22.2), numrange(20.0, 30.0)); 
    SELECT range_intersect(int4range(10, 20) * int4range(15, 25));

or create special range operators (like @>):

    SELECT numrange(11.1, 22.2) @&& numrange(20.0, 30.0); 
    SELECT int4range(10, 20) @* int4range(15, 25);

Which option is better on your opinion?

Postgres has 6 range datatypes

    int4range — Range of integer
    int8range — Range of bigint
    numrange — Range of numeric
    tsrange — Range of timestamp without time zone
    tstzrange — Range of timestamp with time zone
    daterange — Range of date

But for Alasql all of them will be realized with only 'typeless' range. Do I need to keep all these 6 types or can use only one, like: RANGE(1,2)?

Should I implement '::' as an additional form to CAST/CONVERT functions?

Thank you!

Feature request: Range types from Postgresql #55

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions