Commentary on large DB issues -- is this a problem?

dalecosp

Anyone wanna comment on this? Just been sitting there quite a while; I wondered if his concerns were commonplace, or not.....

http://www.phpbuilder.com/board/showthread.php?threadid=10233013

jstarkey

I'm totally lost. What's the question?

jayant

i could be realted to 'searching related efficiency issues'

goldbug

Originally posted by jstarkey
I'm totally lost. What's the question?

Yeah, ditto.... what's the question exactly??

Weedpacket

I dunno, but it sounds like RPC would be the solution.

jstarkey

Thinking about this, I think Dale was posting a funny.

It sounds to me, now, like the person is trying to create a form element with 20,000+ options.

Weedpacket

No, I think the problem was that the person was trying not to create a form element with 20,000+ options.

Been there.

jstarkey

There has to be a hierarchy that can be implemented. The narrowing down is obviously not going to happen in one click.

dalecosp

Well, quite possibly another 'mea culpa.'

I think I read his post, understood a few things he was attempting to describe, and then suffered a 'brainfart' as I posted.

My OP for this thread was basically saying "is 20,000 entries really too large for PHP/SQL to handle?" ... because that seems like it shouldn't be true.

His problem, upon re-reading and trying to keep my brain intact, seems to be "if I tell JavaScript to submit a query based on each key pushed, my application is slower than molasses in Alaska....."

Which might be true.....

[edit]Stray thought: would my shell crap out if I set history=20000 and then tried to autocomplete a command?[/edit]

Whatever his problem, it's gratifying to know that you experienced gents give enough of a rip about my curiousity to start discussion. A round on me??

Moonglobe

Originally posted by dalecosp
A round on me??

why not 😃