Re: FF3 vs MS Date/Time Template - ERROR: date/time field value out of range
От | Nick Davies |
---|---|
Тема | Re: FF3 vs MS Date/Time Template - ERROR: date/time field value out of range |
Дата | |
Msg-id | AM8PR08MB6356ED063DE822D6D03D8943B63C2@AM8PR08MB6356.eurprd08.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: FF3 vs MS Date/Time Template - ERROR: date/time field value out of range (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-bugs |
Thank you so much, that's a seriously speedy turnaround.
Regards
Nick
From: Tom Lane <tgl@sss.pgh.pa.us>
Sent: 07 December 2024 17:49
To: Nick Davies <Nick.Davies@iliad-solutions.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: FF3 vs MS Date/Time Template - ERROR: date/time field value out of range
Sent: 07 December 2024 17:49
To: Nick Davies <Nick.Davies@iliad-solutions.com>
Cc: pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org>
Subject: Re: FF3 vs MS Date/Time Template - ERROR: date/time field value out of range
Nick Davies <Nick.Davies@iliad-solutions.com> writes:
> In the docs it appears the 'MS' and 'FF3' date time template patterns are identical but the behaviour is different. We also support Oracle which doesn't have 'MS', so we tried to use the pattern 'YYYYMMDDHH24MISSFF3'. This doesn't work, but switching to 'MS' does.
Thanks for the report! The problem seems to be that the FFn codes are
mislabeled with is_digit = false. That causes the preceding SS code
to think that it should eat all the remaining digits, so we end with
seconds = 33123 which of course results in an error.
I went through the other format codes to look for similar errors and
didn't see any.
regards, tom lane
> In the docs it appears the 'MS' and 'FF3' date time template patterns are identical but the behaviour is different. We also support Oracle which doesn't have 'MS', so we tried to use the pattern 'YYYYMMDDHH24MISSFF3'. This doesn't work, but switching to 'MS' does.
Thanks for the report! The problem seems to be that the FFn codes are
mislabeled with is_digit = false. That causes the preceding SS code
to think that it should eat all the remaining digits, so we end with
seconds = 33123 which of course results in an error.
I went through the other format codes to look for similar errors and
didn't see any.
regards, tom lane
В списке pgsql-bugs по дате отправления: