> The idea is to have a scheduler for records that on timeout can call a > trigger. > Many existed databases (such as Oracle, MS SQL Server and MySQL) contain > a much wider idea, of task scheduler, while my idea is different.
I do not like your proposal. First, it would require that the database be opened in order for the timeout to occur. That being the case, it seems that you are looking to "hack" a Scheduler into the engine instead of implementing a true "Server Manager" which is what Oracle and MS SQL have. Where every database is registered with the Server Manager which is responsible for managing many aspects of the database functionality (task scheduler for SPs as well as database backups, email notifications...) I would suggest this is the feature which needs attention, rather than "timeout records". Sean ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
