Hello.
I'm unable to give you suggestions, because I don't see the whole picture of your data structure. Please, next time forward your messages to the list. Chances to receive a good advice are greater. Send good model of your databases (use 'SHOW CREATE TABLE' to represent your tables). Describe relations and what you want to get from your queries in human language, and probably somebody will point you to right direction. M.E. Koch wrote: > Thank you very much so far!! > > In my table right now (not the one I will built up) I changed > the where clause which speeded the search up about 40%!!!!!!! > > -> I wonder why I haven't tried this earlier! (easy things somtimes > are sooo fare away) Thanks for giving me parts of my brian back! > *g* > > After all I think I even have to solve this even different to what > I was writing. > > What do you think about: > extracting the search - letter from searchword, convert it to oct, > strip the > slash > and put it as letter_id into the search-table. Searching will than > just go for int's and this should be fastest. > > the new table would look like > +------+-----------+-----------------------------+ > | id | letter_id | search - words | > +------+-----------+-----------------------------+ > > > Thank you for giving me a new idea how to solve this!!!!! > > have a nice weekend! "M.E. Koch" <[EMAIL PROTECTED]> wrote: -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
