| From: | Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Hackers List <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DateStyle (was Re: Per-database/schema settings) |
| Date: | 2000-07-07 05:58:53 |
| Message-ID: | 3965719D.A655E9ED@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 1. Major output mode
> 2. Should month-before-day or day-before-month be *preferred* where
> *applicable*? (It's not "applicable" in any output mode but SQL, and it's
> not "applicable" on input like '99/12/31'. -- I always thought of it as
> "tie-breaker".)
Yes, for input it is a "tie-breaker"; that's how I've thought of it too.
Sure, let's try to break this into two orthogonal attributes. Can you
think of a good name or keyword? "European" and "US" sure isn't saying
things as clearly as "day-before-month" or "month-before-day", but they
are easier to type and make a better shorthand.
Let's find a good syntax for this setting before we go too far...
- Thomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2000-07-07 06:07:01 | Re: Memo on coding practices: strcmp() does not yield bool |
| Previous Message | Paul McGarry | 2000-07-07 05:34:13 | Re: [SQL] MAX() of 0 records. |