What about a field in the images table that is used for ordering and then use 'Images.order_field' as the 3rd parameter in your findAll()
Geoff -- http://lemoncake.wordpress.com On Jul 4, 11:14 am, McFadly <[EMAIL PROTECTED]> wrote: > Hello Bakers - > > I have a situation where I can't agree on the best database schema / > logic for my project. > > Here's a simplified version of my project: > > table: Homes > table: Images > > Each Home will have zero to many Images. Some Images will be "stock" > images that can be used by many Homes. Each group of Images > associated with a Home will be in a user defined and changeable > order. > > Homes HABTM Images would provide the ability to associate images to > homes, but how do I keep them in a specific and changeable order? > > My initial thought is a table: galleries, which has a serialized list > of image_ids, in a particular order. Is this my best bet, or am I > overlooking a possibility? > > Your thoughts and direction, please. > Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
