I suggest that you use an indexer like tsearch2 or lucene / xapian / ...
Indexes cannot be used with the LIKE operator.
José de Paula Eufrásio Júnior wrote:
What's the better form of doing that? To minize DB usage and stuff...
--
Julien Cigar
Belgian Biodiversity Platform
On 11/29/06, José de Paula Eufrásio Júnior [EMAIL PROTECTED] wrote:
What's the better form of doing that? To minize DB usage and stuff...
That all depends on the back end that you'll be using and how portable
you want your code to be. IMHO, for searching a database with large
amounts of
On 11/29/06, Lee McFadden [EMAIL PROTECTED] wrote:
That all depends on the back end that you'll be using and how portable
you want your code to be. IMHO, for searching a database with large
amounts of text, MySQL's full text indexing and searching features are
unparalleled[1]. With a few
On 11/29/06, José de Paula Eufrásio Júnior [EMAIL PROTECTED] wrote:
Responding to myself: mixing InnoDB and MyISAM seems impossible. Looks
like if a key on refers to other table, both table have to use the
same engine... As I use a lot of many-to-many, I ended with all my
tables MyISAM :P
On 11/29/06, Lee McFadden [EMAIL PROTECTED] wrote:
And how I create arbitrary queries like that:
select post_title, post_body from post where match (post_title,
post_body) against ('nasty midgets');
on SA?
match_query = post_table.select(MATCH (post_title, post_body) AGAINST (:q))
