Repository navigation
docs: document the UUID byte order in the Rust and C/C++ clients - #542
Merged
Merged
Conversation
|
🚀 Build success! Latest successful preview: https://preview-542--questdb-documentation.netlify.app/docs/ Commit SHA: d7d5a51
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two UUID byte-order problems on the client pages.
The Rust buffer setter table listed
column_uuidwith nothing aboutloandhi. Taking the client's own wire-layout wording as the caller-facing split silently stores a byte-reversed UUID, so the page now states thathiis the most significant 64 bits, shows theUuid::as_u64_pair()call against the(lo, hi)argument order, and gives the canonical-bytes equivalent.The chunk setter entries said "in QuestDB wire order" (Rust) and "16 bytes" (C and C++). Since questdb/c-questdb-client#186 the chunk setters take canonical RFC-4122 bytes and byte-swap internally, so both entries now say canonical RFC-4122 order.
Includes the September 2026 changelog entry.
Dependencies
The chunk wording matches c-questdb-client
main. That change is merged upstream but not in the published 7.0.0 crate, so it describes the next client release. The row-API wording applies to both.