> Doesn't this just waste performance creating a duplicate object that's going > to be discarded?
To insert a row, you must first instantiate a model to hold the data for that row. So, either way, you're creating an object, you can't avoid that. The problem is that sometimes you don't care about that object. You need it just to do this one DB operation, like insert. And if you create those objects with `var`, they persist after your operation is done. This code sample demonstrates how you can get the object without introducing throwaway variables. Also, I don't think it has any negative effect on performance. It does allocate memory for the object, but, as I said. there's no way around that.
