Model and Form

In most cases, I keep my validation rules in the model and have a method in the base model (get_validation_rules()) to return the validation rules. Then my controller can do the following:

PHP Code:

$this->form_validation->set_rules($this->some_model->get_validation_rules());

// Add more rules if necessary

// Validate
if ($this->form_validation->run() === false) { 
    return false;
}

// Since the data is valid, 
// give it to the model
$data = $this->some_model->prep_data($this->input->post());

if ($insert) {
    $result = $this->some_model->insert($data);
} else {
    $result = $this->some_model->update($data);
}

// do whatever else needs 
// to be done before returning 


Since the method to get the validation rules (and prep, insert, and update the data) is in the base model, I have the flexibility to choose when and where I use them without writing a bunch of boiler-plate code for each model. Some models might need a heavier controller to handle odd circumstances, while others might not need much more code than what I've included above (or could even trim that down by handling the decision to insert/update in the model).

I have a handful of odd models to do things like read data from an array (maybe pulled from a file, or even stored in a property in the model) which still use the same methods used in the base model for data access. This allows me to move the data to the database later, if needed, without changing my controller(s) and/or view(s). In many cases, I can do it by just changing the base class of my model or removing the custom (overriding) methods from the model.

Bonfire

Practical CodeIgniter 3
CodeIgniter Testing Guide