Model Example is Bad in User Guide

[eluser]toopay[/eluser]

...as we don’t know with any certainty that the input will be pulled from the post data.

I think, that reference User Guide, describe it with something like this...

bla bla...For example, let's say you use CodeIgniter to manage a blog.

Of course, this is just a sily example, as you can read from its notes

Note: For the sake of simplicity in this example we’re using $_POST directly. This is generally bad practice, and bla bla

This example, if you want to mention it too, even doesn't assume that you use Form Validation Class, which more OOP.

I agree, that the example was to simple or even become bad practice. But, it still show anyone who read it, that CodeIgniter use MVC pattern, to separate your application workflow into :

Model => are PHP classes that are designed to work with information in your database.
Conroller => are PHP classes that contain your Bussines Logic
View => Final Output