They have very different purposes, it only makes sense to separate them, work with them a bit, and you'll see :)
On Fri, Oct 2, 2009 at 01:58, Keith <kmedli...@gmail.com> wrote: > > That makes sense. Interesting that it's split up like that rather > than all being in a single model class, but interesting nevertheless. > > On Oct 1, 4:48 pm, Gábor Fási <maerl...@gmail.com> wrote: >> You use the Model class when dealing with a single element - like a >> blog entry, or a blog comment; and you use the ModelTable class when >> dealing with the table - like when you retrieve some records from it. >> When retrieving items via the ModelTable class, you get a collection >> of Model objects. >> >> On Thu, Oct 1, 2009 at 22:25, Keith <kmedli...@gmail.com> wrote: >> >> > I'm working through the Jobeet tutorial to learn 1.2 after a long >> > hiatus from Symfony. >> >> > What is the difference between the ModelTable and the Model class in >> > the model/doctrine/ directory? >> >> > When is it appropriate to use each? I'm assuming it has something to >> > do with how requests are processed and the order in which these model >> > classes get processed, but I may have overlooked it or not understood >> > the tutorial if it covered it. >> >> > Thanks for the help! > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
