Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The framework I’m starting to learn supports 2 ORMs out of the box. I don’t think it matters for the purposes of this question to say which 2 ORMs. My question is more general than this. How do you in general decide which ORM to go with? I haven’t used an ORM before, but I’m guessing there’s a list of must-haves that any decent ORM must have, then there’s a list of nice-to-have and so on.
An ORM is just like any other software package. You’ll need to compare multiple things, it’s not all about what it can and can’t. Let’s think about:
Your priorities can be different than mine. Do you require a future-proof production-stable product? Or do you want something more cutting edge?