Fix #19749 - Descending index being converted to ascending #19956
+32
−3
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.

Description
Please describe your pull request.
This pull request fixes an issue where descending index columns (
D) were not preserved when editing an index. When a column had a collation ofD(meaning DESC), phpMyAdmin generated an index definition without specifying any direction.Since MySQL and MariaDB default to
ASCwhen no direction is specified, theoriginal
DESCwas effectively lost.This bug was originally reported against the
QA_5_2branch:Fixes #19749
The fix updates the SQL generation logic to explicitly map column collation
values:
A→ASCD→DESCensuring the original index direction is preserved correctly.
Before submitting pull request, please review the following checklist:
Signed-off-byline as described in our DCO. This ensures that the work you're submitting is your own creation.