| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | tswan(at)idigx(dot)com |
| Cc: | Felipe Nascimento <Felipe(dot)Nascimento(at)multivalor(dot)com(dot)br>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: time stamp |
| Date: | 2002-06-21 21:35:43 |
| Message-ID: | 28945.1024695343@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Thomas Swan <tswan(at)idigx(dot)com> writes:
>> No, it won't. If the user has TimeZone set to -05, as he should, then
>> his input of '2002-06-20 12:00:00' will be read as '2002-06-20 12:00:00-05'.
>> And it will be displayed to him that way. But if someone else who
>> has TimeZone set differently looks at the stored value, it will be shown
>> to them properly converted into their timezone.
>>
> This can be a problem if the client is a web application in a fixed
> timezone and the person viewing the results is in a different time zone.
If the webserver sets its session TimeZone according to the end user's
preference, everything will work just fine. I am not sure how you
expect Postgres to intuit the proper timezone to use in this scenario
without any cooperation from the webserver...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Swan | 2002-06-21 21:45:16 | Re: time stamp |
| Previous Message | Mark Tessier | 2002-06-21 21:20:32 | to recompile or not recompile postgres |