No, that's not what I'm saying. Basically, without access to the full database column definitions, I'm proposing this:
Instead of the many=to-many tables (ALWAYS something to send shivers down a DBAs spine!), put Indexes on the columns used in the SQL and rewrite the statements. The resulting statements (based on the examples provided in the Wiki) will be more streamlined and, when run through an EXPLAIN, will show much improved access paths. This has 2 major impacts: 1. The Many-to-many tables don't have to be created and maintained at the time of a scan or rescan. 2. The SQL can speedily access the rows required at run time instead of constantly scanning at least 2 tables tables for each row required. This, to me, explains a lot of the sluggish performance and exponential sluggishness as the database grows. -- larrettp ------------------------------------------------------------------------ larrettp's Profile: http://forums.slimdevices.com/member.php?userid=10191 View this thread: http://forums.slimdevices.com/showthread.php?t=45261 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
