As you’ve likely seen in your feed reader about 50 times already, Rails is turning 2.0. The Preview Release has just been announced, which means that 2.0 final is just a few release candidates away. So much has changed over the last year or so that a lot of the older material on this blog is out of date and needs updating for the reality of 2.0. Seems like now is a good time to get going on the rewriting. I’ll be digging in and bringing stuff up to date over the next few weeks (months? there are quite a few articles after all).
Here’s the list of articles I’m going to be taking a look at. I’m not certain that all need updates, but I think most of them do. If you have a request for something in particular for me to work on sooner, just leave a comment and I’ll take that into account. Of course, I’ll be updating the Many-to-many Dance-off first!
- New association goodness in Rails 1.1
- New association goodness in Rails 1.1, part 2
- The other ways :through
- The other side of polymorphic :through associations
- Why aren’t join models proxy collections?
- Many-to-many Dance-off!
- Self-referential has_many :through associations
- has_many :through gets :uniq
- When associations aren’t enough
- When associations aren’t enough, part 2
- Working with the relationship model
- CRUDdy searches
- How dynamic finders work
- New on edge: Magic join model creation
- Finding unassociated objects
- Basic Rails association cardinality
- Using faux accessors to initialize values