For finely tuned database behavior, there are two major characteristics of indexes that should be considered: the order of the fields specified in the index and the sort direction of each of the fields.
For instance, there may be cases where one wishes to create two indexes that use the same columns, but with different order and sort directions to optimize two very different queries.
The only way I can currently do this is to add custom sql in the "Extra SQL" section of a table object. However, this subverts which the index naming and tablespace assignment capabilities of druid and prevents the object from being nicely rendered in database table summary documentation.
For the field order, I recommend adding an index field order dropdown next to each index checkbox in the table summary, which could be a list of numbers from 1 to N for the number of fields currently checked in a given index column.
For the sort order, I recommend addding a small up-arrow/down-arrow toggle button next to each index checkbox in the table summary.
Logged In: NO
i agreee with this because its a guud idea and coold be very usefull to me
also i need to have easy way to a checkbox that creates a independent indexz for the colum without mixing with others
thanks
thank you