4 ms·
I don't know why you're being downvoted. Even when you're using an oo language, there's not always a reason to force your query results into an "Object." Freq
by nissimk 13y ago
I don't know why you're being downvoted. Even when you're using an oo language, there's not always a reason to force your query results into an "Object." Frequently the only object you need is a 2 dimensional data structure which could be a list of dictionaries, or a DataTable or something like that. You don't always need a special named structure for the results of every query. ORM's always seem to be designed for people who have a one to one mapping between data structures in their program and tables in their DB. I find that this very rarely makes sense, particularly when you're talking about analytical applications.
- nsxwolf 13y agoGreat, you have a list of dictionaries of dictionaries. Now the user has updated some of the items inside one of the nested dictionaries. The user clicks save. Now what? You've got to get that change to the data in the dictionary inserted into the correct place in the relational database. You're going to write code to do by hand what an ORM wants to do for you.