feature: [wip] implementation of the rescue functionality of the database server version used #155
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.
Due to some differences between the versions of some databases, I am proposing the use of a feature, where you tell us the version of the database server so we can customize and optimize the
SQL
responsible for sorting alphanumeric recordsgetServerVersion()
With the help of this method, when we use the
getSortSqlByDriver
method to retrieve a specificSQL
from one of the databases supported by laravel, in order to sort alphanumeric values more efficiently, we can tell the method not only thedriver
being used, but also theversion
of the database server being used. This way we can be more categorical in customizing the sorts.ATTENTION
As I had suggested in PR(#149), I am in the current proposal, adjusting the database access ports, for each scenario currently created. This change concerns the following test scenario files:
Taking advantage of the port settings, I added another scenario for testing, this time for supporting the
MS SQL Server
database. These changes can be seen in thecomposer.json
file.