SMAT DB – sorting a view re-drives the database search
- This topic has 2 replies, 2 voices, and was last updated 9 years, 9 months ago by
.
-
Topic
-
When we specify search criteria, like a regex / string in the message content, and create a view, and then click on the date column to resort the view, it seems that the entire database is searched again before the data in the view is sorted. Has anyone else seen this behavior? Am I interpreting it right? I tested this theory by opening two GUIs, pointing to a source and target site, resent a message from the source site, and then sorting the view in the target site, and that view picked up the new message.
Its great that it can pick up the latest message, but its not great when I only want to work with the current view. And I want faster response, I don’t want to search the entire database or multiple databases if I had them all selected, just to resort the view.
The same thing happens when I add multiple search criteria. This is a different kind of problem. I want to add multiple search criteria, and then I only want to perform the search once (again, to save time). But if I have three criteria, each time I add one of them, the entire database gets searched again. I want it to wait until I tell it to search.
Peter Heggie
PeterHeggie@crouse.org
- The forum ‘Cloverleaf’ is closed to new topics and replies.
