Re: Avoiding complex mysql selects

2005-07-13 Thread zzapper
On Tue, 12 Jul 2005 18:34:38 -0400, wrote: H, how about using full text indexing? It will be a lot easier to implement and a lot quicker. Can you give more details? -- zzapper vim -c :%s%s*%Cyrnfr)fcbafbe[Oenz(Zbbyranne%|:%s)[[()])-)Ig|norm Vg? http://www.rayninfo.co.uk/tips/ vim, zsh

Re: Avoiding complex mysql selects

2005-07-13 Thread Brent Baisley
Create a full text index that encompasses the fields you want to search in (synopsis, title, keywords). Then format your select to take advantage of the full text index: select * from dbname where match(synopsis, title, keywords) against ('word1 word2 phrase one etc' in boolean mode) You

Re: Avoiding complex mysql selects

2005-07-13 Thread zzapper
On Wed, 13 Jul 2005 09:24:20 -0400, wrote: Create a full text index that encompasses the fields you want to search in (synopsis, title, keywords). Then format your select to take advantage of the full text index: select * from dbname where match(synopsis, title, keywords) against ('word1

Avoiding complex mysql selects

2005-07-12 Thread zzapper
Hi I have a piece of code which will search a series of records for the presence of two keywords $key1 and $key2 (see below) The client now wants more keywords $key1,2,3,4 etc But is there any alternative to mushrooming the the following select??? $wherekeyword =__SQL__ and ( (

Re: Avoiding complex mysql selects

2005-07-12 Thread Brent Baisley
H, how about using full text indexing? It will be a lot easier to implement and a lot quicker. On Jul 12, 2005, at 1:09 PM, zzapper wrote: Hi I have a piece of code which will search a series of records for the presence of two keywords $key1 and $key2 (see below) The client now