Daevid Vincent wrote:
> I don't "get it"... I mean, I get the concept -- it's a crontab; but why
> would someone opt to put these events here instead of in the God-given
> CRONTAB as everything else in the system uses? This just seems like one
> more place to forget about a query/code and have "unexpected" things
"There's more than one way to do it."
(Perl slogan, I didn't look up the author)
> We already have a plethora of 'cron-like' tools:
> * [[...]]
Agreed - but this is Unix/Linux only (not Windows), and this multitude
doesn't make things easier for people working on several systems.
IMNSHO, the question is whether you are viewing some to-be-scheduled
task an aspect of the system as a whole or rather as a database aspect.
In the first case, use your system scheduler, like cron; in the latter
case, it makes sense to handle it internal to the database.
The advantage of scheduling database tasks in the database is that this
allows database backups and migrations to include it. If you handle that
scheduling via cron (or some other scheduler), you need to handle it as
a separate thing in backups and migrations.
In addition, Dan's points are of course valid ones.
> Unless I'm missing some killer functionality this provides (and from that
> URL, I'm not seeing any), then I wish the Sun/mySQL team would have spent
> their precious time on more pressing features and or bug-fixes [[...]]
My answer above is to explain why this is seen useful by several people,
not to claim any relative priority of this and other changes.
Joerg Bruehe, MySQL Build Team, Joerg.Bruehe@stripped
Sun Microsystems GmbH, Komturstraße 18a, D-12099 Berlin
Geschaeftsfuehrer: Thomas Schroeder, Wolfgang Engels
Vorsitzender des Aufsichtsrates: Martin Haering Muenchen: HRB161028