Postico guides9/17/2023 ![]() ![]() Transactions can be started using BEGIN TRANSACTION or simply BEGIN command. They cannot be used while creating tables or dropping them because these operations are automatically committed in the database. Transactional control commands are only used with the DML commands INSERT, UPDATE and DELETE only. ![]() The following commands are used to control transactions −īEGIN TRANSACTION − To start a transaction.ĬOMMIT − To save the changes, alternatively you can use END TRANSACTION command. Isolation − Enables transactions to operate independently of and transparent to each other.ĭurability − Ensures that the result or effect of a committed transaction persists in case of a system failure. Transactions have the following four standard properties, usually referred to by the acronym ACID −Ītomicity − Ensures that all operations within the work unit are completed successfully otherwise, the transaction is aborted at the point of failure and previous operations are rolled back to their former state.Ĭonsistency − Ensures that the database properly changes states upon a successfully committed transaction. Practically, you will club many PostgreSQL queries into a group and you will execute all of them together as a part of a transaction. It is important to control transactions to ensure data integrity and to handle database errors. For example, if you are creating a record, updating a record, or deleting a record from the table, then you are performing transaction on the table. Transactions are units or sequences of work accomplished in a logical order, whether in a manual fashion by a user or automatically by some sort of a database program.Ī transaction is the propagation of one or more changes to the database. A transaction is a unit of work that is performed against a database. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |