if ($this->db->affected_rows() > 0) { return TRUE; } else { return FALSE; }
or
if ($this->db->affected_rows() > 0) return TRUE; else return FALSE;
or
return ($this->db->affected_rows() > 0) ? TRUE : FALSE;
also(much better)
return ($this->db->affected_rows() > 0);
A better solution I’ve found is to manage the difference between an ERROR and 0 affected rows. 0 affected rows is not necessarily a bad thing, but an error is something you do want to know about:
if ($this->db->_error_message()) { return FALSE; // Or do whatever you gotta do here to raise an error } else { return $this->db->affected_rows(); }
Now your function can differentiate…
if ($result === FALSE) { $this->errors[] = 'ERROR: Did not update, some error occurred.'; } else if ($result == 0) { $this->oks[] = 'No error, but no rows were updated.'; } else { $this->oks[] = 'Updated the rows.'; }
Just some quick hacking there – you should obviously make the code far more verbose if you have other people using it.
The point is, consider using _error_message to differentiate between 0 updated rows and a real problem.
Contact Controller [crayon-66362345f2c87680536061/] Contact_form.php - view [crayon-66362345f2c95993625087/] Contact_model [crayon-66362345f2c9c824563305/] Captcha Helper [crayon-66362345f2ca4789336389/] Notifications_model [crayon-66362345f2cad109720883/] Database…
[crayon-66362345f30d4230243519/] [crayon-66362345f30db238091397/]
[crayon-66362345f3212903787572/] The first parameter specifies the type of string, the second parameter specifies the length.…
Create Controller [crayon-66362345f339a616422014/] 2. Create View File [crayon-66362345f33a1664096216/]
[crayon-66362345f3531256013313/] [crayon-66362345f3537106814795/]
All of the native error messages are located in the following language file: system/language/english/form_validation_lang.php To set…