Row count missmatch after updating a row

[surister]

If you insert a new row, refresh and then update, we will have 2 rows in the table instead of one, I suspect this is due to django not being able to detect that the row was correctly updated and therefore inserting a new one, as a 'safe' mechanism to always at least, have the data in the table.

[surister]

We can reproduce this in the unittest, we are aggressively refreshing to make the tests pass.