Have you had experience using nested transactions when working with databases?

Nested transactions are the ability to start another transaction within a single transaction, which can be committed or rolled back independently. Most DBMSs do not support nested transactions directly, but savepoints can be used.

In Go, when working with databases through the database/sql package, savepoints can be used to simulate nested transactions:

// Start the main transaction
tx, err := db.Begin()
if err != nil {
    // handle error
}

// Create a savepoint
_, err = tx.Exec("SAVEPOINT sp1")
if err != nil {
    // handle error
}

// Perform operations
// ...

// In case of an error, rollback to the savepoint
_, err = tx.Exec("ROLLBACK TO SAVEPOINT sp1")

// Commit the main transaction at the end
err = tx.Commit()

Thus, you can control parts of the transaction without canceling the entire operation.