|
Saturday 26 April 2008 10:52:09 pm
How big can a class be and still work well? I'm working on a project in which one class has surpassed 100 attributes. Some of the items could be grouped into classes and connected via the object relations datatype. However, the content model doesn't require it. To further complicate things, the client would like to import information into this class using ezodf import. To make this as easy as possible, this class should stay intact, as ezodf can't import one document into several related objects of different classes--right? If I keep it as one huge class, will I encounter performance problems? If we end up NOT being restricted to one class by the ezodf limitation, should I break this large class into several smaller ones? What's a good guideline for a maximum class size? Incidentally, the class consists mainly of text lines and XML blocks, with a few matrices, 10 images, etc. Many thanks!
Granite Horizon, Certified Developer of eZ Publish Web Solutions
Provider of the SaaS Solution Granite Horizon In The Cloud | http://granitehorizon.com/cloud
http://granitehorizon.com | +1 916 647 6350 | California USA | @granitegreg
Blog: http://granitehorizon.com/blog
|
