@JLRDW - Thank you! Scout looks like something I should perhaps look into. My goal is to allow a flexible query building process on as many of the fields as possible. Translation: Not so much coding and more dynamic -- especially if if I add new fields down the road.
Before I decided to use Laravel, I had actually almost built something using MySQL schema info tables and the comment field. Here is a snippet or two:
Array to hold comparison types:
private $operators_arr = ['='=>'equals', '!='=>'not equal to', '>'=>'greater than', '>='=>'greater than or equal to', '<'=>'less than', '<='=>'less than or equal to', 'like'=>'like', 'like'=>'begins with',
'contains'=>'contains'];
Array to hold form field types (html):
private $answer_type_arr = ['textbox'=>'1', 'datepicker'=>'3', 'yn_bit'=>'4', 'dd_specific'=>'5'];
Then in the comments of the field, I planned to add 'Field Label|1' -type conventions for those fields which should be searchable.
I built stored procedures to access the table/column information that started something like this:
select concat(table_name, '.', column_name) as column_name, column_comment from
information_schema.columns where (table_name like ...) and COLUMN_NAME not in (place to leave out columns that are not to be searched) or COLUMN_NAME not !=;
Then I had built a form that could be hidden and displayed on the management page and additional rows added as needed (with plus sign/minus sign buttons) to build the search parameters for the search.