| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgres Hackers List <hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] Date/time types: big changeu |
| Date: | 2000-02-17 16:58:10 |
| Message-ID: | 200002171658.LAA16756@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> I've been talking about this for quite some time, but there *really*
> is no excuse to not go to the ISO date/time standard. Every other date
> style is prone to misinterpretation, and the ISO standard is commonly
> used in other instances where reliable date reporting is needed.
>
> I've waited until a major rev to do this, and the groundwork has been
> there for a year or two. There are some good summaries of the issues
> on the web.
>
> But, I'd have no objection to a configure or initdb option; I *would*
> suggest that the old default (and it is the default mostly because
> original Postgres95 had no other styles implemented) is a relatively
> poor choice, and that ISO should be the default choice in the absence
> of an explicit configure or initdb switch.
Well, no one is objecting to this yet, so it may be a good choice.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-02-17 17:05:31 | psql and Control-C |
| Previous Message | Tom Lane | 2000-02-17 16:38:01 | Re: [HACKERS] Definitional issue for INET types |