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
-
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
- relates to
-
-
- Open
-
-
MDEV-10575
sql_mode=ORACLE: Date and timestamp formats
-
- Open
-
-
-
- Open
-
- links to
(3 relates to, 2 links to)
Activity
| Field | Original Value | New Value |
|---|---|---|
| Link | This issue relates to MDEV-10575 [ MDEV-10575 ] |
| Priority | Minor [ 4 ] | Major [ 3 ] |
| Fix Version/s | 10.1 [ 16100 ] |
| Due Date | 2017-03-10 |
| Labels | contribution foundation |
| Assignee | Alexander Barkov [ bar ] |
| Fix Version/s | 10.2 [ 14601 ] | |
| Fix Version/s | 10.1 [ 16100 ] |
Hi Daniel,
Yes, the following are important (specifically the first one):
...<time>±hhmm
....<time>±hh
I think that part would be worth doing.
| Link | This issue relates to MDEV-10018 [ MDEV-10018 ] |
| Fix Version/s | 10.2 [ 14601 ] |
| Fix Version/s | 10.4 [ 22408 ] |
| Link | This issue is blocked by MDEV-10018 [ MDEV-10018 ] |
| Link | This issue relates to MDEV-10018 [ MDEV-10018 ] |
| Link |
This issue is blocked by |
| Link |
This issue is blocked by |
| Link |
This issue is blocked by |
| Link | This issue relates to MDEV-17448 [ MDEV-17448 ] |
| Link |
This issue is duplicated by |
| Fix Version/s | 10.4 [ 22408 ] |
| Epic Link | MDEV-21086 [ 80548 ] |
| Due Date | 2017-03-10 |
| Assignee | Alexander Barkov [ bar ] | Ralf Gebhardt [ ralf.gebhardt@mariadb.com ] |
| Assignee | Ralf Gebhardt [ ralf.gebhardt@mariadb.com ] |
| Workflow | MariaDB v3 [ 79246 ] | MariaDB v4 [ 130581 ] |
| Description |
This is a feature request requesting to please add support for datetime with time zone literals (ISO6801).
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 ISO6801, 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 ISO6801: At least the following formats are recogniced (based on number of digits) ... YYYYMMDDTHHMMSS where T is a the character T (ISO8601) https://github.com/MariaDB/server/blob/bb2c1a52c61706dde8c525a8887f2d364c0db1eb/sql-common/my_time.c#L269 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): https://jira.mariadb.org/browse/MDEV-11576 Thank you for your consideration. |
This is a feature request requesting to please add support for datetime with time zone literals (ISO6801). 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 ISO6801, 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 ISO6801: At least the following formats are recogniced (based on number of digits) ... YYYYMMDDTHHMMSS where T is a the character T (ISO8601) https://github.com/MariaDB/server/blob/bb2c1a52c61706dde8c525a8887f2d364c0db1eb/sql\-common/my\_time.c#L269 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): https://jira.mariadb.org/browse/MDEV\-11576 Thank you for your consideration. |
| Description |
This is a feature request requesting to please add support for datetime with time zone literals (ISO6801). 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 ISO6801, 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 ISO6801: At least the following formats are recogniced (based on number of digits) ... YYYYMMDDTHHMMSS where T is a the character T (ISO8601) https://github.com/MariaDB/server/blob/bb2c1a52c61706dde8c525a8887f2d364c0db1eb/sql\-common/my\_time.c#L269 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): https://jira.mariadb.org/browse/MDEV\-11576 Thank you for your consideration. |
This is a feature request requesting to please add support for datetime with time zone literals (ISO6801).
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 ISO6801, 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 ISO6801: At least the following formats are recogniced (based on number of digits) ... YYYYMMDDTHHMMSS where T is a the character T (ISO8601) https://github.com/MariaDB/server/blob/bb2c1a52c61706dde8c525a8887f2d364c0db1eb/sql-common/my_time.c#L269 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): https://jira.mariadb.org/browse/MDEV-11576 Thank you for your consideration. |
| Assignee | Alexander Barkov [ bar ] |
| Issue Type | Task [ 3 ] | New Feature [ 2 ] |
| Description |
This is a feature request requesting to please add support for datetime with time zone literals (ISO6801).
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 ISO6801, 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 ISO6801: At least the following formats are recogniced (based on number of digits) ... YYYYMMDDTHHMMSS where T is a the character T (ISO8601) https://github.com/MariaDB/server/blob/bb2c1a52c61706dde8c525a8887f2d364c0db1eb/sql-common/my_time.c#L269 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): https://jira.mariadb.org/browse/MDEV-11576 Thank you for your consideration. |
This is a feature request requesting to please add support for datetime with time zone literals (ISO6801).
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 ISO6801, 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 ISO6801: At least the following formats are recogniced (based on number of digits) ... YYYYMMDDTHHMMSS where T is a the character T (ISO8601) https://github.com/MariaDB/server/blob/bb2c1a52c61706dde8c525a8887f2d364c0db1eb/sql-common/my_time.c#L269 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. |
| Parent | MDEV-10018 [ 56610 ] | |
| Issue Type | New Feature [ 2 ] | Technical task [ 7 ] |
| Epic Link | MDEV-21086 [ 80548 ] |
| Link | This issue is blocked by MDEV-10018 [ MDEV-10018 ] |
| Parent | MDEV-10018 [ 56610 ] | |
| Issue Type | Technical task [ 7 ] | New Feature [ 2 ] |
| Epic Link | MDEV-21086 [ 80548 ] |
| Epic Link | MDEV-21086 [ 80548 ] |
| Link | This issue relates to MDEV-10018 [ MDEV-10018 ] |
| Zendesk Related Tickets | 182965 |
| Description |
This is a feature request requesting to please add support for datetime with time zone literals (ISO6801).
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 ISO6801, 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 ISO6801: At least the following formats are recogniced (based on number of digits) ... YYYYMMDDTHHMMSS where T is a the character T (ISO8601) https://github.com/MariaDB/server/blob/bb2c1a52c61706dde8c525a8887f2d364c0db1eb/sql-common/my_time.c#L269 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. |
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) https://github.com/MariaDB/server/blob/bb2c1a52c61706dde8c525a8887f2d364c0db1eb/sql-common/my_time.c#L269 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. |
| Summary | Please add support for datetime with time zone literals (ISO6801) | Please add support for datetime with time zone literals (ISO 8601) |
| Remote Link | This issue links to "PR#290 (Web Link)" [ 37400 ] |
| Remote Link | This issue links to "PR#330 (Web Link)" [ 37401 ] |
| Labels | contribution foundation | foundation |
Resetting "contribution" label as there're no active pull requests.
ccalender, as indicated the referenced pull request implements the form ...<time>(±hh:mm|Z)
What isn't implemented is the ISO8601 representations of timezone offsets in these forms
Are these important to you? Is it worth doing for completeness sake?
Are the ordinal or week forms of ISO8601 important to you?