From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Richard Huxton <dev(at)archonet(dot)com>, Cronje Fourie <cfourie(at)e-intelligence(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: TPCH Benchmark query result invalid |
Date: | 2006-12-13 05:13:34 |
Message-ID: | E716EFFD-BBD4-4230-847D-971C9CB51C7D@seespotcode.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
On Dec 13, 2006, at 1:23 , Tom Lane wrote:
> Richard Huxton <dev(at)archonet(dot)com> writes:
>> richardh=# SELECT interval '3' month;
>> interval
>> ----------
>> 00:00:00
>> (1 row)
>
>> It's got a zero-length date-range it's comparing against. If you have
>> interval '3 months' that should work, but I'm afraid I haven't got
>> time
>> to check against the specs to see what the correct format should be.
>
> I think this syntax is supposed to work according to the SQL spec.
> Tom
> Lockhart was fooling around with making that stuff spec-compliant
> before
> he left the project, and no one has bothered to pick it up since :-(.
> Perhaps everyone thinks the spec syntax for interval constants is so
> bizarre and non-orthogonal it's not worth dealing with ...
Well, for what it's worth, I'm interested. I wasn't aware of this
particular problem, and I can't say when I'll get around to doing
something about it, but now I've at least written it down on my
personal todo.
Michael Glaesemann
grzm seespotcode net
From | Date | Subject | |
---|---|---|---|
Next Message | Cronje Fourie | 2006-12-13 05:53:32 | Re: TPCH Benchmark query result invalid |
Previous Message | Erik Jones | 2006-12-12 23:58:37 | Re: Finding gaps in scheduled events |