Joining collections by small Uint8Array's checks by reference rather than content

[Tomaszal]

• I've validated the bug against the latest version of DB packages

Describe the bug
Collections joined by small Uint8Array comparisons are checked using reference, when they should be checked by content

To Reproduce
https://stackblitz.com/edit/vitejs-vite-jwhabpic

If data initialization on lines 10-12 is moved up to the root, references will be consistent across both collections, and join operation will work correctly. However, it should also work in the initial arrangement if Uint8Array's are compared by content

Expected behavior
Using the provided reproduction, "Joined by ID" and "Joined by name" should result in the same output

Additional context
Related to #779

[kevin-dp]

Closing this as won't-fix. We are considering joining on Uint8Array values out of scope due to the added complexity and the ambiguity around what size threshold should trigger content-based comparison vs. reference comparison.

We appreciate the detailed reproduction, but this is a known trade-off we've accepted. If your use case requires joining on binary data, we'd recommend converting the Uint8Array values to a comparable primitive (e.g., a hex string) before using them as join keys.

[Tomaszal]

Understandable, although I wonder if #779 should be reverted then? Because the way it is right now is even more ambiguous, as the eq comparisons behave differently when used in query vs join

[KyleAMathews]

Yes, I'll revert it