Access $this->validation->Name inside Models

[eluser]Randy Casburn[/eluser]

However, I like to keep my models from having to worry about the HTTP request because this is the job of the controller.

This will be more philosophical than anything. This is somewhat like a religion...

For a point of clarity I would like to address your point though. By the time the Controller has the data, the Controller should have already done its job and reacted to any events in queue. At this point all that is left is data sitting and waiting to be operated upon. In other words, after the Controller has ensured validation and XSS etc. as stated here (from: Benedikt)

Now, after all data is confirmed and correct, I want it to be saved into the database.

Then the HTTP request (Event) has already been handled and we are in a steady state with nothing to do but process data.

=====

So from a design perspective, you're sitting on a boundary condition (Controller <-> Model) with sanitized data loaded in an object and no events to operate on whatsoever.

Now this is from the CI user guide:

The Model represents your data structures. Typically your model classes will contain functions that help you retrieve, insert, and update information in your database.

And an excerpt from ootips.org (really should read it all): http://ootips.org/mvc-pattern.html

[The model is used] to manage information and notify observers when that information changes. [...] It contains only data and functionality that are related by a common purpose [...]

====

So Benedikt I hope this helps you understand how to choose to put functionality in the Controller or the Model. Please keep in mind this doesn't apply to every case and there are many opinions about these things.

Randy