![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
is it storing in the time zone of the actual server or something? not sure where my db server actually, physically is. |
|
if so, does that imply that i can translate these stored dates to any target time zone of my choosing when selecting the date from the db? |
#3
| |||
| |||
|
|
See the documentation for Date/Time Types and Date/Time Functions and Operators: http://www.postgresql.org/docs/7.4/s...-datetime.html http://www.postgresql.org/docs/7.4/s...-datetime.html if so, does that imply that i can translate these stored dates to any target time zone of my choosing when selecting the date from the db? Yes -- see the aforementioned documentation. |
#4
| |||
| |||
|
|
well... the examples in the documentation work, but they only use static dates (hard-coded, i mean): SELECT TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40-05' AT TIME ZONE 'PST'; but, when i try: SELECT mydatecolumn FROM mytable AT TIME ZONE 'PST'; .... i get a parse error. |
#5
| |||
| |||
|
|
On Nov 22, 2004, at 11:30 AM, P. George wrote: well... the examples in the documentation work, but they only use static dates (hard-coded, i mean): SELECT TIMESTAMP WITH TIME ZONE '2001-02-16 20:38:40-05' AT TIME ZONE 'PST'; but, when i try: SELECT mydatecolumn FROM mytable AT TIME ZONE 'PST'; .... i get a parse error. It would help if you included the exact error. However, one thing the examples in the docs show, is that the AT TIME ZONE follows the value, i.e., SELECT mydatecolumn AT TIME ZONE 'PST' FROM mytable; hth Michael Glaesemann grzm myrealbox com |
![]() |
| Thread Tools | |
| Display Modes | |
| |