Question

I am currently using Doctrine’s DBAL library for MySQL interfacing and have currently built a structure around:

public function update(array $data, $id)
{
    return $this->db->update($this->table, $data, array('id' => $id));
}

Which of course returns the number of affected rows. The issue now is that I perform certain actions after updates that should trigger upon a successful update. Under the current system if I was to “edit” a record (showing the form only) and immediately hit save it returns an error since I check the result of the update function above. This not only displays an error in my site but also prevents the other “successful update” actions from running.

Is there a way to see if an update failed to run outside of the affected rows? Can I just ignore this completely and assume the update will always work? Would trapping Exceptions be enough to catch any fatal errors?

Answer 1

You can assume that update will always work. Exceptions will be thrown for major problems such as invalid field names or constraint violations. Consider making a few test cases just to convince yourself of this.

Be aware that no escaping is done with the update() method so it up to you cleanse your data.