On Sun, 2006-12-24 at 11:22 -0500, tedd wrote:
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
2006/12/25, Robert Cummings [EMAIL PROTECTED]:
WRONG! See Martin Alterisio's post for the same thread. You must not
have understood the OP's requirements.
xD
I was starting to think my mails weren't getting through the list, maybe its
nothing else than only a bigger delay than the usual.
On Sat, 2006-12-23 at 12:06 -0500, tedd wrote:
At 11:24 AM -0500 12/23/06, Robert Cummings wrote:
On Sat, 2006-12-23 at 11:05 -0500, tedd wrote:
In my opinion, wrong thinking. You ask how many records appear before
and after a search string result. That's like asking What's the
To solve a problem like yours I ussualy do the following:
First you need to use a deterministic order criteria when displaying the
results, this means that according to the order columns you provide, MySQL
will not have to decide how to order two rows that have the same values for
this columns.
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?
I see now that I did not explain myself adequately.
I think jump to record was the wrong way to put it. So, here goes.
I already have excellent paging functionality working well, based on
a nice tutorial at PHPFreaks.
My problem is that when a user performs a search, I need to display
the
At 9:03 AM -0600 12/23/06, T.J. Mahaffey wrote:
I see now that I did not explain myself adequately.
I think jump to record was the wrong way to put it. So, here goes.
I already have excellent paging functionality working well, based on
a nice tutorial at PHPFreaks.
My problem is that when a
I agree, tedd. And your points about what makes sense are taken.
That being said, the end point of all this is for a search to simply
act like a real person turning the pages of a phone book.
All I need to do is take the user to a desired point within the
records in the database. This is by
On Sat, 2006-12-23 at 11:05 -0500, tedd wrote:
In my opinion, wrong thinking. You ask how many records appear before
and after a search string result. That's like asking What's the
difference between an orange? -- it doesn't make sense.
It makes perfect sense. He has an order to his
At 11:24 AM -0500 12/23/06, Robert Cummings wrote:
On Sat, 2006-12-23 at 11:05 -0500, tedd wrote:
In my opinion, wrong thinking. You ask how many records appear before
and after a search string result. That's like asking What's the
difference between an orange? -- it doesn't make sense.
T.J. Mahaffey wrote:
My problem is that when a user performs a search, I need to display the
page on which their search string is found, but still display ALL
records within the paging of the entire database.
I've since discovered the core of what I need to do:
i would suggest u run the
11 matches
Mail list logo
