[MXS-4056]  If we expand Table or Schema list should be in a sequential order Created: 2022-03-23  Updated: 2022-07-26  Resolved: 2022-07-25

Status: Closed
Project: MariaDB MaxScale
Component/s: maxgui
Affects Version/s: None
Fix Version/s: 22.08.0

Type: Task Priority: Major
Reporter: Naresh Chandra Assignee: Duong Thien Ly
Resolution: Fixed Votes: 0
Labels: None


 Description   

In the Query Editor, If we expand the schema or tables list, it looks like they are not sorted properly. It should be alphabetical format from A to Z or 0 -9 something like that.

For Example:
Databases:
A
B
C
.
.
Z

If we expand A database then the tables should be like below:
A -> a
b
c
.
.
z



 Comments   
Comment by Duong Thien Ly [ 2022-03-24 ]

Hi naresh.chandra@copart.com, this is expected behavior now. I'll change it to a new feature.

Comment by Naresh Chandra [ 2022-03-24 ]

But if directly login to DB through CLI in the DB server, it will be in sorted order. it would be good if we implement this feature.

Comment by Naresh Chandra [ 2022-05-14 ]

Hi Duong/Todd,

Can we implement this in the coming release would be good as the developers are asking multiple times about this issue. Can you please take it up in the next release?

Comment by Naresh Chandra [ 2022-06-17 ]

Hi Duong/Todd,

Can we implement this in the coming release would be good as the developers are asking multiple times about this issue. Can you please take it up in the next release?

Comment by Naresh Chandra [ 2022-07-07 ]

Hi Duong/Todd,

Can we implement this feature in the 22.08 release would be good as the developers are asking multiple times about this issue. Can you please fix this issue in the next release 22.08?

Comment by Naresh Chandra [ 2022-07-25 ]

Hi Duong,

It should sort all the DB objects related to Schema right? like Views, functions, procedures, triggers and tables..etc

Comment by Duong Thien Ly [ 2022-07-25 ]

naresh.chandra@copart.com yes, that's right

Comment by Naresh Chandra [ 2022-07-25 ]

Duong, Thanks for the update.

Generated at Thu Feb 08 04:25:53 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.