![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
|
Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a tool for doing 5% of the work and then sitting around waiting for someone else to do the other 95% so you can sue them. |
#2
| |||
| |||
|
|
Is there any way I can use these from within postgresql? Those files contains details about daylight saving changes and other useful details like that, which a simple PST or EST won't cover. Or should I simply do all my date/time conversion in my application? |
#3
| |||
| |||
|
|
* Martijn van Oosterhout <kleptog (AT) svana (DOT) org> [2004-10-07 22:22:24 +0200]: Is there any way I can use these from within postgresql? Those files contains details about daylight saving changes and other useful details like that, which a simple PST or EST won't cover. Or should I simply do all my date/time conversion in my application? The time zone support seems pretty exhaustive. Check out section B-r in the document below. http://www.postgresql.org/docs/7.4/s...-keywords.html |
|
Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a tool for doing 5% of the work and then sitting around waiting for someone else to do the other 95% so you can sue them. |
#4
| |||
| |||
|
|
But it doesn't seem to work to actually work out times across the world w.r.t. daylight savings. ... For example, this script works out, given a time in one timezone, what it was in another timezone: |
#5
| |||
| |||
|
|
The infrastructure needed for this is finally present in 8.0, ie we have the timezone data available, but actually teaching AT TIME ZONE about it didn't get done in time. Likely it will appear in 8.1 (especially if you step up and do the work ;-)). |
|
Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a tool for doing 5% of the work and then sitting around waiting for someone else to do the other 95% so you can sue them. |
![]() |
| Thread Tools | |
| Display Modes | |
| |