Start with [ , end with )

2018-04-23 Thread PG Doc comments form
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/10/static/rangetypes.html
Description:

See in: 

8.17.2. Examples

CREATE TABLE reservation (room int, during tsrange);
INSERT INTO reservation VALUES
(1108, '[2010-01-01 14:30, 2010-01-01 15:30)');
   ^ ^
While not an Error, still...


why is there no CSVQL?

2018-04-23 Thread PG Doc comments form
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/10/static/features.html
Description:

CSV files can be huge. most commercial spreadsheets cannot handle it. there
are high-volume transactions such as for tax reporting which need a separate
copy (user can handle that) with columns dropped, maybe renamed (yeah, ALTER
shouldn't be so hard to use), and an SQL or SQL-like language for this would
be excellent.


Re: Start with [ , end with )

2018-04-23 Thread Mike Toews
On 24 April 2018 at 01:00, PG Doc comments form  wrote:
> 8.17.2. Examples
>
> CREATE TABLE reservation (room int, during tsrange);
> INSERT INTO reservation VALUES
> (1108, '[2010-01-01 14:30, 2010-01-01 15:30)');
>^ ^
> While not an Error, still...

See 8.17.3. Inclusive and Exclusive Bounds

This is an example with an inclusive lower bound "[" and an exclusive
upper bound ")".



Re: Start with [ , end with )

2018-04-23 Thread Jonathan S. Katz

> On Apr 23, 2018, at 8:37 PM, Mike Toews  wrote:
> 
> On 24 April 2018 at 01:00, PG Doc comments form  
> wrote:
>> 8.17.2. Examples
>> 
>> CREATE TABLE reservation (room int, during tsrange);
>> INSERT INTO reservation VALUES
>>(1108, '[2010-01-01 14:30, 2010-01-01 15:30)');
>>   ^ ^
>> While not an Error, still...
> 
> See 8.17.3. Inclusive and Exclusive Bounds
> 
> This is an example with an inclusive lower bound "[" and an exclusive
> upper bound ")”.

When dealing with date/time ranges, it’s a very common use case to have
an inclusive lower-bound and exclusive upper-bound, especially when
dealing with scheduling.

Jonathan