isc_info_db_class and SuperClassic mode
At the moment the isc_info_db_class (link) returns only isc_info_db_class_classic_access or isc_info_db_class_server_access. I think the info_db_class should be expanded and MODE_SUPERCLASSIC should be handled.
Engine implements two kind of database access - Super (database opened in exclusive mode, all attachments are served by only process) and Classic (database opened in exclusive mode, attachments could be handled by multiple processes). SuperClassic is a special mode of network listener, engine works in Classic mode. More, in Classic mode there could be few processes that handle database and some of them could work in Classic mode and others - in SuperClassic. Thus I see no good reason for engine to return such info.
Why do you need it ? Perhaps new RDB$CONFIG table could satisfy your needs ?
I agree that such an info does not make any practical sense.
I was looking at it from end user POV. For these Firebird works in 3 possible configurations. But if it doesn't seem to make sense, it's fine.
BTW I also don't think people mix SuoerClassic ans Classic. And even then, server could return what the current instance is.
-- Mgr. Jiří Činčura https://www.tabsoverspaces.com/