[wp-trac] [WordPress Trac] #44818: cron: preventing duplicate events fails when the first event is too far in the past

[WordPress Trac]

#44818: cron: preventing duplicate events fails when the first event is too far in
the past
-----------------------------+------------------------------
 Reporter:  bodohugobarwich  |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Cron API         |     Version:  2.7
 Severity:  normal           |  Resolution:
 Keywords:  needs-patch      |     Focuses:
-----------------------------+------------------------------

Comment (by bodohugobarwich):

 > For this ticket, I'd rather fix the problem of being able to schedule
 within ten minutes of any identical event (first, last or somewhere in
 between) using either a loop or other appropriate array function. The
 limit has been documented and assumed to be working since version 2.7.
 >
 > @bodohugobarwich are you willing to work on a patch? You can use either
 [https://make.wordpress.org/core/handbook/contribute/git/ Git] or
 [https://make.wordpress.org/core/handbook/contribute/svn/ SVN] to generate
 a patch and upload it to this ticket.

 Yes, I would love to implement this Functionality for WordPress

 Thinking about the issue and seeing that on a production blog in four
 years after its installation the Event Queue has grown up to 10000 queued
 pending events I noticed that the Event Queue is only indexed by the Event
 Time and it lacks a by Hook Index which would greatly improve the
 performance of the search operation.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/44818#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform