Handling Transactions within External Functions in CodeIgniter

As you've observed, the default transaction handling mechanism in CodeIgniter requires manual rollback in case of errors occurring within external functions. To address this issue, a more comprehensive approach is recommended.

1. Encapsulating Transaction Handling in a Model:

According to CodeIgniter's architecture, database operations should be encapsulated within the Model class. This ensures proper data handling and model-view-controller (MVC) separation. External functions should only serve as utilities or helpers.

2. Error Trapping in External Functions:

Within external functions, such as insert_function and update_function2, implement error handling and return FALSE if an error occurs. This will trigger automatic rollback when the transaction is completed.

Example:

public function insert_function($data)
{
    if (!$this->db->insert('transactions_exercices', $data)) {
        return FALSE;
    }

    return TRUE;
}

3. Exception Handling in the Controller:

In the controller, where the transaction is initiated, handle any exceptions that may arise during the transaction and perform necessary actions, such as displaying error messages or logging exceptions.

Example:

try {
    $this->db->trans_start();

    // Call external functions
    $result1 = $this->utils->insert_function($data);
    $result2 = $this->utils->update_function2($test);

    if ($result1 === FALSE || $result2 === FALSE) {
        throw new Exception('An error occurred.');
    }

    $this->db->trans_complete();
} catch (Exception $e) {
    $this->db->trans_rollback();
    // Handle the exception...
}

Note: Ensure that strict mode is disabled in your transaction configuration to allow independent transaction groups, as mentioned in the provided solution.

Alternative Solution:

Alternatively, you can define a custom transaction class that handles error trapping and automatic rollback. This approach can provide central error handling for all transactions.