Csaba Nagy <[EMAIL PROTECTED]> writes: > The only advantage would be that an in-database solution would be OS > independent
That kind of argument leads to monstrosities like Oracle that reimplement everything they can from the OS. What would be a neat project is if someone wrote a cron implementation that used postgres as a backend. You could run cron from the command-line and edit your cron jobs normally, but the resulting data would get stuffed into a postgres database. The cron daemon would connect to the database to get its information. This would be neat since it would let applications access and modify the data through a well defined programmatic interface, but the data could easily be queried using SQL to display in a nice GUI or HTTP interface. I suspect this would be very attractive to shared hosting systems. It would also be convenient for applications that want to provide more restricted access to application-specific routine jobs. This wouldn't really be a part of Postgres though, just another application using Postgres. It could be something Postgres could recommend for people who find cron too awkward for their application. -- greg ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
