Looks like version 1.0 of ASP.NET MVC is finally released. I’ve had a tiny play with some of the previews, but I really want to spend a bit of time getting up to speed with this. On a completely unrelated note, I’ve managed to injure my back today. I was riding to work and all of a sudden it felt like my lower back had a big spasm. I started to walk back home and quickly realised that I wasn’t going to get very far. Happily my Dad was able to come over and pick me up. He’s had personal experience himself of doing his back very badly, so was quite concerned – plus it happened that it was his bike I was riding ([mine not having survived the trip home]/2009/01/tour-down-under-2009.html) from this year’s tour). I’m a reasonably tall fellow and I wonder if the fact that Dad’s bike is a bit smaller might have been a contributing factor. So a rapidly-booked appointment with the Chiro and some Nurofen Plus leaves me a little more mobile now that I was earlier today, but it sounds all going well the pain will be there for a little while longer, and cycling and basketball might have to take a break for a bit. I had also been hoping to still get over to Wagga for CodeCampOz but sitting in a car all day doesn’t really sound that comfortable right now either.
System.Data.SqlClient.SqlException: A severe error occurred on the current command. The results, if any, should be discarded.
That’s not a very helpful error message!
Googling doesn’t throw up much except for KB article 961283. However after installing Cumulative Update 3 the problem remained, so that wasn’t it.
Narrowing down the problem highlighted a stored procedure using a CURSOR while talking to a linked server.
Re-writing the stored procedure without a cursor gave back a more descriptive error (trying to set a non-nullable column to null!). Now it was easy to fix.
Thanks to Timothy, SQL guru :-) I’ll let him describe how he writes T-SQL that avoids cursors.