> I know that supporting composite keys is not a MUST, but it's a SHOULD.
Your invoice lines will have an invoice_id relating them to the invoice, it doesn't get much more related than that. If you're seeing the ids as anything other than serialised object-identity, then you're over using. The very very very good reason not to support composite keys is that it doesn't give any tangible benefits over single, unique IDs. Even less so with an ORM like AR. If you want, you can add your own unique constraints. > I understand ActiveRecord doesn't support it now in favor of > simpleness, but aventually it should have that option. It won't, for the same reasons we don't support all the other DBA centric options. The costs outweight the benefits. If you want to work this way, the soon-to-be-real rbatis persistence is your best option. -- Cheers Koz _______________________________________________ Rails-core mailing list Rails-core@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-core
