From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, Postgres Hackers List <hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Date/time types: big changeu |
Date: | 2000-02-16 22:13:42 |
Message-ID: | 200002162213.RAA14254@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> Also, I've changed the default date style to "ISO" (not just in
> >> time for Y2K, but we'll be ready for "Y3K").
>
> > I think we need a consensus on this. I think this may be a problem for
> > some people. Comments?
>
> Good point. Perhaps there should be a way to select the default date
> style at configure or initdb time. I don't mind if the "default default"
> is ISO, but if I had apps that were dependent on the old default setting
> I'd sure be annoyed by this change...
>
> Has anyone thought much about the fact that beginning next year,
> heuristics to guess which field is the year will become nearly useless?
> Quick, when is '01/02/03'? I suspect a lot of people who got away with
> not thinking hard about datestyles will suddenly realize that they need
> to set the default datestyle to whatever they are accustomed to using.
Wow, that is an excellent point. I was doing it for 2000, and was
thinking, gee, that's not too hard. I can see it getting much more
confusing next year, as you said.
--
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 | Bruce Momjian | 2000-02-16 22:29:33 | Re: [HACKERS] FYI: BNF for SQL93 and SQL-3 |
Previous Message | Hannu Krosing | 2000-02-16 22:12:42 | FYI: BNF for SQL93 and SQL-3 |