Thanks Massimiliank, I did consider doing this but in that in that case I need to write the whole class from scratch so no getters and setters etc which I was hoping to avoid.
-----Original Message----- From: symfony-users@googlegroups.com [mailto:symfony-us...@googlegroups.com] On Behalf Of Massimiliano Arione Sent: Thursday, 11 February 2010 12:02 AM To: symfony users Subject: [symfony-users] Re: Model with no DB requirements. Just define your object as a class in lib/model. On 9 Feb, 01:35, "Pat Fong" <pf...@globaldatacompany.com> wrote: > Occasionally I come accross an object that I need in my application > which doesnt require being saved to the DB. > > I usually define this object through the schema as I would any other > object and that works fine. I guess the problem I have is that it > creates unessecary tables in the DB, not a big deal but not as clean > as I would like. > > Is there any way to avoid this or a better approach that someone could > suggest ? > > Cheers, > Pat -- You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-us...@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. -- You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-us...@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.
