Re: Clarification: Jump to a record/PHP paging...

From: Date: Sun, 24 Dec 2006 16:22:26 +0000
Subject: Re: Clarification: Jump to a record/PHP paging...
References: 1 2 3 4 5 6  Groups: php.general 
Request: Send a blank email to php-general+get-246194@lists.php.net to get a copy of this message
Again, in my opinion, that's fuzzy thinking. Sure, Yeti may be in the
monster sub-set, but how much monster it is as compared to Lockness? You need a means, a yardstick, to compare the two with each other. Like, is Lockness bigger than the Yeti while monster-mouse is smaller, or what?
Who the hell cares, I asked for any entry with monster in the description, I didn't say make higher level philosophical debate within your head as to the level of monsteriness. Quit trying to paint shades of gray when all that lies before you is black and white. We have an order, the order in the dictionary, we have a query for which results are returned using the same ordering criterion as in the dictionary.
Rob: If YOU are doing a FULL TEXT search within a description field looking for the word "monster" and reporting all those records that fulfill the search, then I agree with YOU, but that's not what the POSTER was asking. In fact, I already discussed a FULL TEXT search in a previous post re this subject. The poster asked:
... my question is: how might I have MySQL tell me how many records came BEFORE the found record?
So, if he followed your advice/technique, then tell us how many records came before "monster"? I claim you can't.
He has already decided an order so your rebuttal is completely devoid of additional content.
You are arbitrarily inferring that the order was alphabetical, but he did not say that. However, if he had, then please explain how you would use a FULL TEXT search to find the word that came BEFORE "monster"? I would be very interested to see how that's done. We all can learn. Cheers, and Happy Holidays. tedd -- ------- http://sperling.com http://ancientstones.com http://earthstones.com

« previous php.general (#246194) next »