On 02/22/12 00:14, ik wrote: > Hello, > > For a long time now, I have an idea for a feature, that I gave it a > name of "Timeout records" > (http://idkn.wordpress.com/2012/02/20/timeout-records-feature-request/). > Long before I'll ever try to report a feature request, I wish to have > a discussion about it, to better understand things from the > development point of view. > > 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. > You can find more information on it at the post I linked above. > > I would really be interested in hearing the development side of > things, and see how to develop the idea further before actually > opening a bug report of a feature request.
Well, this has some problems. - In what context should timeout trigger fire? - What to do if database server (or the whole box) is not active at the moment when timeout should fire? For firebird that issues are even more funny. - In what process should timeout trigger work in case of classic server? - What to do if given database file is not opened when timeout should fire? ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
