Re: select with join of 25 tables crashes mysql database
>Is the design bad?
Yes. Why not have a table of modules and a table of words and, if necessary, a table that relates one to the other. It seems that would reduce this design from 24 tables (each comprising some 180+ columns!) to 3 tables comprising a TOTAL of maybe 8 to 10 columns!
That said, I'm impressed by the performance RJ was able to provide - but are you sure that's not due to some kind of caching?
Either way, a normalised approach (like the one I describe above) will likely offer better performance in the long run.
Subject
Written By
Posted
Re: select with join of 25 tables crashes mysql database
October 05, 2012 05:33AM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.