Re: BUG #1518: Conversions to (undocumented) SQL year-month and - Mailing list pgsql-bugs

From Roy Badami
Subject Re: BUG #1518: Conversions to (undocumented) SQL year-month and
Date
Msg-id 16961.59734.409675.896781@giles.gnomon.org.uk
Whole thread Raw
In response to Re: BUG #1518: Conversions to (undocumented) SQL year-month and  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: BUG #1518: Conversions to (undocumented) SQL year-month and  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-bugs
Bruce> Here is an email stating it is implementation defined:

    Bruce>     http://archives.postgresql.org/pgsql-bugs/2005-03/msg00162.php

Hmm, looks like I'm mistaken, then.  In fact the "whether to truncate
or round" bit suggests you should do one or the other, rather than
raise an exception.

Will have to take a look at the spec when I get a moment...

      -roy

pgsql-bugs by date:

Previous
From: Roy Badami
Date:
Subject: Re: BUG #1517: SQL interval syntax is accepted by the parser,
Next
From: Tom Lane
Date:
Subject: Re: BUG #1552: massive performance hit between 7.4 and 8.0.1