Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
22.08.17, 23.02.14, 23.08.10, 24.02.6, 24.08.0, 25.01.3
-
None
-
MXS-SPRINT-239
Description
Currently, the `Schema Tree Explorer` limits results to 1000 items per node due to the default `max_rows` setting in the API. This means that if the server has more than 1000 schemas or tables, not all available items are displayed to the user.
The GUI should explicitly set a value for `max_rows` in the query using the user-defined value.
This will be fixed in 25.01.4, as the virtual tree feature was only added in 25.01 to reduce memory usage (DOM pollution). Increasing the `max_rows` value in earlier versions would cause memory issues unless the virtual tree feature is backported to those versions.
Attachments
Issue Links
- relates to
-
MXS-4875 Slowness when changing query tab while schema explorer has a large number of nodes
-
- Closed
-