Skip to content

Add SQLite-backed RDS Data API execution - #47

Merged
damianh merged 2 commits into
mainfrom
dh/rds-data-api-sql
Nov 12, 2026
Merged

damianh merged 2 commits into
mainfrom
dh/rds-data-api-sql

Conversation

@damianh

@damianh damianh commented Nov 12, 2026 •

Copy link
Copy Markdown
Owner

Emulated RDS clusters previously had no database behind them, so Data API statements could not run. This adds an isolated in-memory SQLite database per cluster and wires its lifecycle to cluster creation, deletion, reset, and MicroStack shutdown.

The Data API now executes SQL with parameter binding and result mapping, supports atomic batch writes and transaction commit/rollback, and returns explicit errors for invalid SQL and unsupported values. The documentation explains the SQLite dialect and its differences from Aurora/PostgreSQL/MySQL. Integration tests cover query results, affected-row counts, parameters, transactions, batch behavior, and cluster lifecycle.

Validation: 31 focused RDS Data API tests passed; Linux x64 Native AOT publish succeeded.

Fixes: #31


Read this PR faster    Follow each request

Add per-cluster in-memory SQLite databases and connect the RDS Data API execution, batch, and transaction operations to emulated clusters. Cover SQL behavior and lifecycle with integration tests, and document SQLite compatibility.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@coldtea-pr-lens

coldtea-pr-lens Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
  • Redraw · drawn at 3471262, the branch has moved on

Architecture

Walkthrough of In-memory SQLite execution for RDS Data API, in six steps

Read this PR faster

Inside the changed components — 1 view

Component view — RDS Data execution engine

Lifecycle coordination and SQL execution between RDS, RDS Data, and SQLite stores

Architecture view of Component view — RDS Data execution engine in damianh/microstack

Data flow

Data flow diagram for damianh/microstack at 3471262

Follow each request


Review

1 finding on the diff · reviewed 3471262

Tip

Click the link under each diagram to open it on a canvas you can zoom, pan and step through

🪧 More tips
  • Run npx skills add coldteadotai/pr-lens, then tell your coding agent: "Diagram the change you just made with PR Lens and attach it to the pull request."
  • Run npx @coldtea/pr-lens-cli analyze --base origin/main on a branch, then npx @coldtea/pr-lens-cli render .pr-lens/graph.json. Same lenses, your own model key, before the pull request exists
  • The diagrams are links. Click one to open it on the canvas, then press W or click play to walk through the change
  • Open a diagram on the canvas, then press W or click play to walk through the change one step at a time
  • The CLI's render reads .github/pr-lens.yml and applies your renames, exclusions and lane pins at draw time
  • Set github.comment.collapsed: true in .github/pr-lens.yml to fold the comment behind one View architecture… row. Drawing still runs as before
  • Set github.draw: on-demand in .github/pr-lens.yml and PR Lens stops drawing pull requests on its own. Comment @pr-lens draw on a pull request when you want that one drawn
  • Add .github/workflows/pr-lens.yml with coldteadotai/pr-lens/packages/action@v0 and your model provider's key as its api-key to run PR Lens from your own CI. Any /chat/completions endpoint works
  • After a push, tick Redraw to draw the latest commit
  • Switch GitHub to dark mode and the diagrams follow. The moving dots are this pull request's data in motion
  • Set github.description: false in .github/pr-lens.yml to stop PR Lens adding buttons to your PR descriptions

Thanks for using PR Lens! It's free for OSS. If it helped, a star helps other teams find it.  Star PR Lens on GitHub

Preserve the updated EventBridge registration, prevent cross-account access to cluster databases, and retain the admin notice expected by CI.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@damianh
damianh merged commit e7ee4c5 into main Nov 12, 2026
1 check passed
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.

RDS Data API: execute SQL against emulated database resources

1 participant