+972 52-548-6969
A bug that drove me crazy!
time to read 1 min | 98 words
I am ashamed to say how much time and effort (and at least one complete re-design) this bug has cost me.
Take a look at the following test, meant to show that Raven can replicate deletes between servers:
There is a very subtle bug in this code, which completely tripped me.
Here is a hint, the session interface is the high level client API for Raven.
Can you spot the bug?
Comments
A session-level cache doesn't know that underlying data was deleted after it has been read for the first time?
If loaded once successfully, the non-null object is cached by the session.
if (company == null) is the bug
if (company != null) is the correct thing you want to do.
Those thing are can drive one crazy
My guess would be along the lines of Rafal..
I don't know RavenDB but I'd guess there'd be a parameter available on Load() to ensure a clean hit to the document source. (I.e. NoCache)
Caching is the answer from my glance
But that's only because you hinted about it being about the session, I'd not have seen that - and I'm fairly sure I've done similar in NH before by accident!
Yeah, I was thinking cache too.
I'd like to jump in and say that it appears your test is missing a pre-condition.
I think you should ensure "companies/1" exists in store1 and store2 before you delete it from store1, and poll store2 until timeout or it no longer exists.
I'm not aware of the specific syntax for RavenDB [yet] but I am surprised that there is no query you can use to see if "companies/1" exists other than to load the company.
I assume RavenDB will return null if the requested document is not found?
Damn, my answer came to fast, truly newbie...
If there is a Flushmode enumeration in the Raven Client API (similar to NHibernate) my answer would be that Flushmode is set to Never on the sessions you get back from your session factory.
I think the session should be opened inside the for loop.
+1 for Mistertom, Steve Py and Markus Zywitza. ;-)
What about transactions?
I know that NHibernate session does not sync its content with the DB unless you either commit the transaction or call its Flush method. I do not know if a RavenDB session acts in a similar way, but if it does, I see no transaction commit or flush, so your company was not deleted yet ...
Two variations on what others said: if the session is like NH's, Load might never return null OR it might never go to the database twice for the same ID in the same session, so the session should be opened INSIDE the loop.
Comment preview