Hi Tom,
Agreed, it's very ugly. Unfortunately the product has been mostly
developed relying on some fields being used in ways I'd never considered
someone would do. Too late and not enough time to get it changed, so
I'm having to devise a workaround.
:-(
Regards and best wishes,
Justin Clift
Tom Lane wrote:
>
> Justin Clift <aa2@bigpond.net.au> writes:
> > This is so we can have certain types of data which are stored in the
> > database as localtime, updated to still be correct during DST and
> > after.
>
> This sounds awfully ugly. Can't you design the data representation so
> that no such kluge is needed? Most of the PG date/time types store in
> GMT internally, so that there shouldn't be a problem...
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi