This repository is private.
All pages are served over SSL and all pushing and pulling is done over SSH.
No one may fork, clone, or view it unless they are added as a member.
Every repository with this icon (
) is private.
Every repository with this icon (
This repository is public.
Anyone may fork, clone, or view it.
Every repository with this icon (
) is public.
Every repository with this icon (
commit 603a71b877355d9cb5a74fc11fca887fdd15602b
tree 104d4f259ae76a93531ecf81cbc4b542e5c315d1
parent 64f4082bb3b72cc0ccfc4e61e3fa9bbb7f9d67c1
tree 104d4f259ae76a93531ecf81cbc4b542e5c315d1
parent 64f4082bb3b72cc0ccfc4e61e3fa9bbb7f9d67c1
| name | age | message | |
|---|---|---|---|
| |
.gitignore | Mon May 04 13:23:22 -0700 2009 | |
| |
README | Mon May 04 13:31:54 -0700 2009 | |
| |
Rakefile | Mon May 04 13:23:22 -0700 2009 | |
| |
app/ | Mon May 04 13:31:54 -0700 2009 | |
| |
config/ | Tue May 12 12:40:46 -0700 2009 | |
| |
db/ | Mon May 04 13:23:22 -0700 2009 | |
| |
doc/ | Mon May 04 13:23:22 -0700 2009 | |
| |
public/ | Mon May 04 13:23:22 -0700 2009 | |
| |
script/ | Mon May 04 13:23:22 -0700 2009 | |
| |
test/ | Mon May 04 13:23:22 -0700 2009 |
README
== acts_as_revisable Demo #1: Handling Associations A simple blog post can cover the simple common case of AAR usage. In this series of repos I thought I'd cover some more advanced usage. In this case I'm showing how you could handle associations and revise them along with another model. In this project I'm demonstrating a very simple structure. Basically with have Posts which can have many Links. Any time a post is revised, it's current links should be stored with that revision. Also, we're going to count adding a link as a revision to a post. All the code is in app/models/*







