Subject | Engine information (nr. of attachments, databases, db-name-info) for vulcan |
---|---|
Author | Arno Brinkman |
Post date | 2006-05-06T16:37:46Z |
Hi All,
Currently in vulcan the services don't provide information about the number of attachments,
databases and attached db-names. This code is disabled because the way it was implemented it breaks
the layering.
To enable this service function again i propose to add a function called fb_engine_info() to the
engine. This function should be extensible for future features, so i propose to use info items (same
as isc_database_info). Some new info items needs to be declared for fb_engine_info() inside ibase.h.
The function needs also to be added to the subsystem (and by default does nothing?). Engine8 will
override it and call the function in jrd.
We could have multiple engines, so we need to walk through all known providers and subsystems. For
every subsystem from the provider the fb_engine_info() function is called.
As far as i understand the Dispatcher it the place to handle this.
I see some problems with walking through all providers:
What if an info_item isn't supported by engine-old, but it is by engine-new.
We can't ask information for a specific engine.
Ideas, suggestions, comments?
Regards,
Arno Brinkman
ABVisie
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
General database development support:
http://www.databasedevelopmentforum.com
Firebird open source database (based on IB-OE) with many SQL-99 features :
http://www.firebirdsql.org
http://www.firebirdsql.info
http://www.fingerbird.de/
http://www.comunidade-firebird.org/
Support list for Firebird and Interbase users :
firebird-support@yahoogroups.com
Nederlandse firebird nieuwsgroep :
news://newsgroups.firebirdsql.info
Currently in vulcan the services don't provide information about the number of attachments,
databases and attached db-names. This code is disabled because the way it was implemented it breaks
the layering.
To enable this service function again i propose to add a function called fb_engine_info() to the
engine. This function should be extensible for future features, so i propose to use info items (same
as isc_database_info). Some new info items needs to be declared for fb_engine_info() inside ibase.h.
The function needs also to be added to the subsystem (and by default does nothing?). Engine8 will
override it and call the function in jrd.
We could have multiple engines, so we need to walk through all known providers and subsystems. For
every subsystem from the provider the fb_engine_info() function is called.
As far as i understand the Dispatcher it the place to handle this.
I see some problems with walking through all providers:
What if an info_item isn't supported by engine-old, but it is by engine-new.
We can't ask information for a specific engine.
Ideas, suggestions, comments?
Regards,
Arno Brinkman
ABVisie
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
General database development support:
http://www.databasedevelopmentforum.com
Firebird open source database (based on IB-OE) with many SQL-99 features :
http://www.firebirdsql.org
http://www.firebirdsql.info
http://www.fingerbird.de/
http://www.comunidade-firebird.org/
Support list for Firebird and Interbase users :
firebird-support@yahoogroups.com
Nederlandse firebird nieuwsgroep :
news://newsgroups.firebirdsql.info