-
Notifications
You must be signed in to change notification settings - Fork 428
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove untested and outdated 'azuresql.sql' #3086
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3086 +/- ##
==========================================
- Coverage 78.84% 78.82% -0.02%
==========================================
Files 377 377
Lines 31259 31259
==========================================
- Hits 24645 24641 -4
- Misses 6614 6618 +4
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All is good! I noticed only one cosmetic issue, no need to take care of it.
@@ -200,11 +200,11 @@ ALTER DATABASE $name_of_your_db SET READ_COMMITTED_SNAPSHOT ON | |||
|
|||
The command above may take some time. | |||
|
|||
Then you need to import the SQL schema from either ``mssql2012.sql`` or ``azuresql.sql`` file depending on which database you are using. | |||
Then you need to import the SQL schema from ``mssql2012.sql``. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor: I think that single grave accents are enough:
Then you need to import the SQL schema from ``mssql2012.sql``. | |
Then you need to import the SQL schema from `mssql2012.sql`. |
This file was outdated, unsupported and untested.
The docs were misleading, because they gave an impression that it was up to date and working.
We can bring it back when a need arises and there is a way to test it.