Describe the bug
There are about 100 validation differences I found between DynamoDB and ExtendDB for validations and error messages and codes.
I had an LLM pull my DynamoDB parity tests out of u19r/aux-storage, mainly https://github.com/u19r/aux-storage/tree/main/crates/storage-api/src/routes and adjacent _test files and run them against ExtendDB and write up all conditions and failure in a markdown document.
dynamodb-error-parity.md
Most of the issues are slight mis-wording, extra information, missing information. There are a class of errors that appear to be due to the order in which validations are run, and there are a set of missing validations where ExtendDB fails to return a 400 error.
To Reproduce
Table rows include the operation to run, the payload, the expected output payload, the ExtendDB payload, and an LLM generated note.
Expected behavior
ExtendDB replicates DynamoDB behaviour
Actual behavior
There remain inconsistencies in the 400 errors and some validations remain uncaught.
Environment
- ExtendDB version: 0.1.0
- Operating system: macOS 26
- Rust version (if building from source): 1.94
- Client SDK/driver and version: CLI
- Deployment method (binary, container, source): source
Additional context
If a standalone test suite crate would be helpful to you I can refactor my tests to pull together all dynamodb conformance tests in a new crate.
Checklist
Describe the bug
There are about 100 validation differences I found between DynamoDB and ExtendDB for validations and error messages and codes.
I had an LLM pull my DynamoDB parity tests out of u19r/aux-storage, mainly https://github.com/u19r/aux-storage/tree/main/crates/storage-api/src/routes and adjacent _test files and run them against ExtendDB and write up all conditions and failure in a markdown document.
dynamodb-error-parity.md
Most of the issues are slight mis-wording, extra information, missing information. There are a class of errors that appear to be due to the order in which validations are run, and there are a set of missing validations where ExtendDB fails to return a 400 error.
To Reproduce
Table rows include the operation to run, the payload, the expected output payload, the ExtendDB payload, and an LLM generated note.
Expected behavior
ExtendDB replicates DynamoDB behaviour
Actual behavior
There remain inconsistencies in the 400 errors and some validations remain uncaught.
Environment
Additional context
If a standalone test suite crate would be helpful to you I can refactor my tests to pull together all dynamodb conformance tests in a new crate.
Checklist