Skip to content

MCPDBWizard for MariaDB 2.0.46

Latest

Choose a tag to compare

@srmadscience srmadscience released this 15 Nov 19:18

The console's Runtime page now lists the SQL statements a server was built without, and why. No
regeneration needed to see the list; regenerate to get the clearer reasons.

docker pull ghcr.io/srmadscience/mcpdbwizard-mariadb:2.0.46
docker pull docker.io/srmadscience/mcpdbwizard-mariadb:2.0.46
  • New: skipped SQL statements are shown on the Runtime page. When MariaDB cannot describe a
    statement in a config — most often because it names a table that is not in the database the
    config connects to, since an unqualified name is looked up there — the statement gets no tool,
    while the build still succeeds and the server still starts. Until now the only trace was a
    warning in the generation log, so a server could quietly come up with fewer tools than its config
    asks for. Each config's row now shows SQL statements not exposed, naming every such statement
    with the reason, whether the server is running or stopped.
  • Improved: the reason names the database's error. A statement that could not be described
    used to be reported as "it produced no metadata". It now reads, for example,
    the database could not describe it: Table 'mcpdemo.hotels' doesn't exist. This comes from the
    generator, so a server needs to be regenerated (press Start) before its row shows it.