Browse files

after_(commit|rollback) rdoc, edit pass

  • Loading branch information...
1 parent f5fa13c commit 1ff954aaea764c16e812dadea44a07a3f4119905 @fxn fxn committed Apr 30, 2010
Showing with 5 additions and 5 deletions.
  1. +5 −5 activerecord/lib/active_record/transactions.rb
View
10 activerecord/lib/active_record/transactions.rb
@@ -163,24 +163,24 @@ class TransactionError < ActiveRecordError # :nodoc:
# === Callbacks
#
# There are two types of callbacks associated with committing and rolling back transactions:
- # after_commit and after_rollback.
+ # +after_commit+ and +after_rollback+.
#
- # The after_commit callbacks are called on every record saved or destroyed within a
- # transaction immediately after the transaction is committed. The after_rollback callbacks
+ # +after_commit+ callbacks are called on every record saved or destroyed within a
+ # transaction immediately after the transaction is committed. +after_rollback+ callbacks
# are called on every record saved or destroyed within a transaction immediately after the
# transaction or savepoint is rolled back.
#
# These callbacks are useful for interacting with other systems since you will be guaranteed
# that the callback is only executed when the database is in a permanent state. For example,
- # after_commit is a good spot to put in a hook to clearing a cache since clearing it from
+ # +after_commit+ is a good spot to put in a hook to clearing a cache since clearing it from
# within a transaction could trigger the cache to be regenerated before the database is updated.
#
# === Caveats
#
# If you're on MySQL, then do not use DDL operations in nested transactions
# blocks that are emulated with savepoints. That is, do not execute statements
# like 'CREATE TABLE' inside such blocks. This is because MySQL automatically
- # releases all savepoints upon executing a DDL operation. When #transaction
+ # releases all savepoints upon executing a DDL operation. When +transaction+
# is finished and tries to release the savepoint it created earlier, a
# database error will occur because the savepoint has already been
# automatically released. The following example demonstrates the problem:

0 comments on commit 1ff954a

Please sign in to comment.