Skip to content

ArfaKhalid/Transaction-Data-Management-and-Analysis

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 

Repository files navigation

Transaction Data Management

This repository reflects my exploration of PostgreSQL's transaction management capabilities, focusing on a table called bank_accounts.The steps I follow for this project include creating the table, showcasing atomic transactions, demonstrating rollback scenarios, and delving into various transaction isolation levels.

Table of Contents

  1. Table Creation and Initial Data Insertion
  2. Atomic Transactions
  3. Rolling Back Transactions
  4. Savepoints
  5. Transaction Isolation Levels
  6. Conclusion

1. Table Creation and Initial Data Insertion

I created a new table called bank_accounts, which will store essential information about various bank accounts. Initial data insertion showcases examples with individuals like Charlie, Dora, and Jack.

2. Atomic Transactions

Then explored the concept of atomic transactions, ensuring a sequence of steps is executed atomically. Examples include debiting and crediting amounts to different accounts within a single transaction block.

3. Rolling Back Transactions

Through this project, I Learned how to roll back transactions using the ROLLBACK command using different scenarios where transactions are rolled back, preserving the integrity of the data.

4. Savepoints

Savepoints offer flexibility within a transaction. I demonstrate their use in rolling back to specific points, allowing for more nuanced management of changes.

5. Transaction Isolation Levels

I dived into different transaction isolation levels provided by PostgreSQL and understand their impact on concurrent transactions.

READ COMMITTED

I explored how the READ COMMITTED isolation level allows changes to be visible only after a transaction is committed.

REPEATABLE READ

The REPEATABLE READ isolation level, prevents changes in the same transaction from affecting subsequent reads.

SERIALIZABLE

The SERIALIZABLE isolation level, prevents concurrent transactions from making changes to the same data simultaneously.

6. Conclusion

This project provides hands-on experience with SQL commands and transaction management, offering a solid foundation for working with financial data in a relational database.

Releases

No releases published

Packages

No packages published

Languages