Disable sorting by any column

[mtrezza]

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

It's not possible to disable sorting in the data browser UI.

Feature / Enhancement Description

Add an option in the dashboard UI (not dashboard config) to disable sorting. For example, when clicking on a column to sort, the sorting could change in the following order:

• sort ascending
• sort descending
• do not sort

Example Use Case

Sometimes it's not necessary to sort data, especially for ad-hoc queries. For ad-hoc queries, mandatory sorting add an unnecessary complexity for unindexed queries.

Alternatives / Workarounds

None in dashboard, only manual data query.

[parse-github-assistant]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!

[MrMartinR]

Hi @mtrezza , I've found some issues/merges related to sorting... not sure if I should put this here, open new Issue or something.. the thing is I had drama with some field.

I created a column (named ‘s’) in the Contact class to test the schema, then I deleted it via Dashboard and via JS SDK but when I click on the dashboard Contact Class, no records are showing, and parse server log complains with error:

error: column "s" does not exist {"code":1,"stack":"Error: error: column \"s\" does not exist\n    at /Users/Martin/Dev/Parse-Server/node_modules/parse-server/lib/Controllers/DatabaseController.js:1164:21\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)"}

If I create the field again (via dashboard or via JS) the error goes away and the records appear

I found the cause in the POST request when I select the Contact Class that returns a 500 error

XHRPOST http://localhost:1337/parse/classes/Contact
[HTTP/1.1 500 Internal Server Error 6ms]
_ApplicationId	"appId"
_ClientVersion	"js3.4.1"
_InstallationId	"8ad5475f-30e5-4a1"
_MasterKey	"masterKey"
_method	"GET"
limit	200
order	"s"  //<-- here is where I realize the problem
where	{}

So, I guess someone has to remove the "order"/sort of the field somewhere before the deletion ?

[mtrezza]

How is this related to this feature request?

[MrMartinR]

I was not sure if this was the right place... when this is done, someone can add this "unsort" feature before the deletion field process ? is this a "bug"? should I add a new Issue?
there are many issues related to sorting (merged/bugs/features/issues..) I was not sure what to do with this info and I just drop it here... 🤷‍♂️

[mtrezza]

Could you open a new server issue? You can always ask in chat where this best fits. I marked your comments as off-topic.