KohanaPHP » Kohana v3.x » Database

"Nested" transactions may not be the right idea to generalize since every database supports savepoints. Instead of hiding savepoints, I'm thinking we should leverage them and abstract BEGIN / COMMIT somewhat.

I'll try and write some code in the next couple days.

¹ Oracle is in a transaction unless AUTOCOMMIT has been set to ON

Lorenzo, Isaiah and I talked about the above implementation on IRC.

The API behaves similarly to SQL in that rollback() or commit() without any parameters will end the current transaction. This is different from another DBAL that hides automatic nesting from the user. This difference may be counterintuitive.

On the other hand, this API supports automatic nesting by requiring a little more effort from the user. The trade-off seemed acceptable since it makes the API more consistent and flexible.

Transactions¶

/* Basic/single transaction */

// Start transaction
$db->begin();
try
{
    // Save everything
    $db->commit();
}
catch ()
{
    // Abort everything
    $db->rollback();
}

/* Automatic nesting */

// Start transaction or generate savepoint
$token = $db->begin();
try
{
    // Save transaction or release savepoint
    $db->commit($token);
}
catch ()
{
    // Abort transaction or savepoint
    $db->rollback($token);
}

Savepoints¶

/* Savepoints */

// Start transaction
$db->begin();

// Define a savepoint
$db->savepoint('first_part');

// Generate a savepoint
$name = $db->savepoint();

// Abort two savepoints
$db->rollback('first_part');

// Save everything
$db->commit();

/* Savepoints with nesting */

// Start transaction or generate savepoint
$token = $db->begin();
try
{
    // Define a savepoint
    $db->savepoint('anything');

    // Save transaction or release two savepoints
    $db->commit($token);
}
catch ()
{
    // Abort transaction or savepoints
    $db->rollback($token);
}

we were kicking this for more than a year, it's time to make a goal here :P
what is the state of this now? I want to help.