I have a strange thing that is happening where I am getting duplicate key errors occasionally - most of the time it is in a database session call, but occasionally it is elsewhere. I am guessing this is because I have some pages with rapid ajax calls. I also have a query pair that updates like:

\App\model::were('user_id',$user_id)->delete();
\App\model::insert([
  [
    'user_id'=>$user_id,
    'value'=>1,
  ]...
]);

where there is a unique contstraint between user_id and value - but every so often I get a duplicate key error on this, again probably a race condition maybe brought on by the database taking longer to perform the insert, I'm guessing I have two threads that are:

Thread1:delete Thread2:delete Thread1:insert Thread2:insert - error, key already exists

Normally I would use replace instead of insert (I'm doing the delete/insert to try to mimic the replace functionality). I don't want to use raw queries because the list of inserts can be fairly long.

In both of these cases, is there a best practices solution that I'm not thinking of?