---

This section details on the original issue you should resolve

<issue_title>Feature request: Range types from Postgresql</issue_title>
<issue_description>I do a lot of work with dates, range types would be useful.

http://www.postgresql.org/docs/9.2/static/rangetypes.html
</issue_description>

<agent_instructions>Please make a new test file named test/test055-B.js to verify the expected funktionality. Then start the implementation. I propose using the new functions on set functions like

union(other)

difference(other)

symmetricDifference(other)

isSubsetOf(other)

isSupersetOf(other)

isDisjointFrom(other)​

if that is helping </agent_instructions>

Comments on the Issue (you are@copilot in this section)

@agershunThank you for request! May I ask you to answer on the following questions:1. Is it important to keep syntax of operations, like:

SELECTnumrange(11.1,22.2)&&numrange(20.0,30.0);SELECTint4range(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:

SELECTrange_and(numrange(11.1,22.2),numrange(20.0,30.0));SELECTrange_intersect(int4range(10,20)*int4range(15,25));

or create special range operators (like @>):

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

Which option is better on your opinion?

1. 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)?

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

Thank you!

@mathiasrwI have added this as a featurerequest: http://feathub.com/agershun/alasql/+22