I’m thinking about learning ORM stuff but I think about one thing. If I have a table (or some joined tables) with millions of records, is it good to have mapped objects with millions of items? Is it safe to handle so big objects?
Thanks!
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.
I’m thinking about learning ORM stuff but I think about one thing. If I have a table (or some joined tables) with millions of records, is it good to have mapped objects with millions of items? Is it safe to handle so big objects?
Thanks!
It really depends on what you will be doing with these objects; having a large number of them isn’t by itself a reason to use ORM or not.
It might be more important to handle records in an object-oriented fashion so that business logic can be reliably performed on them. Or conversely, if performance is a bigger issue then keeping things lighter might be preferable. ORM is just a tool with its pros and cons; you need to decide if the benefits of using that tool outweigh the disadvantages.