From: | Gavan Schneider <pg-gts(at)snkmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Yet Another Timestamp Question: Time Defaults |
Date: | 2013-01-23 09:24:31 |
Message-ID: | 22267-1358933073-179617@sneakemail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Monday, January 21, 2013 at 18:11, bgd39h5xxt(at)sneakemail(dot)com
(Nathan Clayton nathanclayton-at-gmail.com |pg-gts/Basic|) wrote:
>I only wish. I work with a transactional system from the 70s on
>a daily basis that decided to store something like a "work date" and
>"work time". The date changes whenever they decide to dateroll the
>system. Until then the time field continues to grow, so you see times
>like 25:00 and 26:00 all the time.
>
SELECT execute(relevant_dba) FROM the_70s WITH tardis WHERE
working_tardis = true;
>Exceptions abound.
>
At least that can't be blamed on a government, and, we can only
hope ISO-8601 will prevent more examples being created.
You sound as though you really need, and/or already have, a
dedicated datatype... if only to stop 'the system' from 'fixing'
such weirdness.
Regards
Gavan Schneider
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2013-01-23 12:13:18 | Re: proposal: fix corner use case of variadic fuctions usage |
Previous Message | Cliff de Carteret | 2013-01-23 09:14:35 | Re: Pg_xlog increase due to postgres crash (disk full) |