下面的方法呢?

客户端:

1. 为插入请求创建 GUID
2. 发送插入请求(值 + 日期 + GUID)
3. 等待回复
4. 收到响应 --> 向用户显示确认信息(已成功完成")
5. 未收到响应 --> 请求插入响应(包括 guid)
6. 收到插入响应 --> 向用户显示确认(已成功完成")
7. 未收到插入响应 --> 重复 5.
8. 响应 ==未插入"--> 向用户显示错误消息(错误，再试一次")

服务器端:

1. 接收插入请求 --> 将数据(值、日期)插入表中
2. 发送确认 --> GUID，好的
3. 或:接收请求(插入 GUID?)--> 发送响应插入的 guid 是/否

I have a table that takes INSERTS to store integers for a date. These integers are then summed for each date with sum(COLUMN) and the total is used. So, date cannot be unique as there are many inserts per date. Integer value itself cannot be unique either.

I use the system to count entries (for instance at a restaurant, club, whatever).

A person holds an iPad at the door and sends an INSERT command for how many people entered (like a group of 5 would be a row with an integer value of 5 and the current date).

If there is a bad connection and the iPad sends the request but doesn't receive an answer, then the user will attempt to perform the insert again, causing duplicates.

Would it be sensible to add a column such as "IDENTIFIER" with a random string/number/hash etc. that would then be unique, so that if the user retries the insert and the server already has the row, it will give the same reply as if the insert succeeded.

I'm having trouble navigating the logic in handling errors such as these. If it were an UPDATE command on a unique column this wouldn't be an issue, but the way I built this that's not really possible.

What about the following approach?

Client side:

1. Create GUID for insert-request
2. Send insert-request (value + date + GUID)
3. Wait for response
4. Response received --> show confirmation to user ("Completed successfully")
5. No response received --> request insert-response (incl. guid)
6. insert-response received --> show confirmation to user ("Completed successfully")
7. No insert-response received --> repeat 5.
8. Response == "not inserted" --> show error message to user ("Error, try again")

Server side:

1. Receive insert-request --> insert data (value, date) into table
2. Send confirmation --> GUID, ok
3. OR: receive request (GUID inserted?) --> send response guid inserted yes/no