We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Submitted by: @aafemt
Assigned to: @aafemt
Database UID is displayed wrongly by gstat, API and monitoring tables. It makes output incompatible with UUIDs stored in data fields.
====== Test Details ======
Discussed with Dimitry Sibiryakov, 28.01.2021.
The text was updated successfully, but these errors were encountered:
Commented by: @mrotteveel
Could you specify how they are wrong?
Sorry, something went wrong.
Commented by: @aafemt
Like this: UUID_TO_CHAR output: {E3076F03-B513-47FB-9444-1EA8302D020D} MON$DATADASE output: {6F03E307-B513-47FB-4494-A81E2D300D02}
status: Open [ 1 ] => Resolved [ 5 ]
resolution: Fixed [ 1 ]
Fix Version: 4.0 RC 1 [ 10930 ]
assignee: Dimitry Sibiryakov [ aafemt ]
status: Resolved [ 5 ] => Resolved [ 5 ]
QA Status: No test => Cannot be tested
Test Details: Discussed with Dimitry Sibiryakov, 28.01.2021.
status: Resolved [ 5 ] => Closed [ 6 ]
No branches or pull requests
Submitted by: @aafemt
Assigned to: @aafemt
Database UID is displayed wrongly by gstat, API and monitoring tables. It makes output incompatible with UUIDs stored in data fields.
====== Test Details ======
Discussed with Dimitry Sibiryakov, 28.01.2021.
The text was updated successfully, but these errors were encountered: