Re:ORMs don’t kill databases. Developers do.
by trebor on Tuesday August 30, 2011 @01:17PM
(#2942311)
http://api.rubyonrails.org/classes/ActiveRecord/ConnectionAd...
I did this and indexed the table by date, and it works for everything except saving a record. Like I said, an ID/primary key is required though that section of the documentation implies that an ID is optional.
[ Parent
| on HN ]
Re:ORMs don’t kill databases. Developers do.
by rahoulb on Tuesday August 30, 2011 @03:45PM
(#2942951)
Hmm - yeah the docs are sort of unclear, if you're not familiar with the convention.
:categories_suppliers implies that the table is a join table (a many-to-many join between categories and suppliers) - which is why it has no ID and why it only has the two foreign key fields with no other data.
Re:ORMs don’t kill databases. Developers do.
by trebor on Tuesday August 30, 2011 @06:41PM
(#2943539)
Yet the assumption that all models require an ID is a fallacy. I was generating reports unique to the day, therefore a simple Date field was adequate as an index/ID. I don't know about other ORMs but when working directly with the SQL it'd be no issue.
I hold out that it's a problem in the design of ActiveRecord to assume that there will always be a primary key. That said, if I can just tell the model "identify yourself by this key" WITHOUT setting it as the primary key I would be happy.