Repository navigation
the grid shows MariaDB, and the engine cards match 1.0.0 again - #80
Merged
Merged
Conversation
MariaDB has no driver of its own: the MySQL provider serves it, so it was missing from the hexagon grid. It now has a card of its own, copied from docs/providers/mysql.md section 1.1, with a new `via: 'mysql'` field that shows it without counting it, the same way the embedded LibreDB store is shown. The count stays forty-one, /databases names it beside the SQL counter, and its REFERENCE line points at the MySQL provider doc. Every card was then checked against the 1.0.0 tag. Agent mode runs statements on seven type-ids there (PostgreSQL, MySQL and so MariaDB, SQLite, DuckDB, SQL Server, MongoDB and Kubernetes), but the cards, the FAQ, the feature limit and llms-full.txt still named the first four. MySQL, MongoDB and Kubernetes now say agent mode runs there, and Couchbase names the current set. The MCP limit says which engines run a query there and which do not. Other cards that no longer matched their provider doc: - Elasticsearch and OpenSearch said "no ER diagrams"; the diagram is offered, there are just no foreign keys to draw. They now name the real absences. - DuckDB: admins are confined to the database file on a seed a standard user can reach. - SQL Server: the agent also reports the estimated plan it admitted with. - Snowflake: PUT and GET were in no source; the card states the absence of bound parameters and multi-request transactions instead. - SNMP: a Set PDU exists and the valve refuses it; the transport names port 161. - MySQL: the stated limit is the open transaction a released pooled connection keeps. The FAQ said fifty-four named engines; it is sixty-eight, as on the grid.
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.
MariaDB was missing from the hexagon grid on the home page and /databases, because it has no driver of its own: the MySQL provider serves it. The MariaDB Ecosystem Hub, which now lists LibreDB Studio, asked for it to be named among the other databases.
docs/providers/mysql.mdsection 1.1. A newvia: 'mysql'field shows it without counting it, the same way the embedded LibreDB store is shown, so the count stays forty-one. /databases names it beside the SQL counter, the llms headings say so, and the REFERENCE line points at the MySQL provider doc.tests/engines.test.tsholds the seven-engine agent set and the uncountedviaengines.bun run gateis green: 233 pass, 0 fail.