| From: | Thomas Lockhart <thomas(at)fourpalms(dot)org> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Yury Bokhoncovich <byg(at)center-f1(dot)ru>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Eurodates by default |
| Date: | 2002-03-20 03:58:23 |
| Message-ID: | 3C9808DF.E62B2B9E@fourpalms.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
(redirected to -hackers)
...
> What we want to do is integrate the SET DateStyle variable into GUC
> somehow, but I'm not entirely happy with the current behavior and have
> been unable to agree with Thomas Lockhart on how to do it. But it will
> get done eventually.
Hmm. I've sensed a general unhappiness with most of the world's time
zones recently ;)
But I'm afraid I'm not recalling the specific issues associated with GUC
vs no-GUC. What in the current behavior of date and time needs to
change? Is it locale issues (which for non-ISO date input and output is
a can of worms by itself) or something else?
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2002-03-20 04:32:54 | Re: Eurodates by default |
| Previous Message | Bruce Momjian | 2002-03-19 19:44:00 | Re: JDBC PreparedStatement Memory Leak. |