I will concur with Richter here. It is far better maintenance-wise to
keep all your application logic in the app and not distribute that
around into the database. The only time a view is of use is when an
outside batch-script or cron job might use it as that is not directly
related to your appl
Thank you for your suggestion.
I will rethink my design.
Himanshu
From: Richtermeister
To: Symfony users
Sent: Sat, 26 February, 2011 10:57:44 PM
Subject: [symfony-users] Re: dynamically extending classes
Hi Himanshu,
this seems overly complicated. Since
Hi Himanshu,
this seems overly complicated. Since you're getting the same fields
from the database regardless of which user is logged in, you should be
fine using the same class to access those fields. The model shouldn't
change depending on which user uses it, only different data should be
access
