On 22/10/2020 09:33, Mark Rotteveel wrote:
>
> On a related note, given time zones are new in Firebird 4, I think we
> should be more strict about them and not introduce ambiguity in their
> syntax, and we should follow the SQL standard requirements, and always
> expect:
>
Agree.
Adriano
On 22-10-2020 13:09, Adriano dos Santos Fernandes wrote:
On 20/10/2020 08:42, Dmitry Yemanov wrote:
This is stil ambiguous.
This is valid in v3:
SQL> select timestamp '22 oct' from rdb$database;
CONSTANT
=
2020-10-22 00:00:00.
SQL> select tim
On 10/22/20 2:09 PM, Adriano dos Santos Fernandes wrote:
SQL> select timestamp '22 oct 20' from rdb$database;
CONSTANT
=
2020-10-22 00:00:00.
But now you can't easily know if 20 is a time zone or a year.
In this particular case that's known
On 20/10/2020 08:42, Dmitry Yemanov wrote:
> 20.10.2020 13:58, Vlad Khorsun via Firebird-devel wrote:
>
>>> AFAIU, it was discussed here in February 2018, thread "Valid date or
>>> not".
>>
>> I've re-read that thread quickly and I saw nor final decision, nor
>> proposition
>> to change (or break)
Whitespace as date separator causes conversion error
Key: CORE-6427
URL: http://tracker.firebirdsql.org/browse/CORE-6427
Project: Firebird Core
Issue Type: Bug
Components: Engine
