On Sun, 22 Jul 2007, Frederik Holljen wrote:

> One comment about the data stored if used as content structure in a 
> CMS. Typically you will want to store not only the data itself but 
> meta-data as well. Sometimes you want to do filtering on the meta-data 
> e.g I want all nodes below X but only those that are in the "sports" 
> section.
>
> Is this something we want to implement on the level of the Tree 
> component (makes sense because it puts the load on the DB.... it 
> raises complexity though) or do we want to make this up to the 
> application developer to take care of?

I think that this is useful, and it would be sort of trivial to 
implement something later by inheriting from the ezcTreeDb* classes 
where just the fetching methods are overridden to include filtering. I 
think however, that we should focus on that later.

regards,
Derick
-- 
Components mailing list
[email protected]
http://lists.ez.no/mailman/listinfo/components

Reply via email to