Details
-
New Feature
-
Status: Open (View Workflow)
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
This is a feature request requesting to please add support for datetime with time zone literals (ISO 8601).
A valid value with this format would be:
2016-12-10T10:10:10-05:00
As far as I know, we do support part of ISO 8601, which is:
2016-12-10T10:10:10
However, we do not support the trailing time zone literal ("-05:00" in this case).
For reference, this code revision is what mentions the partial support of ISO 8601:
At least the following formats are recogniced (based on number of digits)
...
YYYYMMDDTHHMMSS where T is a the character T (ISO 8601)
Also, this bug is spawned off of the following bug (which was designated "not a bug", thus I wanted to file a feature request for the future):
Thank you for your consideration.
Attachments
Issue Links
- is blocked by
-
MDEV-4912 Data type plugin API version 1
- Closed
-
MDEV-13995 MAX(timestamp) returns a wrong result near DST change
- Closed
-
MDEV-16806 Add Type_handler::create_literal_item()
- Closed
-
MDEV-16852 Get rid of Item_temporal_hybrid_func::fix_temporal_type()
- Closed
- is duplicated by
-
MDEV-18125 JSON_VALUE broken in functions
- Closed
- relates to
-
MDEV-10018 Timestamp with time zone
- Open
-
MDEV-10575 sql_mode=ORACLE: Date and timestamp formats
- Open
-
MDEV-17448 Support DATETIME(6) for ROW START, ROW END
- Open