Dates not displaying correctly in tables vs text

[Bryon-Abbott]

VSCode Mysql-Shell-Plugin Date Issues

I am experiencing an issues when displaying data via the mysql-shell-plugins associated with Date fields.

When data is displayed via a table in the mysql-shell-plugin, the dates displayed are a day earlier than the database.

I am guessing this is something to do with the Timezone default for VSCode or the mysql-plugin but not sure where to configure this?

Query via Terminal / mysql - OK

mysql> select * from aaExchangeRates where erDate between '2024-03-26' and '2024-04-05';
+------------+--------+---------+
| erDate     | erEUR  | erUSD   |
+------------+--------+---------+
| 2024-03-26 | 1.4711 | 1.35720 |
| 2024-03-27 | 1.4701 | 1.35870 |
| 2024-03-28 | 1.4632 | 1.35500 |
| 2024-04-01 | 1.4592 | 1.35740 |
| 2024-04-02 | 1.4609 | 1.35720 |
| 2024-04-03 | 1.4642 | 1.35370 |
| 2024-04-04 | 1.4666 | 1.35040 |
| 2024-04-05 | 1.4723 | 1.35980 |
+------------+--------+---------+
8 rows in set (0.00 sec)

mysql> 

Terminal Mysql Output - OK

Query via mysql-shell-plugin with Results as Text - OK

sql> select * from aaExchangeRates where erDate between '2024-03-26' and '2024-04-05' LIMIT 0, 1001;
+------------+--------+---------+
| erDate     | erEUR  | erUSD   |
+------------+--------+---------+
| 2024-03-26 | 1.4711 | 1.35720 |
| 2024-03-27 | 1.4701 | 1.35870 |
| 2024-03-28 | 1.4632 | 1.35500 |
| 2024-04-01 | 1.4592 | 1.35740 |
| 2024-04-02 | 1.4609 | 1.35720 |
| 2024-04-03 | 1.4642 | 1.35370 |
| 2024-04-04 | 1.4666 | 1.35040 |
| 2024-04-05 | 1.4723 | 1.35980 |
+------------+--------+---------+

VSCode Mysql Plugin Output - OK
Execute the block and print the results as text

Query via mysql-shell-plugin - Table vs Text - TABLE NOT-OK

When the same query is displayed as a table, the dates are displayed shifted 1 day earlier.
I also noticed that the display format has changed to a local format (MM/DD/YYYY) vs the default (YYYY-MM-DD)
Note the data is selected correctly according to the Where clause but displays as a day earlier.

Here is the environment I am using.

• OS: Linux Fedora 40
• MySQL: Ver 8.4.0 for Linux on x86_64 (MySQL Community Server - GPL)
• mysql-shell-plugins: v1.14.2

[mike-lischke]

This is certainly a timezone issue, because midnight is used for TypeScript Date, if no explicit time is specified. Fortunately, this should be fixed in the upcoming release of the extension.

[Bryon-Abbott]

Thanks Mike, once I figured out it was only in the display in the tables, it became a minor issue but will be good to see if fixed. Bryon

…

On Thu, 16 May 2024 at 23:59, Mike Lischke ***@***.***> wrote: This is certainly a timezone issue, because midnight is used for TypeScript Date, if no explicit time is specified. Fortunately, this should be fixed in the upcoming release of the extension. — Reply to this email directly, view it on GitHub <#52 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFNSJJBZF3ZQETOU3TCVZOLZCWTGHAVCNFSM6AAAAABH3MIEQGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJWHA4DGNJSGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[JCSViperion]

Thank heavens I came across this, because I did a fresh install of Windows, and reinstalled MySQL multiple times after reinstalling Windows with this problem still persisting. Glad to know its not an error with my setup.

[JCSViperion]

This is certainly a timezone issue, because midnight is used for TypeScript Date, if no explicit time is specified. Fortunately, this should be fixed in the upcoming release of the extension.

Do you know if a fix for this issue is in the works? As of writing this comment, the issue is still present.