too many files

On Fri, 21 Jul 2006 16:22:14 -0700, CptDondo staggered into the Black Sun and said:

This is why it's a good idea to think through the design *first*, before starting a large project.

Right... IIRC, there's a comp.lang.php* group or heirarchy, so you might want to post relevant snippets of your PHP code there. I'd take a look at them myself, but the last time I used PHP seriously was when PHP3 was the big thing. The database queries themselves would be a good thing to post. There's probably a subset of comp.lang.* that deals with SQL, but I forget what exactly that is.

I doubt it. It's more probable that a query is doing something suboptimal somewhere, and you're getting tons of results when you want 5 (or something). At one point, a co-worker managed to enter a Bugzilla query that retrieved all 4000 bugs in the database0 and he was ... less than happy about it.1 A more sane query ("all bugs not Fixed or Closed in project N") returned in half a second.

This depends greatly on which database you're using. Are you using My, Postgres, Firebird, DB2, or something else? Anyway, HTH,

0 roughly 3300 of them were marked fixed or closed, TYVM. 1 Bugzilla returned the random quote "The request could not be completed because of Error 0x0032 : Parachuting Weasels" and sat there displayed the header and the quote, and no bugs, for ~3 minutes. This confused him. Oh well....

-- Matt GThere is no Darkness in Eternity-But only Light too dim for us to see Brainbench MVP for Linux Admin mail: TRAP + SPAN don't belong ----------------------------- penguins, is Tux." --MegaHAL