On 26/02/2015 10:29, Carlos H. Cantu wrote: > I would like to start a discussion to propose the implementation of > "Event triggers" (for the lack of a better name for now). > > Those special triggers would be associated to an EVENT, not to a > TABLE. When the associated event is fired in any of the active > attachments, all the active attachments "interested" in that event > would run the trigger. > > My personal example of use for such feature, would be to force the > update of global context variables in all active attachments, when > the EVENT is fired. > > Of course there are questions to be discussed, for example: the > trigger would ran in what transaction context? Should it be forced to > be ReadOnly (making things simpler, but much more limited)? > > I think FB 3 has features capable to let this be easily implemented by user.
For example, there is example UDR who waits for an event, blocking the calling. I don't test asynchronous entering in an UDR due to an event, but it may (or should) be possible. Question about when trigger and what transaction, also is customizable with ON CONNECT triggers and autonomous transactions. Adriano ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
