Multiple execution of the same job against same data
From: <taguato1_at_gmail.com>
Date: Sun, 11 Oct 2015 06:34:55 -0700 (PDT)
Message-ID: <60510609-eb6b-4ea4-a8fc-b0bdcd72f925_at_googlegroups.com>
Hi folks: What if there are so many 'P' records that the update process doesn't end within the 5 minutes and CRON fires up another instance of the update process? Will that screw up the database?
Date: Sun, 11 Oct 2015 06:34:55 -0700 (PDT)
Message-ID: <60510609-eb6b-4ea4-a8fc-b0bdcd72f925_at_googlegroups.com>
Hi folks:
Environment: linux, php and mysql.
I have a process that I am planning to execute automatically with a CRON, every 5 minutes. This process updates all records with status 'P' to 'E', based on certain criteria. That far everything good and simple.
But here is the kicker: On the front end, users are constantly adding new 'P' records to the table, so it could happen that before the update process ends, there may be new 'P' records added.
The questions are:
- Will the update process update those as well, or they will be left 'P' until the next execution?
Regards,
Lou Received on Sun Oct 11 2015 - 15:34:55 CEST