Friday 18 April 2003 8:02:20 am
I've been looking at the implementation of the content module and the whole attribute stuff strikes me as being kinda inefficient by cramming everything into the same table. Why doesn't content just create a new table for each class with fields for each of the attributes? (And a meta table to describe field much like it is now). Another field containing a readily assembled XML representation of the row would be great for caching, I suppose. Seems to me that would be a much more efficient way to store the data AND it would make it much much easier for modules to operate on the data. It could pose a few problems for searching though (mostly because you need to search through all tables instead of one). I mean don't get me wrong, I love the functionality of the content module, it just runs too slow. Most of the design is really elegant and easily the best open source CMS code I've ever looked on but this strikes me as rather weird. Maybe there are reasons to this I don't get so please enlighten me.
Visit http://triligon.org
|