LWN: Comments on "New Event Feature in MySQL 5.1.6"

New Event Feature in MySQL 5.1.6

nix — Thu, 26 Jan 2006 20:04:27 +0000

And of course having gone back, changes should lead to the creation of a branch! w00t!

(er, OK, perhaps not... although I *have* designed a database-backed filesystem sitting atop FUSE which works like this. Now all I have to do is *implement* the damn thing.)

New Event Feature in MySQL 5.1.6

pimlott — Thu, 26 Jan 2006 01:18:54 +0000

While jwb's post was riotous, the ability to run a query "in the past" would be terribly useful. Imagine you find out today that your database-using application did something wacko yesterday. You want to figure out why, but the data's changed in the meantime. Encoding time-series data yourself is quite tedious, so in a perfect world the DBMS would do it. Of course, this should be an on-line, not recovery, feature.

New Event Feature in MySQL 5.1.6

zblaxell — Wed, 25 Jan 2006 01:57:32 +0000

While I have built a number of large and small applications with various time-based event scheduling tables stored in an SQL database, including things like triggers that send asynchronous notifications to daemon clients to advise them to re-query for updated schedules, it never in my wildest imaginings occured to me to actually initiate execution autonomously from the database back end.

This sounds like something that would be useful to a web hosting customer who has access to CGI and MySQL but nothing else, and wants to get access to cron the next time their ISP upgrades the database without reading the release notes first.

New Event Feature in MySQL 5.1.6

nix — Thu, 19 Jan 2006 10:59:55 +0000

I have a hideous vision of combining this with PostgreSQL's Point-In-Time Recovery feature.

'If the time has moved back to {X time somewhere in the past}...'

New Event Feature in MySQL 5.1.6

jwb — Thu, 19 Jan 2006 08:34:03 +0000

As a MySQL user and paying customer, I know that the top of my wishlist reads "Implement a half-baked buggy featureless version of cron". Thank you MySQL AB for this wonderful contribution to humanity.

I can only assume that somewhere out there exists a version of the cron daemon which stores the crontabs in a MySQL table, making a kind of perfect Escher-like cycle of horror.