chore(examples): add SQL Server DDL import test case and README #683
+47
−0
Conversation
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
|
@Kundan-CR7 is attempting to deploy a commit to the dottle's projects Team on Vercel. A member of the Team first needs to authorize it. |
1ilit
reviewed
Nov 10, 2025
Member
1ilit
left a comment
1ilit
left a comment
There was a problem hiding this comment.
thanks for the pr, but there is no need for this
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.
This PR adds a sample SQL Server DDL under
/examples/sqlserver/to help reproducethe import error reported in issue #529.
The file demonstrates SQL Server–specific syntax such as
IDENTITY,GO,and
getdate()that currently trigger parsing errors in DrawDB's import feature.This example can be used by maintainers or contributors to test and verify
SQL Server dialect handling improvements in the future.