From: | Jim Nasby <decibel(at)decibel(dot)org> |
---|---|
To: | Richard Broersma Jr <rabroersma(at)yahoo(dot)com> |
Cc: | Andrus <eetasoft(at)online(dot)ee>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Why overlaps is not working |
Date: | 2006-11-27 23:19:02 |
Message-ID: | 3C80B72B-F961-48DF-B881-81BC18E810AF@decibel.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Nov 23, 2006, at 10:57 AM, Richard Broersma Jr wrote:
>> If my database contains dates greater than DATE '9999-12-31' then
>> this
>> check fails.
>>
>> This is why I'm searching for a real MAX_DATE value in Postgres.
>>
>> It would be nice if there will be MAX_DATE constant in Postgres or
>> some one
>> row system table contains MAX_DATE value.
>
> through expermentation I came up with:
>
> logs=# select '5874897-12-31'::date;
> date
> ---------------
> 5874897-12-31
> (1 row)
>
> logs=# select '5874898-12-31'::date;
> ERROR: date out of range: "5874898-12-31"
Keep in mind that that number could change depending on if you're
using integer or floating point timestamps.
I know that numeric supports +/- infinity; I don't remember off-hand
if timestamps have that as well.
--
Jim Nasby jim(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Nasby | 2006-11-27 23:24:31 | Re: IN clause |
Previous Message | Jim Nasby | 2006-11-27 23:16:09 | Re: A generic trigger to log chanes on database tables |