| From: | Chris Bartlett <c(dot)bartlett(at)paradise(dot)net(dot)nz> |
|---|---|
| To: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>, David Johnston <polobo(at)yahoo(dot)com> |
| Cc: | Alban Hertroys <haramrae(at)gmail(dot)com>, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Can't figure out how to use now() in default for tsrange column (PG 9.2) |
| Date: | 2012-07-16 21:30:13 |
| Message-ID: | p06240806cc2a31e90c8c@[192.168.200.4] |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
At 8:35 PM +0100 16/7/12, Daniele Varrazzo wrote:
>Even without this quirk, the problem of mapping timestamps to other
>languages data types could be an even stronger design factor. I've
>personally settled for 9999-12-31 which is python's datetime.max, maps
>ok to doubles and won't create problems for almost 8000 years.
>
>
>-- Daniele
Stephane Faroult ('The Art of SQL') says that dates so far in the
future can throw off query planners. He explains it nicely here:
http://www.youtube.com/watch?v=gu0WJJXgEFM
Interesting discussion, thanks.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chris Angelico | 2012-07-16 21:42:38 | Re: Replication/cloning: rsync vs modification dates? |
| Previous Message | Brar Piening | 2012-07-16 20:29:54 | Re: Create stored procedure from C#.net |