GUI / after_commit
- Source
- Commits
- Network (9)
- Issues (1)
- Downloads (0)
- Wiki (1)
- Graphs
-
Tree:
3c562d7
Xavier Shay (author)
Tue Jun 24 20:01:20 -0700 2008
commit 3c562d72e58dfe88a6806093aec69e8cc9e01fc1
tree f9defea2254fd58e363796b0a9e9c4b55d9a677c
parent 34832ee3359516042d302961c8e9157d0cbec512
tree f9defea2254fd58e363796b0a9e9c4b55d9a677c
parent 34832ee3359516042d302961c8e9157d0cbec512
| name | age | message | |
|---|---|---|---|
| |
.gitignore | Tue Jun 24 20:01:20 -0700 2008 | |
| |
LICENSE | Sat May 31 14:27:26 -0700 2008 | |
| |
README | Wed Jun 11 18:45:45 -0700 2008 | |
| |
Rakefile | Sat May 31 14:27:26 -0700 2008 | |
| |
init.rb | Sat May 31 14:27:26 -0700 2008 | |
| |
lib/ | Tue Jun 24 20:01:20 -0700 2008 | |
| |
test/ | Tue Jun 24 20:01:20 -0700 2008 |
README
after_commit =========== A Ruby on Rails plugin to add after_commit callbacks. The callbacks that are provided can be used to trigger events that run only after the entire transaction is complete. This is beneficial in situations where you are doing asynchronous processing and need committed objects. The following callbacks are provided: * (1) after_commit * (2) after_commit_on_create * (3) after_commit_on_update * (4) after_commit_on_destroy The after_commit callback is run for any object that has just been committed. You can obtain finer callback control by using the additional <tt>after_commit_on_*</tt> callbacks.
