Searched refs:CONFLICT (Results 1 – 13 of 13) sorted by relevance
74 case CONFLICT: in AttemptOneApplication()125 update_progress->AddAppliedUpdate(CONFLICT, *i); in SaveProgressIntoSessionState()
258 return CONFLICT; in AttemptToUpdateEntry()270 return CONFLICT; in AttemptToUpdateEntry()276 return CONFLICT; in AttemptToUpdateEntry()286 return CONFLICT; in AttemptToUpdateEntry()321 return CONFLICT; in AttemptToUpdateEntry()339 return CONFLICT; in AttemptToUpdateEntry()345 return CONFLICT; in AttemptToUpdateEntry()
35 CONFLICT, enumerator
151 case CommitResponse::CONFLICT: in ProcessCommitResponse()240 if (CommitResponse::CONFLICT == response) { in ProcessSingleCommitResponse()
88 status_.summary = sync_api::SyncManager::Status::CONFLICT; in CalcStatusChanges()
674 CONFLICT, enumerator
160 status.mutable_update_progress()->AddAppliedUpdate(CONFLICT, in TEST_F()
338 if (it->first == CONFLICT) { in HasConflictingUpdates()
792 reply.response_type = sync_pb2.CommitResponse.CONFLICT
94 // a result code of CONFLICT. In a GetUpdatesResponse, |version| is418 CONFLICT = 2; // You're out of date; update and check your data enumerator
11580 4DC5;HEXAGRAM FOR CONFLICT;So;0;ON;;;;;N;;;;;
34619 …how SQLite handles the "ON CONFLICT REPLACE" condition, which is to delete the row and re-insert i…
22496 CONFLICT K AA1 N F L IH0 K T22497 CONFLICT(2) K AH0 N F L IH1 K T