vinniefranco / exandra

88%

main: 88%

LAST BUILD ON BRANCH push-ppztktulqtkz

branch: push-ppztktulqtkz

CHANGE BRANCH

x

Reset

• push-ppztktulqtkz
• add-counter-and-udt
• add_decimal
• al/integration-tests
• docs
• fix-uuid-and-decimal
• fix_typo_in_execute_batch_function
• main
• nil_is_a_curse
• nimble-opts
• push-kusnyzwltvqn
• push-nnwonukzzrxs
• push-nnwpxynwrtlm
• push-snvplkknwzmk
• push-tmzqutopryyv
• push-upsolxnnxnvw
• refs/pull/81/merge
• vinnie/rename-key-options

Build # 60bebfa6973805fc14b5d54e11f6ad3b549fbb91-PR-79

Build Type

Pull #79

github

Committed by noaccOS

Commit Message

fix: uuid types in data structures

the current implementation assumes xandra always returns strings and
avoids loading uuids itself.

this usually works, but has a few drawbacks:
- we're forced to use embedded loaders for data structures, which should
  not be needed as the structures themselves declare their loaders
- these embedded loaders perform the UUID load themselves, attempting at
  loading a string UUID and resulting in an exception

By requiring xandra to send us UUIDs in binary format and performing the
loading ourselves, we avoid the issue above.

The drawback of this is that it is no longer possible to request UUIDs
in binary format to Xandra, but this did not work for values nested
inside maps/sets even before this refactor

Pull Request Pull Request #79: fix: uuid types in data structures

Run Details

2 of 2 new or added lines in 2 files covered. (100.0%)

530 of 605 relevant lines covered (87.6%)

42.18 hits per line