Transactions

[FabrizioG202]

We are currently exploring the possibility of implementing transactions to enhance the reliability of our database. I'm inclined towards a Write-Ahead Log (WAL) approach and am eagerly seeking your insights and suggestions.

Considerations

Right now, we're not focusing on handling multiple transactions at the same time, so managing concurrency isn't a top priority for us at this point

Proposed Implementation Strategy

1. Logging:
   Every transaction will be recorded in the WAL prior to initiating any alterations in the database. This ensures a chronological record of all transactions, bolstering data integrity.

2. Commit Process
   A transaction will only be marked as committed after its entry is securely logged in the WAL. This step is crucial to maintain a consistent and reliable state within the database.

3. Recovery Mechanism
   In scenarios of system failure, the WAL will serve a dual purpose:

• Redoing Committed Transactions: Transactions that were committed but not yet applied to the database will be redone.
• Undoing Uncommitted Transactions: Transactions that were not committed at the time of failure will be undone.

Request for Collaboration
I'm new to implementing database systems from scratch, so I'd really appreciate any help to ensure we get this implementation right on our first try.

Therefore, I welcome any specific strategies, best practices, or general suggestions you might have. Please feel free to share your thoughts below!