How should you properly implement database transactions in sqflite to ensure several genuinely related separate operations either all fully succeed together, or all genuinely fail together entirely, maintaining your overall data's own genuine consistency?

A database transaction properly groups several genuinely separate related operations together as one single atomic unit, meaning either every single one of those operations genuinely succeeds together, or if any single one of them genuinely fails partway through, every single other operation within that exact same transaction is automatically and properly rolled back entirely, ensuring your data never ends up left in a genuinely inconsistent, partially completed state, which is particularly important for a scenario such as processing an order that genuinely requires both deducting inventory stock and properly recording that specific transaction together, where you genuinely never want just one of those two particular related operations to succeed while the other one unexpectedly fails.

await db.transaction((txn) async {
  await txn.update('inventory', {'stock': newStock}, where: 'id = ?', whereArgs: [productId]);
  await txn.insert('transactions', {'productId': productId, 'quantity': quantity});
});