Skip to content

docs(readme): drop MySQL from interception backends list#73

Merged
hyperpolymath merged 1 commit into
mainfrom
fix/prune-mysql-redis-readme
May 14, 2026
Merged

docs(readme): drop MySQL from interception backends list#73
hyperpolymath merged 1 commit into
mainfrom
fix/prune-mysql-redis-readme

Conversation

@hyperpolymath
Copy link
Copy Markdown
Owner

Summary

Per V-L1-I1: README claimed MySQL interception support, but abi::DatabaseBackend only defines PostgreSQL/SQLite/MongoDB. Drop the MySQL line to match.

MySQL stays in ROADMAP.adoc as a [ ] todo — that's the right place for unimplemented work. Redis is no longer in the README at all (the issue noted it but it's already gone).

Closes

Test plan

  • README backend list matches abi::DatabaseBackend enum
  • ROADMAP still tracks MySQL/Redis as future work

Closes #62.

The README listed MySQL alongside Postgres/SQLite/MongoDB as if it were
a supported interception backend, but `abi::DatabaseBackend` only
defines PostgreSQL/SQLite/MongoDB. Anyone landing on the README would
think MySQL works.

Remove the MySQL line. MySQL remains in ROADMAP.adoc as a `[ ]` todo,
which is the appropriate place for unimplemented work.

(Redis appears nowhere in the current README — already absent. The
issue mentioned it but the README has since been edited.)

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@hyperpolymath hyperpolymath merged commit 4273284 into main May 14, 2026
16 of 18 checks passed
@hyperpolymath hyperpolymath deleted the fix/prune-mysql-redis-readme branch May 14, 2026 14:05
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.

V-L1-I1: prune unimplemented backends (MySQL/Redis) from README, or stub them

1 participant