docs(connections): retitle the Database parity row — MF is ODBC, not JDBC#9
Merged
Merged
Conversation
…JDBC The competitive-parity row read "Database reader/writer (JDBC/ODBC)" with a bare check in the MF column, which reads as a claim that MessageFoundry speaks JDBC. It does not: MF is pure Python with no JVM, and DB-OUT / DB-IN / db_lookup all connect over ODBC (aioodbc/pyodbc, DSN built in transports/database.py::_build_dsn). Retitle the row transport-neutral and move the mechanism into each engine's own cell (Mirth and Rhapsody are JVM engines, so theirs is JDBC), plus name the generic-ODBC dialect and state the no-JDBC fact explicitly in the MF status cell. `jdbc` now appears in the repo only where it is disclaimed. Docs-only; the CONNECTIONS.md drift guard (tests/test_communications_inventory.py, 77 passed) pins the resource-management section, not this table.
wshallwshall
enabled auto-merge (squash)
July 27, 2026 14:42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The competitive-parity table in
docs/CONNECTIONS.mdtitled a row "Database reader/writer(JDBC/ODBC)" and put a bare ✅ in the MF column. That reads as a claim that MessageFoundry speaks
JDBC. It does not — MF is pure Python with no JVM, and
DB-OUT/DB-IN/db_lookupall connectover ODBC (
aioodbc/pyodbc; DSN built intransports/database.py::_build_dsn).The row is now transport-neutral, with the mechanism moved into each engine's own cell (Mirth and
Rhapsody are JVM engines, so theirs is genuinely JDBC), plus the generic-ODBC dialect named and the
no-JDBC fact stated explicitly in the MF status cell.
jdbcnow appears in the repo only where it is explicitly disclaimed.Why it matters
This is a customer/prospect-facing parity table. A ✅ on a row titled "(JDBC/ODBC)" is the kind of
claim that gets read back to us in an RFP. The honest answer is that ODBC reaches the same
databases — Oracle, DB2, MySQL, PostgreSQL, SQL Server — via
dialect='generic'.Testing
tests/test_communications_inventory.py— 77 passed. That guard pins the resource-managementsection, not this table, so the edit is unconstrained by it; run for confirmation.
Notes
origin/main(9e4e614) before pushing rather than relying on a stale green,since branch protection is
strict:false.forbidden-contentgate was run locally with the real token list loaded(
names=7, estate=13, site_prefixes=1— matching the CI floor), exit 0.