| From: | Michael Glaesemann <grzm(at)seespotcode(dot)net> |
|---|---|
| To: | Agent M <agentm(at)themactionfaction(dot)com> |
| Cc: | Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Timestamp vs timestamptz |
| Date: | 2006-07-14 05:11:18 |
| Message-ID: | F77EB48F-209B-4E48-A4EB-C413C3420C85@seespotcode.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Jul 13, 2006, at 21:49 , Agent M wrote:
> For example, flight arrival information should probably include the
> timezone of the destination.
Of course, for this example you'd also want to know *where* the
flight is arriving, which would also let you know the appropriate
time zone in an indirect way. Hopefully we'll be able to store time
zone information with the timestamp sometime. It's been discussed
before, but I don't believe a concrete proposal has been put forward
yet.
Michael Glaesemann
grzm seespotcode net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Volkan YAZICI | 2006-07-14 06:28:58 | Re: stored function - array parameter - how many element in array ? |
| Previous Message | Patrick TJ McPhee | 2006-07-14 04:46:59 | Re: Physical block structure in PostgreSQL |