fix: reject MSSQL database name with connection-string separator - #42077
Merged
Conversation
subrata71
approved these changes
Aug 3, 2026
2 tasks
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.
Description
reject MSSQL database name with connection-string separator
Fix
CE/EE sync
Merge this PR first. The hourly CE→EE sync propagates it to EE.
EE counterpart
EE PR: https://github.com/appsmithorg/appsmith-ee/pull/9409
EE CI when this PR was opened: passing (ci-test|ci-test-limited, ci-test-result|ci-test-limited-result green).
Tracking
Linear: https://linear.app/appsmith/issue/APP-15746
Automation
/ok-to-test tags="@tag.All"
🔍 Cypress test results
Tip
🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/30679150865
Commit: 3fb8c8b
Cypress dashboard.
Tags:
@tag.AllSpec:
Sat, 01 Aug 2026 03:08:17 UTC
Communication
Should the DevRel and Marketing teams inform users about this change?