Repository navigation
Read DBML database schemas as text (#854) - #1094
Merged
Merged
Conversation
A .dbml file (Database Markup Language, dbdiagram.io) is plain text, so it joins the TXT entry like Dart and HiveQL did in #1047: TXT, Markdown, PDF and DOCX go through the text routes. Nothing translates the schema to SQL or draws it as a diagram. Schema 65: the text donut learns "dbml"; custom claims stay put. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
KnifeLemon
added a commit
that referenced
this pull request
Nov 4, 2026
#1094 (DBML) took schema 65 first. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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 changed
A
.dbmlfile (Database Markup Language, the schema language of dbdiagram.io) is plain text, so it joins the TXT entry the way.dartand.hqldid in #1047. It opens the text donut and goes through the text routes: TXT, Markdown, PDF, DOCX and the rest, with the schema kept as it was written.FormatRegistry:dbmladded to the TXT extensions; the comment above the list now names database schemas and [Format]: .dbml #854.dbml; a user's own donut that already claims it keeps it. (Schema 65 may be renumbered if another change takes it first: the.kra~and FLIC PRs add one each, and feat(tools): Add background tool #1081 just took 64.)docs/ENGINES.md: DBML in the text engine's row.Not part of this (FORMAT-RULES rule 5, and what the issue thread said): DBML → SQL and DBML → a diagram. The file is only read as text; nothing translates or draws the schema. No new format id, so
FormatFieldsis unchanged (TXT already has its field and grade).How it was tested
Filee.Core.Tests/ScriptTextTests:shop.dbmlis detected as TXT; schema 64 → 65 learnsdbmlonce and leaves a custom claim alone.Filee.Engines.Tests/ScriptTextTests: a generatedshop.dbmlbecomes a PDF of its text (rhwp) and ashop.txtwith the same text.dotnet build, all ofFilee.Core.Tests(972 passed, 3 skipped, incl.FormatFieldsTests),dotnet format Filee.slnx --verify-no-changes.Closes #854
🤖 Generated with Claude Code