Bug #117270 Contribution: Report third decimal place for milliseconds
| Submitted: | 22 Jan 2025 16:00 | Modified: | 20 Aug 2025 10:14 |
|---|---|---|---|
| Reporter: | OCA Admin (OCA) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Command-line Clients | Severity: | S3 (Non-critical) |
| Version: | 8.0, 8.4, 9.0 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Contribution | ||
[22 Jan 2025 16:00]
OCA Admin
[22 Jan 2025 16:00]
OCA Admin
Contribution submitted via Github - Report third decimal place for milliseconds (*) Contribution by Marcelo Altmann (Github altmannmarcelo, mysql-server/pull/586#issuecomment-2607042609): I confirm the code being submitted is offered under the terms of the OCA, and that I am authorized to contribute it.
Contribution: git_patch_2268464153.txt (text/plain), 2.79 KiB.
[22 Jan 2025 16:08]
Daniël van Eeden
Related: Bug #84007
[23 Jan 2025 5:08]
MySQL Verification Team
Hello Marcelo Altmann, Thank you for the report and contribution. regards, Umesh
[26 Feb 2025 18:36]
Daniel So
Posted by developer: Added the following entry to the MySQL 9.3.0 changelog: "The mysql client now displays query execution times with three decimal places of precision to show milliseconds. Our thanks to Marcelo Altmann for the contribution."
[20 Aug 2025 7:47]
Daniël van Eeden
I think this bug should have been closed now that the version with the enhancement was released
[20 Aug 2025 10:14]
MySQL Verification Team
Agree, Thank you Daniël. Sincerely, Umesh Shastry
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.056 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.