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.

Sign up for GitHub

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

Jump to bottom

Use hexadecimal Statement Fingerprint ID in the URL of the Statement Details page #91875

Open
florence-crl opened this issue Nov 14, 2022 · 0 comments
Open

Use hexadecimal Statement Fingerprint ID in the URL of the Statement Details page #91875

florence-crl opened this issue Nov 14, 2022 · 0 comments
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-observability

Comments

@florence-crl
Copy link

florence-crl commented Nov 14, 2022 •
edited by exalate-issue-sync bot
Loading

Is your feature request related to a problem? Please describe.
Currently, the Statement Details page URL uses the fingerprint id in int64 format, as mentioned in this comment. For example:

http://127.0.0.1:26258/#/statement/true/4705782015019656142?appNames=

However on the Statements page, the Statement Fingerprint ID column has the ID in hexadecimal format, such as 414e4bcf73ab23ce.

Describe the solution you'd like

For consistency, it would be helpful if the Statement Details page URL uses the fingerprint id in hexadecimal format. For example:

http://127.0.0.1:26258/#/statement/true/414e4bcf73ab23ce?appNames=

Jira issue: CRDB-21465

Epic CRDB-32130
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-observability
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@florence-crl