Subject Re: [Firebird-Architect] Re: Vulcan services engine info. was (engine information (nr. of attachments, da
Author Ann W. Harrison
Roman Rokytskyy wrote:
> So, unless you make dispatcher to be some kind of provider that can
> handle some requests and delegate others, you can't solve this without
> breaking the layering.
Actually, that's the way that create database is handled, and
may not be a bad way to handle system-wide statistics. At
the entry point for that particular info call, the dispatcher
queries its providers, aggregates their statistics, and adds
its own.

Haven't checked this with Jim, but I did some of the work on
SpecialSql in the dispatcher, which parses create statements.