You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2018. It is now read-only.
I remember switching from AR because of certain pain points, things solved by DM.
Properties in the model (so you don't have to keep checking the schema in the DB)
Better associations (through many, more than 1 step away)
Composite primary keys
Please comment with your pain points solved by DM.
The text was updated successfully, but these errors were encountered:
I like how DM uses the strengths of the DB rather than just viewing it as a dumb storage container. I mean, if server side constraints aren't being used, then there are alot faster/simpler ways to store objects in a datastore than an RDBMS. The strength of an RDBMS is that it does maintain consistency of the data it accepts, so that you can be sure that it represents true facts within it -- that you can trust the data it contains.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I remember switching from AR because of certain pain points, things solved by DM.
Properties in the model (so you don't have to keep checking the schema in the DB)
Better associations (through many, more than 1 step away)
Composite primary keys
Please comment with your pain points solved by DM.
The text was updated successfully, but these errors were encountered: