Untangles the control of the casing and quoting of columns #864
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.
Note that there is only MySQL driver change. If you think this works, I'll do all the others
The casing of table, column and index names are incorrectly linked to the casing of returned associative array keys and the field quoting performed, see #792. This change separates the feature into distinct methods solely for the feature, and deprecates previous methodologies
@dregad , I am quite happy with the way this has turned out. This removes all of the previous methods of controlling the casing and quoting in core, data dictionary and active records, and replaces all of it with just 2 ADOConnection methods:
So looking at a CreateTableSQL, we can see the changes
Quoting = 0, Casing = 0
Quoting = 1, Casing = 1
Quoting = 1 Casing = 2