Jeremy, Thanks for the reply. I can see where you're coming from. This site is for a single artist, but I suppose that it would still be better to have a single table for the art work and have it related to the images and categories.
Thanks for the advice, I'll try to redesign it. Sean On Wednesday, April 11, 2012 12:53:19 AM UTC-4, Jeremy Burns wrote: > > That sounds like poor database design from a number of angles. If you > wanted to add another category you'd have to add another table. Presumably > these are all tied together with something common like Artist? Then you > could do a find from the Artist model and contain (see the Containable > behaviour) each of the models you mention below. Then place conditions on > the Artist and/or category models to show the entire catalogue or a subset. > > Jeremy Burns > Class Outfit > > http://www.classoutfit.com > > On 10 Apr 2012, at 21:44:55, Sean wrote: > > Good afternoon everyone, > > I have a site I'm working on in 2.1. It is an artists website. I have the > models and controllers for several categories of artwork: CharacterStudy, > Figure, Monochrome and Portrait. > > What I'm trying to do is also create a page that shows all of them at > once, a "Collected Works" page. So far I have hit a brick wall. I don't > need another table in the database, because that would duplicate the > information. I would rather be able to address each table and it's > associated images all at once. > > Does anyone have any ideas? > > Thanks, > Sean > > > -- Our newest site for the community: CakePHP Video Tutorials http://tv.cakephp.org Check out the new CakePHP Questions site http://ask.cakephp.org and help others with their CakePHP related questions. To unsubscribe from this group, send email to cake-php+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cake-php
