On 06/06/2012 09:50 AM, tanshu wrote:
Hi,
I am sorry if this has been asked before, but I couldn't find the
answer anywhere. I am relatively new to python / pyramid and have
developed a few test programs. I come from a C# background and could
not figure out what the best pattern is to lay out database access.
In C# etc, you create separate dal classes and go with n-tier
architecture, should I just the validation, save, update in the
controller in pyramid or create separate classes. Any help will
be gratefully appreciated.
My preference lately is to move all business and data logic to model
methods and use views only to do views: ACL and context setup for
template and response, a glue between involved models, templates,
request data and response construction.
--
.oO V Oo.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" 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/pylons-discuss?hl=en.
