Linked by Thom Holwerda on Fri 7th Dec 2007 19:44 UTC, submitted by Bill Davenport
General Development Ruby on Rails 2.0 has been released. "Rails 2.0 is finally finished after about a year in the making. This is a fantastic release that's absolutely stuffed with great new features, loads of fixes, and an incredible amount of polish. We've even taken a fair bit of cruft out to make the whole package more coherent and lean." On Zenbits, they give tips on how to install 2.0.
Thread beginning with comment 289456
To view parent comment, click here.
To read all comments associated with this story, please click here.
FooBarWidget
Member since:
2005-11-11

It still doesn't.

But why do you need compound primary keys? What are its advantages over using a number? I've never felt the need to use compound primary keys.

Reply Parent Bookmark Score: 4

borker Member since:
2006-04-04

I've always felt slightly off about creating an arbitrary unique value unrelated to the actual context of the data when there is already available a way of uniquely identifying rows that only uses actual system data.

Also, by default most DBs create an index on the primary key, which is a bit meaningless with a created single key when most/all data access will still be by what would otherwise be the compound primary key. Just means you have to create an additional index, i realize, but there ya go.

So no real technical show stoppers, just a couple of things that kinda run against the grain for me anyway...

Reply Parent Bookmark Score: 4