Skip to content

feat(dbConnection): sticky writer during open transaction for getReader() - #8

Merged
Headgent merged 2 commits into
developfrom
feature/260810_sticky_writer_tx
Aug 10, 2026
Merged

feat(dbConnection): sticky writer during open transaction for getReader()#8
Headgent merged 2 commits into
developfrom
feature/260810_sticky_writer_tx

Conversation

@Headgent

Copy link
Copy Markdown
Contributor

Automatisierter Update-Release. Zielversion: v1.1.0

Opt-in ConnectionPoolConfig flag stickyWriterDuringTransaction: bei offener Writer-Transaktion liefert getReader() den Writer (gleiche Health-Pruefung wie getWriter()). Default false, kein Verhaltensaenderung fuer Bestand. Tests: 192/350 inkl. Sichtbarkeits-Integrationstest auf MySQL, Postgres, SQLite.

https://claude.ai/code/session_01B3myqC1R5NcWWMHxDh6zBH

…er()

Add opt-in ConnectionPoolConfig flag stickyWriterDuringTransaction; when set and
the writer has an open transaction, getReader() returns the writer (same health
check as getWriter()) instead of an independent reader, so reads inside a
transaction see the same uncommitted state. Default false, no behavior change
for existing consumers.

Claude-Session: https://claude.ai/code/session_01B3myqC1R5NcWWMHxDh6zBH
…okumentiert

Beschreibt Config-Flag stickyWriterDuringTransaction, Health-Semantik,
getReaders()-Topologie-Auskunft und die zwei Grenzen (Repository-Caching,
Kernel-Wiring) laut ZUG5-Baustein2-Plan Phase 2.

Claude-Session: https://claude.ai/code/session_01B3myqC1R5NcWWMHxDh6zBH
@Headgent
Headgent merged commit 423c564 into develop Aug 10, 2026
3 checks passed
@Headgent
Headgent deleted the feature/260810_sticky_writer_tx branch August 10, 2026 07:11
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