kotovalexarian-likes-github
/
paper-trail-gem--paper_trail
mirror of https://github.com/paper-trail-gem/paper_trail.git
1
0
Fork 0
Code Releases Activity

Docs: Modern AR find coerces to int if necessary 

From the AR docs:

> If the primary key is an integer, find .. coerces its arguments using to_i.
> http://bit.ly/1NltoaC

So, our advice to use to_i manually is no longer necessary.

[ci skip]
This commit is contained in:
Jared Beck 2015-06-26 23:16:21 -04:00
parent 30a9d18052
commit fc9244dea2
1 changed files with 6 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
README.md
View File

@ -475,14 +475,13 @@ And you can perform `WHERE` queries for object versions based on attributes:
## Finding Out Who Was Responsible For A Change
If your `ApplicationController` has a `current_user` method, PaperTrail will attempt to store the value returned by `current_user.id` in the version's `whodunnit` column (if it returns). Note that this column is of type `String`, so you will have to convert it to an integer if it's an id and you want to look up the user later on:
If your `ApplicationController` has a `current_user` method, PaperTrail will
attempt to store the value returned by `current_user.id` in the version's
`whodunnit` column.
```ruby
>> last_change = widget.versions.last
>> user_who_made_the_change = User.find last_change.whodunnit.to_i
```
You may want PaperTrail to call a different method to find out who is responsible. To do so, override the `user_for_paper_trail` method in your controller like this:
You may want PaperTrail to call a different method to find out who is
responsible. To do so, override the `user_for_paper_trail` method in your
controller like this:
```ruby
class ApplicationController
@ -694,7 +693,6 @@ end
3. PaperTrail only reifies the first level of associations, i.e., it does not reify any associations of its associations, and so on.
4. PaperTrail relies on the callbacks on the association model (and the :through association model for Has-Many-Through associations) to record the versions and the relationship between the versions. If the association is changed without invoking the callbacks, Reification won't work. Below are some examples:
Given these models:
```ruby
@ -756,7 +754,6 @@ end
See [issue 113](https://github.com/airblade/paper_trail/issues/113) for a discussion about this.
## Storing metadata
You can store arbitrary model-level metadata alongside each version like this: