| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Vincent Moreau <vincentneko(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Add a new pattern for zero-based months for Date/Time Formatting |
| Date: | 2025-03-26 15:42:24 |
| Message-ID: | 1616069.1743003744@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Christoph Berg <myon(at)debian(dot)org> writes:
> Re: Peter Eisentraut
>> Moreover, if there are zero-based months, why not zero-based days,
>> or any of the other fields?
> I would suspect this is coming from C's struct tm where tm_mon is
> 0..11 and all other fields being "normal". Used by asctime(), gmtime()
> and friends.
FWIW, I agree completely with Peter's objections, and here's one more:
the last thing the world needs is yet another way in which datetime
strings can be ambiguous. I think the right answer to the OP's
problem is to push back on the data source.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vladlen Popolitov | 2025-03-26 15:57:53 | Re: Current master hangs under the debugger after Parallel Seq Scan (Linux, MacOS) |
| Previous Message | Robert Haas | 2025-03-26 15:41:13 | Re: vacuum_truncate configuration parameter and isset_offset |