Here is a test to confirm. The table ends up as:

apple
potato
orange

"pomegranate" is missing, because it has been rolled back, but potato is included, because release_savepoint() actually has the effect of "forgetting" that savepoint, but NOT rolling back the work.

$db->begin_transaction();
$db->query('INSERT INTO utility_belt SET item="apple"');
$db->savepoint('vegetables');
$db->query('INSERT INTO utility_belt SET item="potato"');
$db->release_savepoint('vegetables');
$db->savepoint('nope');
$db->query('INSERT INTO utility_belt SET item="pomegranate"');
$db->query('ROLLBACK TO nope'); // No rollback to savepoint function..?
$db->query('INSERT INTO utility_belt SET item="orange"');
$db->commit();

It's interesting too that there appears to be no function to ACTUALLY rollback to a given savepoint.

I have submitted a respective patch via PHDOE.

> It's interesting too that there appears to be no function to
> ACTUALLY rollback to a given savepoint.

Feel free to file a respective feature request. :)

This has already been fixed[1] quite a while ago!

[1] <https://github.com/php/doc-en/commit/3a488bc675db0eef92c52122486574c58ca8c417>