On Sat, Sep 29, 2018, 12:14 Dimitry Sibiryakov <s...@ibphoenix.com> wrote:
> 29.09.2018 16:30, Dmitry Yemanov wrote: > > AFAIU, Adriano's point is more about technology (use stall mode for the > function request), > > syntax may be adjusted. We may choose a different keyword, if necessary > (as a syntax sugar > > for the same BLR verb). > > Ok. How simple is this technology from engine POV if there are several > user-defined > aggregates in a query? > One function fetched a row from result set, then another do the same. > Wouldn't be > non-cached result set in troubles? > What engine will do if one of functions return without calling SUSPEND? > It's the engine who controls the moving of rows in the dataset. It moves a row and continue each aggregate function and so on. It already does this for internal aggregate functions. Adriano
Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
