It depends.
Let me explain.
For example, there is a table with dates and pay info like in your app. And users have to fill it and sometimes they need to change the data entered by a mistake or something. From the first sight you may think it will be great to give user an ability to edit the data inplace, but...
There is another kind of users of your system, people who sit at the other side of it: managers or whatever. And these people should process that data. And everything is OK until a moment somebody want to modify the old data.
So, here is the problem: the data goes the way that managers could pick it one by one from the top of the queue. And what happens with the modified data? Should it pop up at the top (and change it's order or return back later, etc) or just be highlighted somehow (so, how managers fill catch this and proceed), etc?
The one solution will be to not let users to edit the data, but let them remove it and then place a new row which will pop up at the managers side (so, the queue will be the same, etc).
I mean, this is a kind of imagined scenario so don't take it seriously, it's justan illustration, but I know there are a lot of systems which will not allow you to demonstrate that often it'sedit your data but to remove and add instead (twitter). And that's just a trade-offs we have to do to keep our systems useful and usable byuseful, usable and simple to all kinds of users. So, answering your question, I think that actually it dependsit depends.
In your case I believe you may let your users to edit dates inplace by showing a datepicker right near the cell, etc.