Dynomate 1.18.0

Dynomate now supports Amazon Athena alongside DynamoDB. Connect an account, browse catalogs, databases, and tables, and open a query tab from any table.

Query tabs have two modes. Guided filters build common queries without writing SQL. SQL mode gives you the full editor when you need it.

Workgroups and S3 output locations are configurable. Long-running queries can be cancelled, results export to CSV or JSON, and Athena calls show up in the log console next to your DynamoDB activity. When Athena returns scan-volume metadata, Dynomate surfaces it inline so you can see what a query cost without leaving the app.

DynamoDB table views load the next page as you scroll. Works in table view, JSON view, filtered scans, and queries.

Staged updates now support changes to partition keys and sort keys.

DynamoDB can't mutate primary keys in place, so a key edit is a delete + write under the hood: Dynomate deletes the original item and writes a new one with the updated key. The review dialog flags pending key changes explicitly, so you can see what's about to happen before committing.

Paginated scans and queries used to produce one activity entry per page. A 30-page scan meant 30 log entries.

They now collapse into a single grouped entry representing the action you took: one browse, one scan, one query. The individual page requests are still there if you need to drill in.

Some DynamoDB queries were running up to 10x slower than they should have. Dynomate was rebuilding DynamoDB clients between page requests instead of reusing them, paying the connection setup cost on every page.

Clients are now reused across page requests. Repeat scans and queries are noticeably faster, especially when paginating deep.