Repository navigation
v1.6.0
The crate moves to dynoxide-rs 3.3.0, which adds public items and removes
none. Everything else a user installs carries 1.6.0. The release brings PartiQL
reads, request validation and number handling closer to DynamoDB, so some
requests answer differently: see Behaviour changes and
docs/compatibility-summary.md.
Security
zstdmoves to 0.13.4,zstd-safeto 7.4.0 andzstd-systo 2.1.2 for
RUSTSEC-2026-0391, RUSTSEC-2026-0398, RUSTSEC-2026-0403 and
RUSTSEC-2026-0410. They cover context reuse across streams, seekable and
legacy-frame decompression, and the wasm32 allocator shim. Dynoxide only
compresses import output with a freshzstd::Encoderon native targets, so
none of them reach its code, but zstd is built into the binary with the
importfeature, so it ships in this release.
Behaviour changes
- Expressions refuse attribute names starting with
_unless they use an
ExpressionAttributeNamesalias, as DynamoDB does, in key condition,
filter, projection, condition and update expressions alike. This includes
an import rule'smatchexpression, so a rule matching such an attribute
now needs an alias in itsnames. A rule'spathis unaffected
(#274). - PartiQL reads one partition where DynamoDB does. A
SELECTwhose OR
branches all name the same partition key, or whose sort key is matched with
IN, now reads and charges only those keys, andLimitcounts only their
rows. These used to scan the table or read the whole partition, so their
charges and page counts change. The entries under Fixed give the detail.
Fixed
- An
UpdateItemthat creates its item returns noAttributesfor
ReturnValues: ALL_OLD, whether it usesSET,REMOVEor no update
expression. It used to return the key attributes as the old image.
Captured against eu-west-2 and us-east-1 on 5 November 2026
(#278,
#292, thanks
@alfaproject). - A PartiQL
SELECTon one partition refuses aNOTwritten over a key
attribute inside an OR whose other branch names no key attribute, such as
pk = 'k' AND (NOT sk = 's0' OR x = 0), with DynamoDB'sFilter Expression can only contain non-primary key attributeserror. Every writtenNOT
counts, two as much as one, and so doNOT IN,NOT BETWEEN,IS NOT MISSINGandIS NOT <type>. ANOTwrapping such an OR is refused too, as
is one over an AND such asNOT (sk = 's0' AND x = 0). A partition key of
the wrong type is reported first. On an index the check uses the index's
keys. These used to run, or fail as too complex or as overlapping key
conditions. Captured against eu-west-2 and us-east-1 on 5 and 6 November
2026 (#282). - A PartiQL
SELECTrunsattribute_exists,attribute_not_existsorIS MISSINGon a key beside a branch naming no key attribute, such as
pk = 'k' AND (attribute_not_exists(sk) OR x = 1), as a filter over the
partition, on tables and on both kinds of index. It used to be refused for
overlapping key conditions. Captured against eu-west-2 and us-east-1 on
6 November 2026. - PartiQL
SELECTreads one partition when every OR branch names the same
partition key. It used to scan the table, charging for unrelated rows and
counting them towardsLimit. Separate parameters holding the same key,
including equivalent numeric spellings, use the same partition read.
Captured against eu-west-2 and us-east-1 on 23 October 2026
(#229,
#269, thanks
@jay23606). - A PartiQL OR of sort-key conditions reads only their union within the
shared partition, on tables and on global and local secondary indexes,
including beside a filter too wide to expand. ALimitread that ends on
the last of a set of sort keys, or on a range's closed bound, returns no
NextToken, so two keys underLimit: 1take two pages rather than
three, on an index and underORDER BYtoo.
Read capacity is charged per OR branch, as DynamoDB charges it, so each
requested key costs a read whether or not it exists. Captured against
eu-west-2 and us-east-1 on 3 and 4 November 2026
(#271). - A PartiQL sort-key
INwith more than one value reads, charges and pages
like the OR of its keys, on tables and on global and local secondary
indexes. It used to read the whole partition, sopk = 'k' AND sk IN ['row-1', 'row-3']cost what the partition did and aLimitwalk
kept its token past the last key. Each listed key is charged a read whether
or not it exists, and a last listed key with no item keeps the token for one
empty page, as the OR form does. Captured against eu-west-2 and us-east-1 on
5 November 2026
(#289). - PartiQL accepts
ORDER BYon the sort key when OR branches share one
partition. It used to count that partition more than once and demand the
partition key inORDER BY
(#273). - A PartiQL filter on an attribute an index doesn't project is refused when
OR branches share the index partition key, including through one
multi-valueIN. It used to return no items
(#272). - PartiQL evaluates large OR filters as a tree when expanding their
combinations would exceed the read planner's budget. A partition key
equality beside the filter still reads that partition. Nine, sixteen and
forty pairs of OR conditions now run, with key-type and overlapping-range
checks preserved when the filter exceeds the expansion budget. A string
partition key given1and1.0is refused for its type, where it used to
read nothing
(#225). - Request-member errors follow DynamoDB's wording and order for deep
DeleteItem,PutItemandUpdateItemrequests. AnUpdateItemwithout
a key joins an empty table name or invalidConditionalOperatorwith the
missing-key error, and Query reports a misusedConditionalOperatorbefore
an invalidSelect. A deepPutItem,UpdateItemorDeleteItemreports
every invalid member together, in DynamoDB's order: the enum members, a
missingItemorKey, and a missing or empty table name. As in DynamoDB,
a table name's length and pattern are reported only once those pass
(#262). - ExecuteStatement reads
Limitas any JSON number, as DynamoDB does. A
fraction truncates, so1.5and1.0read as 1, and a value past
2147483647, such as1e+20, one near or past 9223372036854775807, or
1e400, reads every row. These used to be refused with serde's own message
or fail the read. ALimitof-1is refused withMember must have value greater than or equal to 1, echoing the value and listed with the
request's other member errors, and-1e400echoes-2147483648. Captured
against eu-west-2 and us-east-1 on 5 and 6 November 2026
(#287). - Query's
Limitand Scan'sLimit,SegmentandTotalSegmentsread a
number past the range of a double, such as1e400or-1e400, as the
32-bit integer it saturates to, and check it as they check any other
value. They used to answer with a bareSerializationException. ALimit
of0.0or-0.0is reported asValue '0' at 'limit', as0.5is,
where it used to get the message for aLimitof0. Captured against
eu-west-2 and us-east-1 on 6 November 2026. - A number where a string or boolean member belongs, such as
TableName,
SelectorConsistentRead, is named by how it is written, as DynamoDB
names it. A whole number getsNUMBER_VALUE cannot be converted to String
(orBoolean) at any size, including-0,100000000000000000000and a
400-digit number, and one written with a point or an exponent gets
DECIMAL_VALUE, including1e400. In a string member,-0and whole
numbers past 64 bits used to getDECIMAL_VALUE, and anywhere, a number
past the range of a double got a bareSerializationException. Captured against eu-west-2 and us-east-1 on
6 November 2026. - A
PutItem,UpdateItem,DeleteItem,GetItem,QueryorScan
table name is measured in characters, as DynamoDB measures it, so😀😀is
too short and 128 emoji aren't too long.SearchVectorsshares the check.
A deepPutItem,UpdateItemorDeleteItemmeasures it in UTF-16 units,
as DynamoDB does there. --port 0reports the port the server bound. The startup line used to
print the requested address,Dynoxide listening on http://127.0.0.1:0, so
nothing outside the process could tell which port the OS had assigned. The
line is unchanged for any other port
(#277, thanks
@samchungy).