Dynoxide 1.6.0 went out on Saturday night and I forgot to write it up, so this is a couple of days late. Most of the release is about PartiQL, and specifically about how much a SELECT reads.
PartiQL reads what DynamoDB reads
Take a query for two orders in one customer's partition:
SELECT * FROM orders WHERE pk = 'customer#42' AND sk IN [ 'order#1' , 'order#3' ]
Enter fullscreen mode
Exit fullscreen mode
DynamoDB treats that as two key lookups. It reads those two items and charges a read for each one, whether the item exists or not. Dynoxide read the whole partition instead and charged for all of it. The result set was right, so nothing failed, but the consumed capacity was whatever the partition happened to weigh. On a customer with a few hundred orders that's a number DynamoDB would never give you.
The same was true for an OR across sort keys ( sk = 'order#1' OR sk = 'order#3' ).…