Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Default/last used search & sort options #1533

Open
BlueCobold opened this issue Sep 12, 2022 · 2 comments
Open

Default/last used search & sort options #1533

BlueCobold opened this issue Sep 12, 2022 · 2 comments

Comments

@BlueCobold
Copy link

BlueCobold commented Sep 12, 2022

I am using Realm Studio a lot to update or search for existing entries in a rather large database. I have to type and fill in a lot of simple queries that all look very similar: "name like 'something'" or "ean like '12345'. Whenever I switch views, I have to re-type these queries and also to re-apply the previously selected column-sorting (which is bugging me, because I have to scroll quite far to the right to find the relevant column). It would be very handy to have a solution for this, because it is rather annoying and time-consuming.

What solutions I could imagine for sorting (descending in preference):

  1. Entering an alpha-numeric-string gets automatically used as filter for all string fields of the table via wildcard search (in case this is slow, it could be an "easy mode" option)
  2. Entering a number gets automatically used as a filter for all numeric (match) or string fields (wildcard) of the table (in case this is slow, it could be an "easy mode" option)
  3. Keeping previously entered search-strings for each table when switching the UI between different tables
  4. Storing/selecting pre-made search patterns to easily select from last used to only replace the specific string/number-values

What solution I would prefer for table-column-sorting:

  1. Keeping the selected column and sort-mode alive for all tables, even when switching back and forth between them.
@kneth
Copy link
Member

kneth commented Sep 13, 2022

@BlueCobold Thank you for your suggestions. 1. and 2. might have some surprising results if a column/property has the type mixed but your idea is interesting.

We will add the suggestions to our next prioritisation round.

@BlueCobold
Copy link
Author

Has this been discussed and dismissed or scheduled to the backlog?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants