You are right. Plus, there's already a HABTM add/delete/update behaviour in the bakery that deals with extra fields.
On Wed, Jun 11, 2008 at 12:46 AM, Joel Perras <[EMAIL PROTECTED]> wrote: > > > On Jun 6, 1:14 pm, "b logica" <[EMAIL PROTECTED]> wrote: > > That's not going to work. In fact, if you figured out a way to get > > Cake to make it work, I'd file a ticket to say that it was a bug, not > > a feature. > > > > A "join table" should have only fields which are foreign keys to other > > tables. Its sole purpose is to join records between 2 or more tables, > > nothing else. > > I beg to differ. From Mariano's own blog: http://tinyurl.com/4kbe9q > In Cake 1.2, extra fields in the join models are easy to integrate > into your application. > > There are plenty of situations where additional information in the > join table is useful, the simplest being the date/time that the join > record was created, such as in the prototypical articles_tags example; > sometimes it is useful to know when a particular article was > associated with a particular tag, or vice versa. Other examples could > include an online shopping system, where you would have products, > carts, and carts_products (taken from an old thread on this group). > The logical location to indicate the quantity of a product in a cart > would be in the carts_products join table. > > -Joel. > > > > -- Marcos Aruj Alvarez Ingeniero de Software ------------------------------- [EMAIL PROTECTED] ----- --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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 -~----------~----~----~----~------~----~------~--~---
