If the table/view is large and the column is not indexed, you may not want users to search on the field as they could have a poor experience. If someone needs to search a field and can't, they'll let you know and you can go and add an index at that time if necessary. If it's only slow, they may never inform you.
I don't know many that do this intentionally. Most of the time the admin just forgot to change it. I'd also prefer a default of EXACT. It would enable people to search by default and encourage best practices versus every field being set to WILDCARD which introduces its own set of performance issues that most people don't realize.
------------------------------
Steven Shull
------------------------------
Original Message:
Sent: Thu November 25, 2021 08:33 PM
From: User1971
Subject: DB Config: Why would we want the attribute search type to be NONE?
MAM 7.6.1.2:
When creating a custom object in db config (i.e. an imported view):
The Search Type is automatically set to is NONE.
(Imported view; config changes not yet applied)
Question:
Why would we ever want the attribute Search Type to be NONE for a custom object? Why wouldn't the default Search Type be EXACT instead? (allowing us to filter on the attribute in the Advanced Search and List View)
Is there a benefit to having NONE as the Search Type?
Thanks.
#Maximo
#AssetandFacilitiesManagement