What is transaction management in object oriented database design? Please suggest some sites where I will get detailed information along with implementation approach.
Transaction management is the ability to group changes to the database so that those changes are atomic. This means that either all of the changes in a group happen, or none of them happen. In most SQL dialects this is done using the BEGIN TRANSACTION to mark the beginning of a transaction, then either COMMIT TRANSACTION to keep all of the changes or ROLLBACK TRANSACTION to discard all of the changes.
Different SQL dialects don't always handle transactions quite the same. This is especially true when one transaction occurs inside of another transaction. Be sure to check the documentation of the dialect you are using if you have questions about the details of how transactions are handled.
Because transaction management is such a fundamental concept, it is usually covered in books rather than web sites. The idea of transactions isn't really subject to debate, it is generally accepted that transactions are required for a database engine, so the subject doesn't get much coverage on Web sites because there isn't really anything to discuss.
You'll find more coverage in discussion groups such as here at SearchDatabase, or in vendor specific forums that can be either on various Web sites or on Usenet.
For More Information
- What do you think about this answer? E-mail the editors at editor@searchDatabase.com with your feedback.
- The Best Database Design Web Links: tips, tutorials, scripts, and more.
- Have an Oracle or SQL tip to offer your fellow DBAs and developers? The best tips submitted will receive a cool prize. Submit your tip today!
- Ask your database design -- or help out your peers by answering them -- in our live discussion forums.
- Ask the Experts yourself: Our SQL, database design, Oracle, SQL Server, DB2, metadata, object-oriented and data warehousing gurus are waiting to answer your toughest questions.