This is expected behavior for the Query Editor. The value for max_rows is used as a session system variable in the server. In the GUI, the query editor just persists the value in the browser. You can test it via the CLI by querying this

SHOW variables like 'sql_select_limit'

It would not use the value from the GUI.

Hi Duong,

But, when the max_rows option changed to something else other than default(10000), after logout and login, can make it always default would be good.
We are expecting this after logout not in the current session.

Hi Naresh,
This is actually hard to decide. Others may want to keep the value after logging out. Besides, it doesn't have much effect on the user experience. Anyways, this is debatable. So I'll mark this as "Needs feedback", if other users want the same behavior as you suggested, I'll make the changes.

Hi Duong,

As the max_rows=Don't Limit is casuing memory issue for big tables, any how after login to the maxscale they can set it to whatever value they can set it. But
we are expecting not to cause any memory problem on the maxscale instance if its "Don't Limit" option is selected.

At least please do it, only when it is selected max_rows to "Don't Limit" other than this not a problem.

Hi Duong,

As the max_rows=Don't Limit is causing memory issue for big tables, any how after login to the maxscale they can set it to whatever value they can set it. But
we are expecting not to cause any memory problem on the maxscale instance if its "Don't Limit" option is selected.

At least please do it, only when it is selected max_rows to "Don't Limit" other than this not a problem.

OR

Give this as a separate option like SQL_YOG for only Don't Limit option?

Hi naresh.chandra@copart.com,
I think removing the `Don't Limit` option would be the simplest way as you said It could cause memory issues when the user chooses it. So the best option is just to remove it

Hi Duong,

Thanks for the update.

Yes, it would be good if we can remove and also provide range/pagination option if possible.

and one more thing the limit rows option, you may provide separately instead of removing permanently it like SQL yog.
Can you please shift the Run/Stop button and limit rows options like the below screenshot.

Hi Duong,

Any update on this?

HI naresh.chandra@copart.com, I'll remove the `Don't Limit` option in the upcoming release. i.e 6.2.2 or 6.2.3.
About the range/pagination option, there is a ticket for it that you created which is https://jira.mariadb.org/browse/MXS-3952.
About the position of the run button, thank you for the suggestion, we'll consider it.

Hi Duong,

Thanks for the update.