I am of the opinion that it really depends entirely upon what your business-needs are. It begins, of course, with what sort of search capability you intend to provide in your product ... what options you provide and how those options may (or may not) be used together. This, and your database schema, defines what the search strategy or strategies may consist of; what makes sense. And this, in turn, governs the implementation.
The Catalyst framework by-design does not impose any strictures upon how you “must” implement the Model layer. TMTOWTDI™.
Obviously, one thing that must always be in the front of your mind when dealing with user-generated queries is that you must not allow the user to query for the entire world. You must set reasonable limits not only on what the user may ask for, but how much. In your logic, you must know, and know very well, what each query possibility ultimately leads to.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||