Re: BUG #4935: Weird input syntax for intervals, part 2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Frank Spies" <frank(dot)spies(at)biotronik(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4935: Weird input syntax for intervals, part 2
Date: 2009-07-23 15:21:54
Message-ID: 16834.1248362514@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Frank Spies" <frank(dot)spies(at)biotronik(dot)com> writes:
> After finding out that bug #4918 was already fixed in 8.4 release, I played
> around with the interval input syntax in 8.4 and found that
> '2.5' year
> is not the same as
> '2.5 year'
> in release 8.4:

I don't think this is a bug. The former case specifies (per SQL
standard) that you are only wanting storage to year accuracy.
The latter is a historical Postgres syntax that does not involve
constraining the precision of the stored value.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Mathieu Dupuis 2009-07-23 15:45:01 BUG #4936: Bad result for SQL query
Previous Message Frank Spies 2009-07-23 12:56:36 BUG #4935: Weird input syntax for intervals, part 2