… not sure myself, but certainly it is a sneaky creature.
I will not talk about all ORMs (as if I could ) since I want to exemplify on what gave me grief.
I was using Linq2SQL to perform some “simple” queries in an application.
I wish not to discuss:
- whether Linq2SQL is an ORM at all. For me it is and we might discuss its shortcomings and debate o semantics.
- why I am using a “walking zombie” of a technology. For me, i is not an “un-dad”. Linq2Sql does the job I am asking it to do efficiently enough (or so I thought) and the bits are not going to vanish all of a sudden from the framework.
My intention is neither debating nor ranting (I do that more than anything apparently), but leaving the grumpy-not-so-old man in me behind and offer the reader some knowledge (for a change).
Let’s say we have a very simple model:
There is a Subject class that has a Parent relationship and multiple children: Child and OtherChild. Fairly simple if you ask me.
As usual, all code will be provided in
Google CodeGithub. Since we are dealing with databases you will have to have a SQL Server database named SneakyORMs with the schema specified in SneakyORMs.sql.
For query execution and analysis I am going to use the must-have tool if you are dealing with LINQ (in any of its flavors): LinqPad. If you do not know the tool, go ahead and download it, it is free but you can activate Intellisense for a very reasonable amount of money.
First things first, let’s insert some data in the system, executing initData.linq after the connection to the newly created database has been set up and verifying that there is indeed some data AllEntities.sql.
A Soup of Queries
Alright then, we have all nuts and bolts in place. Let’s do something interesting. Let’s query the Parent_Subject relationship with the query Parent_Subject.linq:
This query displays all Parents and Subjects, but also displays a given Parent and a given Subject. How many queries do you think are going to be executed? Stop guessing and start asking LinqPad:
Only one. Thinking about it, it makes sense as we already got all the information required in out first query and Linq2Sql offers some “identity map” capabilities in the DataContext, So it is clever enough to figure out that both the Parent and the Subject have been retrieved before, and it does not go to the database again.
Let’s move on and place out attention in Subject, by querying the Subject_Children relationship. Let’s execute the Subject_Children.sql:
As before, we have 3 LINQ queries and in the first one we retrieve all the information. Anyone dares to take a guess on how many queries are actually issued? Those of you who thought “one” could not be more wrong (I was one of you, if that gives you any relief, not that it should, though…). Those of you who thought “not one, you are trying to trick us” are closer, but it is a pretty lame thought, mind you. I would only give credit to those who thought “two” and are able to explain it to me because it is beyond my comprehension. Not kidding, leave a comment explaining it to me and we will see what I can do in terms of “credit”. LinqPad says:
Doh! After all Linq2Sql is not clever enough to figure out that the Child with id 131 was already part of the result-set was fetched before.
Let’s dig a bit deeper and focus on only one Subject and its Parent SingleSubject_Parent.linq:
Uhm, two queries? Makes some sense, since we are asking for something we had not fetched before (the Parent). Therefore it has to go to the database and fetch it in another round-trip.
Couldn’t we disable this lazy behaviour and instruct Linq2Sql to eager fetch more information? Yes we could, let’s try playing with the LoadOptions property of the DataContext in order to retrieve a Subject and its Parent in one go:
A small victory here. One single query suffices to get both Subject and Parent.
But we are also interested in the Subject_Children relationship, would the behaviour be the same?
What? Three queries!?! Linq2Sql is simply not clever enough to figure out that the Child with id 231 was fetched before. Would eager loading solve this mess?
Hardly. We moved from three down to two, as we are eager loading the children, but still the identity map is not able to figure out that 131 was already fetched before. Is it terrible? Not, but it could do better.
What we have seen? We have seen that Linq2Sql exhibits an unexpected behaviour (at least for me) in regards to relationships and the necessity to go to the database multiple times to satisfy the demand of data. It was successfully using its identity map powers to save queries when querying the Parent_Subject relationship but failing to do so when querying the Subject_Children or the Subject_OtherChildren. Cause? Unknown. Diagnosis? Twiddle fingers and look upwards.
ORMs are wonderful tools. And as such they can’t be handled recklessly. Their sheer existence does not make them evil or golden.
For myself? They have become a very-nice-to-have weapon in my arsenal. Most of the time they save me a lot of work (and money to my customers) but other times they are just another piece of the puzzle that need to be understood.
Piece of advice: do not forget your SQL skills. They come very, very handy. You may just switch from looking at the execution plan in SQL Server Management Studio to looking at the SQL generated by my LINQ queries.
But remain vigilant… Rogue queries and N+1 are everywhere