Fix schema-qualified TableGroup export names#940
Merged
huydo862003 merged 1 commit intoJul 7, 2026
Conversation
huydo862003
approved these changes
Jul 7, 2026
huydo862003
left a comment
huydo862003
left a comment
Contributor
There was a problem hiding this comment.
Thank you for your contribution 🚀
huydo862003
added
the
PR: Bug Fix 🐛
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
2 participants
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.
Summary
TableGroupnames so exported DBML remains parseable.ModelExporter.Issue
Fixes #927
Lasting Changes (Technical)
DbmlExporter.exportTableGroupsnow emitsTableGroup "name"while still schema-qualifying member table references when needed.Checklist
Please check directly on the box once each of these are done