P
Look at the web server logs, you'll probably see duplicate requests.To cure a mistake, you can steer (create a lux file with an equal client's ip address, allow) importation at the start of a crypt for each ip address, remove the file at the end of the crypt. If the file with such ip exists, do nothing.That is, at any time, only one import process will be possible from the 1st Api.You can refine the violin differently.You keep somewhere. md5(file_get_contents("old_csv_file"))compare md5(file_get_contents("new_csv_file"))if they're equal, you don't do anything.Then go to programmer 1s and knock on the head if he somehow sends double requests.And, yes, check your code just in case you don't leave a double data box in the bud for research purposes yourself.P. S.
In any case, the addition of duplicate data would be a good tone. It's better not even do it at the php-scrypt level, but do it at the OBD level.If your playlist has, let's say, an artics, make it a unique key to the OBD, and if the duplicate data are available, just activate current values.The best is to carry out md5 checks and checks in bd, and suddenly 1c begins to send practicers, which contain both duplicates and unique values, but in general, the data differ from the previous front page.Your job as a software player is to provide as many bad data solutions as possible, or not to download bad data at all, so the guys on that side don't relax. That ultimately depends on your business assignments.
