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

Wrong byte order on UUIDs in gstat and monitoring output [CORE6472] #6703

Closed
firebird-automations opened this issue Jan 22, 2021 · 5 comments

Comments

@firebird-automations
Copy link
Collaborator

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.

@firebird-automations
Copy link
Collaborator Author

Commented by: @mrotteveel

Could you specify how they are wrong?

@firebird-automations
Copy link
Collaborator Author

Commented by: @aafemt

Like this:
UUID_TO_CHAR output: {E3076F03-B513-47FB-9444-1EA8302D020D}
MON$DATADASE output: {6F03E307-B513-47FB-4494-A81E2D300D02}

@firebird-automations
Copy link
Collaborator Author

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

Fix Version: 4.0 RC 1 [ 10930 ]

assignee: Dimitry Sibiryakov [ aafemt ]

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Resolved [ 5 ]

QA Status: No test => Cannot be tested

Test Details: Discussed with Dimitry Sibiryakov, 28.01.2021.

@firebird-automations
Copy link
Collaborator Author

Modified by: @pavel-zotov

status: Resolved [ 5 ] => Closed [ 6 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant