docs(qwp): document the 7.1.0 UUID byte order for C, C++, and Rust

[mtopolnik]

Documents the C, C++, and Rust client behavior that shipped in c-questdb-client 7.1.0. Split out of #516, which keeps the Python changes until the Python client 5.1.0 is released.

Changes

• C/C++ and Rust client pages: UUID values cross the API in canonical RFC 4122 byte order, except the row-buffer call that takes the two 64-bit wire halves. Binary Arrow columns land as BINARY unless they claim UUID or LONG256 through arrow.uuid / questdb.column_type field metadata or a per-column override, with examples. A caution box covers the silent behavior change for code written against 7.0.0. Also documents the scope of in_doubt for low-level flushes and for Rust flush_polars_dataframe.
• Store-and-forward and delivery semantics: corrects the replay guidance. wireSeq is connection-local and does not deduplicate replayed frames; suppressing duplicates needs table-level DEDUP UPSERT KEYS with stable row identity.
• QWP/WebSocket wire protocol: notes how the UUID wire encoding relates to RFC 4122 order and which client calls reverse it. The sentence lists C, C++, and Rust; docs(qwp): document canonical RFC 4122 UUID byte order #516 adds Python once 5.1.0 ships.
• Version references: the behavior-change notes name 7.1.0, the release that contains c-questdb-client#186, and the C/C++ FetchContent example pins the 7.1.0 tag.
• Changelog: entries for the above under October 2026.

Related

• c-questdb-client#186 (UUID byte order and binary column claims), c-questdb-client#195 (in_doubt scope)
• docs(qwp): document canonical RFC 4122 UUID byte order #516 (remaining Python 5.1.0 documentation)

Validation

• npm run build, which fails on broken links and anchors

🤖 Generated with Claude Code

[github-actions]

🚀 Build success!

Latest successful preview: https://preview-589--questdb-documentation.netlify.app/docs/

Commit SHA: 195290e

📦 Build generates a preview & updates the link on each commit.