Date-time parsing is very weak [CORE5750] #6013
Comments
Modified by: @asfernandesVersion: 3.0.3 [ 10810 ] Version: 2.5.8 [ 10809 ] Version: 4.0 Alpha 1 [ 10731 ] Component: Engine [ 10000 ] assignee: Adriano dos Santos Fernandes [ asfernandes ] |
|
Commented by: @asfernandes Fixed in branch work/time-zone-support. Date components separator may be a single one (first and second occurence): dash, slash or dot. Time components (hours to minutes to seconds) separator may be colon. Seconds to fractions separator may be dot. There could not be any separator (other than spaces) between date and time. Spaces are allowed before and after separator characters. |
Modified by: @asfernandesstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 4.0 Beta 1 [ 10750 ] |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Resolved [ 5 ] QA Status: No test => Done successfully |
Modified by: @pavel-zotovstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @asfernandes
Firebird date-time parser accepts non-standard separators, accepting (interpreting) wrong strings.
These are currently considered valid:
SQL> select timestamp '2018-01-01 10 20 30' from rdb$database;
=========================
2018-01-01 10:20:30.0000
SQL> select timestamp '2018-01-01 10,20,30 40' from rdb$database;
=========================
2018-01-01 10:20:30.4000
This is a problem when timezone is introduced, as the zone is separated from the time by a space.
Commits: 53be87c 4812ce8
The text was updated successfully, but these errors were encountered: