Changing db results in model before passing

Changing db results in model before passing

El Forum
Guest

#10

09-22-2010, 11:01 AM

[eluser]bretticus[/eluser]
Actually, @timotheus, you are absolutely correct. Models are exactly the right place to form your application data. Your use is totally recommended. Controllers should be lean (I typically have problems sticking to that rule.) Ideally, your controllers know what the end user wants when a URL is accessed, controllers then know how to get application data (models) and where to send that data to handle the presentation of it to the end-user (views.) Nothing more.

Messages In This Thread

Changing db results in model before passing - by El Forum - 09-21-2010, 02:45 PM

Changing db results in model before passing - by El Forum - 09-21-2010, 04:26 PM

Changing db results in model before passing - by El Forum - 09-21-2010, 05:40 PM

Changing db results in model before passing - by El Forum - 09-21-2010, 08:30 PM

Changing db results in model before passing - by El Forum - 09-22-2010, 09:53 AM

Changing db results in model before passing - by El Forum - 09-22-2010, 10:01 AM

Changing db results in model before passing - by El Forum - 09-22-2010, 10:21 AM

Changing db results in model before passing - by El Forum - 09-22-2010, 10:26 AM

Changing db results in model before passing - by El Forum - 09-22-2010, 10:37 AM

Changing db results in model before passing - by El Forum - 09-22-2010, 11:01 AM

Changing db results in model before passing - by El Forum - 09-22-2010, 11:38 AM

Changing db results in model before passing - by El Forum - 09-22-2010, 12:05 PM