I don't think rails supports primary keys across multiple columns,
though work may be being done on this. Currently though, many methods
(such as find(id)) assume a single-column primary key. I'm not sure
the best way to resolve this. I'd probably look to getting it working
without multiple column PKs, then building on that.
This need was strictly for Migrations not for model objects. We currently have our link tables have the ID's for each table it's linking defined as a multiple column primary key.
Also, its worth considering how to get the PK from a table definition.
I think the PK belongs to the table, rather than just being a
property of a column.
I definitely agree that having a primary key at the table definition level would be good.
In production mode this won't be an issue as the columns information
is only loaded once.
Ok, I assumed this was the case but I wanted to bring it up just to make sure.
_______________________________________________ Rails-core mailing list [email protected] http://lists.rubyonrails.org/mailman/listinfo/rails-core
