Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Configurable Query Log timestamp format #5235

Closed
3 tasks done
sinus-x opened this issue Dec 6, 2022 · 1 comment
Closed
3 tasks done

Configurable Query Log timestamp format #5235

sinus-x opened this issue Dec 6, 2022 · 1 comment
Labels
duplicate Duplicate or merged issues.

Comments

@sinus-x
Copy link

sinus-x commented Dec 6, 2022

Prerequisites

  • I have checked the Wiki and Discussions and found no answer

  • I have searched other issues and found no duplicates

  • I want to request a feature or enhancement and not ask a question

Description

What problem are you trying to solve?

In Query Log, the dates are formatted as M/D/YYYY. While that is natural for US folks, it can be confusing for people outside, as we usually use some form of D. M. YYYY.

Both the system's and container's locale are set to en_US.UTF_8. But even when I added LC_TIME=en_GB.UTF-8 to the container's environment, the format did not change, so I assume it is hardcoded or not respecting the environment variable.

Proposed solution

Add a dropdown to the configuration, or a free text field to add own format string.

Alternatives considered

Respect the LC_TIME environment variable.

Additional information

I have English l10n set in the UI. The version is v0.107.18.

@ainar-g
Copy link
Contributor

ainar-g commented Dec 8, 2022

Hello. The UI uses the date-time format from the browser's locale, so the backend isn't to blame here. You can check your browser's locale here: https://www.localeplanet.com/support/browser.html. Mine has navigator.language: en-GB and a sensible DD/MM/YYYY date format, so you may want to change your browser's settings until the format looks good to you.

The feature request itself is a dup of #1498, so I'll close this one.

@ainar-g ainar-g closed this as not planned Won't fix, can't repro, duplicate, stale Dec 8, 2022
@ainar-g ainar-g added the duplicate Duplicate or merged issues. label Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Duplicate or merged issues.
Projects
None yet
Development

No branches or pull requests

2 participants