Has anyone really wanted and used inheritance support on ORM tools, and if yes which one do you think offers the best support?
Or is ORM Inheritance a ‘pie in the sky’ concept?
Share
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.
Has anyone really wanted and used inheritance support on ORM tools, and if yes which one do you think offers the best support?
Or is ORM Inheritance a ‘pie in the sky’ concept?
I like this question a lot. I’ve used ORM tools (Toplink, now eclipselink, Hibernate) for a while and I’ve always seen this as referenced in JPA documents but I’ve never really had a need for it. Basically my philosophy is the ORM is just there to prevent you from writing tedius code to pull out records for the database. That really is the huge timesaver and it prevents you from making stupid mistakes. Sure you can do fancy stuff with this, but why not save it for the controller (if you’re following MVC) than stick it in the model?