Roster is updated with setData method which calls removeData, addData methods. It may happen that the first query is successful whereas the second fails. This may lead to data loss in database. In particularly this has happened for the roster once.

Therefore, it seems like a better way to handle it would be calling 'update' on the data and catch an exception if data does not exist to insert (addData).