Fixes for sqlsrv compatibility #139
Open
Conversation
This file contains 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.
Summary
Gets
writeSchema()working and addresses issue with escaped table prefixes/names format in queries for sqlsrv.Reason
Schema file generation and all queries using a model were failing.
Notes
This is a first attempt to fix sqlsrv compatibility so all comments welcome.
Due to the table prefix/name escaping required for sqlsrv, currently you need to specify a
$tablePrefixand set$restrictPrefixtotruein thewriteSchema()call. Then set the table prefix in yoursetPackage()call. This could be improved.Environment
Database:
Application: