Skip to content

docs: name the three top-level update differences, scope the latency sentence - #2

Merged
dynotable-user merged 1 commit into
mainfrom
docs/top-level-update-exceptions
Nov 9, 2026
Merged

dynotable-user merged 1 commit into
mainfrom
docs/top-level-update-exceptions

Conversation

@dynotable-user

Copy link
Copy Markdown
Contributor
  • The README and the migration guide said top-level updates store the same bytes as dynamoose 4.2.0 with no exceptions. Three allowlisted differences are top-level updates: D9, D10 and D14. D10 was filed under nested paths.
  • During a rollout, nested-path updates come from dynotable-orm only: it drops dynamoose's dotted attributes on read (D12), so a read-then-write removes them.
  • benchmarks.md: DynamoDB latency is larger than the dynotable-orm and SDK numbers, not the dynamoose 4.2.0 update and query rows.

Docs only. Gate: format, lint, 391 tests, check:package.

…sentence

- Top-level updates store the same bytes apart from D9, D10 and D14; D10 is not a nested-path case.
- Nested-path updates come from dynotable-orm only during a rollout (D12 drops dotted attributes on read).
- DynamoDB latency exceeds the dynotable-orm and SDK numbers, not the dynamoose ones.
@dynotable-user
dynotable-user merged commit 237a7ee into main Nov 9, 2026
3 checks passed
@dynotable-user
dynotable-user deleted the docs/top-level-update-exceptions branch November 9, 2026 08:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant