Good deduction Steve.
Looks like we are going to use the timestamp idea. This way, the ticket will
be open for sale again the second it's hold_until time lapses. The cronjob was
a close second, but there could be a lag-time between runs.
Thanks everyone for all the help.
--
Robert Sosinski
On 09/18/2012 08:59 AM, Robert Sosinski wrote:
We have a table, which has items that can be put on hold of 5 minutes
(this is for an online store) once they are placed into a cart. What
we need is for this hold to automatically expire after 5 minutes.
Right now, we put a time stamp into the r
On 09/18/2012 10:03 AM, Szymon Guz wrote:
On 18 September 2012 17:59, Robert Sosinski
mailto:rsosin...@ticketevolution.com>>
wrote:
We have a table, which has items that can be put on hold of 5
minutes (this is for an online store) once they are placed into a
cart. What we need is f
On 18 September 2012 17:59, Robert Sosinski
wrote:
> We have a table, which has items that can be put on hold of 5 minutes
> (this is for an online store) once they are placed into a cart. What we
> need is for this hold to automatically expire after 5 minutes. Right now,
> we put a time stamp
We have a table, which has items that can be put on hold of 5 minutes (this is
for an online store) once they are placed into a cart. What we need is for
this hold to automatically expire after 5 minutes. Right now, we put a time
stamp into the row (called hold_until) at 5 minutes into the fut
