On Mon, Mar 13, 2006 at 10:32:55PM +0900, joseph wrote: > mr. maas, > > psychic me ........ you are a man. > > i created an index, no change. but i already knew that because one of > the cases where an index is never used is when > > The key used to fetch the rows is not the same as the one used in the > > > ORDER BY: > > > > which is the case here. > > (index creation stuff follows) > > i'm just going to bite the bullet for a few months and do a massive code > rehaul. move all the matching code preferably to the sql-server. or > pre-compiled C code for the php [ make an extension ]. i think the mb_ > functions in php are very slow ( reportedly ) ... so move those > somewhere else is a good idea. maybe the 'select ... like' clauses to > the sql-server Personally I think you are making a wrong decision. If you think having a store_procedure of what you are wanting to do it may buy you perhaps 1 second of compile time. The problem is design. Put stuff in a pre-compile C code for php, well, i'd like to see that happen but besides that, let me ask you, if you have query 'A' that you are exeucting in php. how long does query 'A' take to execute without using php? blaming mb_* functions on speed isn't even the question of your problems. Curt. -- cat .signature: No such file or directory -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
