| From: | Brendan Jurd <direvus(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | to_timestamp() changes in 8.4 release notes |
| Date: | 2009-04-19 05:12:09 |
| Message-ID: | 37ed240d0904182212s4ba01015jf5c4335d4c481315@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi guys,
I noticed the following item under "Observe the following
incompatibilities" in the 8.4 release notes (E.1.2.4.1.)
* Require to_timestamp() input to match meridian (AM/PM) and era
(BC/AD) format designations with respect to presence of periods
(Brendan Jurd)
For example, input value AD now does not match format string A.D..
This is actually not a change in behaviour. AM/PM and BC/AD have
always required you to use the correct format string w.r.t. periods.
I'm sorry if the comments in my patch submission were vague on this.
I think this item should be pulled from the "incompatibilities" list.
The preceding item (about not having to match case on AM/PM and BC/AD
anymore) is still valid.
Cheers,
BJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-04-19 07:38:54 | Re: 8.4b1: Query returning results in different order to 8.3 |
| Previous Message | Ian Barwick | 2009-04-19 04:22:56 | Re: 8.4b1: Query returning results in different order to 8.3 |