Hi - James calling in from the UK.
I’m researching backendless for use upgrading a legacy app, I’ve worked thru most of the ‘Missions Map - Starter Pack with Code’ and I am liking what I see. I have a question about how to approach a complex search page.
Imagine an ecommerce app with an orders list page where an admin user can search for orders. In the DB there is a user table, order header table, and order line table. I want to provide a single search page with say 6 search inputs - lets say order number, orderer name, orderer email, product code, product description and order status (pending, delivered, returned, etc).
The concept is that any search field can be used in any combination. So:
- entering an order number only would search for and return only that order number;
- entering a product code would return all orders where that product code is referenced in an order line
So far so good, but…
- entering some part of the orderers name AND some part of a product description would do a combined search matching cases where the name AND the product desc matched.
Quick summary would be ‘whatever search boxes are filled then use those values otherwise do not filter on those things’
That’s a simple example - our legacy app has several of these supersearch pages and one has around 15 search inputs.
The legacy app was built using SQL Server. Our solution in that world was to use the Coalesce function which I can explain further but do not with to mansplain if not needed.
I should also mention that I want to write a blog article about how to accomplish this, so there will be some payback for everyones collective brain-spend.
Thanks in advance.