[liphp] Big MySQL problem

[Sean McCorkle]

> I had a similar problem however it was due to poor query design.  Certain
> queries would bog down my server big time. I had to re-evaluate the design
> of my database, rebuild an index or two, and either rewrite certain
> queries or eliminate them completely from my app.

   related:
     A common mistake is to do a join on two tables without some sort
     of relational constraint, like "where table1.col1 = table2.col2".
     The server then performs a cartesian join, giving you NxM rows,
     where N and M are the numbers of rows of table1 and table2.  If both
     are large, it can hose you.

=sean
-------------------------------------------------------------------------------
Sean R. McCorkle           mccorkle@bnl.gov   | Haven't you heard, that aside
Genome Groupph  | from the details, there's
Biology Departmentfax | nothing further to be found?
Brookhaven National Laboratory                |    --Master Dogen's 300 Koan
Upton, New York  11973                        |      Shobogenzo  (commentary)