product)
acting as flag.
On Nov 26, 4:30 pm, keymaster <ad...@optionosophy.com> wrote:
> forgot to mention, the categories are heirarchical using the tree
> behavior.
>
> On Nov 26, 5:27 pm, keymaster <ad...@optionosophy.com> wrote:
>
> > Suppose one has a need for categories of articles, products,
> > downloads, etc., within the same application.
>
> > What would be a better approach to implementing this?
>
> > 1. having a different categories table/model for each, like
> > article_categories, product_categories, download_categories, etc.
>
> > 2. having a single categories table/model and defining subcategories
> > called articles, products, downloads, and then putting the various
> > article categories under articles, product categories under products,
> > etc.
>
> > 3. having a single model with multiple tables, and dynamically
> > switching the table it uses.
>
> > Option #1 means duplicate tables, models, fields, and validation
> > rules, but might end up being cleaner.
>
> > I am also wary of gotchas I haven't thought of in option #2,3.
>
> > Any suggestions?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to cake-php+unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
No comments:
Post a Comment