Bug Fix: WilsonORMapper v3.1.0.1

I inadvertently broke most custom providers in my WilsonORMapper v3.1 -- this is fixed in v3.1.0.1.  Those that were manually adding their own parameter names in their mapping files were not affected, which was also why I didn't notice this in my testing.  Of course the recent change in the MySql provider did not help make this any easier to spot.  Thanks to David Dimmer for helping me track down the bug in my code -- and just when I was bragging about stability.

4 Comments

  • As long as we're on the subject of bugs, I've dealt with one since Transactions were added.



    "Message: This SqlTransaction has completed; it is no longer usable.

    Source: System.Data

    Stack Trace: at System.Data.SqlClient.SqlTransaction.Rollback()

    at Wilson.ORMapper.Transaction.Rollback()

    at Wilson.ORMapper.ObjectSpace.PersistChanges(ICollection entityObjects, PersistDepth persistDepth)

    at Wilson.ORMapper.ObjectSpace.PersistChanges(Object entityObject)"



    It actually seems to be out of scope, and since I'm try/catching the service using it, and reinstantiating it every 60 seconds it's never been a showstopper for me, but it is annoying to get 10 emails in the morning from my exception logger. :)



    I tried to look at the code a bit when I first started getting this (after upgrading to v3 I think), but didn't understand the intent of the deconstructor for Transaction, so I gave up after a couple minutes.



    Anyways, still a great mapper, it's certainly made my job easier, really looking forward to V4! :)

  • Hey Sam:



    I still have not been able to reproduce this, and I didn't realize it was something you saw that frequently either. I'd love to get some code that I could reproduce it -- one other person mentioned getting this also, but that's all.



    Thanks, Paul Wilson

  • I'll shoot you an email tomarrow if you'd like. Like I said, it's in a Windows Service that cycles every 60 seconds though, and I might get from 2 to 10 emails a day (though always atleast 2). So say 5 out of 1440 cycles throw this exception. And like I said, I haven't noticed it actually affecting the work (though I wouldn't notice if the work was still done on the next cycle).



    I haven't reported it before I don't think, so no one should take this as major. You can't fix what you're not aware of after all. :)



    Again, great product, the $50 has paid for itself many times over in what you've taught me. :)

  • Again, great product, the $50 has paid for itself many times over in what you've taught me.



    Amen to that!

Comments have been disabled for this content.