Subject | Re: [Firebird-Architect] Vulcan services part II |
---|---|
Author | Arno Brinkman |
Post date | 2006-05-11T10:27:04Z |
Hi,
Regards,
Arno Brinkman
ABVisie
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
General database developer 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
Support list for Interbase and Firebird users:
firebird-support@yahoogroups.com
Nederlandse firebird nieuwsgroep:
news://newsgroups.firebirdsql.info
> So, fb_engine_info in this case must return information from onlyThe name "database" suggest information about single database not about server-version, multiple databases, etc...
> one provider? What's the difference from isc_database_info()?
>>> We are discussing about which provider must provide informationBackwards compatibility of "isc_info_svc_svr_db_info" info item in the service.
>>> about engine. I think that it must be the engine because only engine
>>> has all necessary information.
>>
>>Yes, and were discussing which method to use, but for backwards
>>compatibilty this must be supported inside services provider.
>
> Vulcan has backward comatibility? There are previous versions of
> Vulcan?
> I don't understand this: "for backwards compatibilty this must be
> supported inside services provider". Who cares where requested
> information comes from - services provider, engine or Y-valve as long
> as the information is correct.
Regards,
Arno Brinkman
ABVisie
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
General database developer 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
Support list for Interbase and Firebird users:
firebird-support@yahoogroups.com
Nederlandse firebird nieuwsgroep:
news://newsgroups.firebirdsql.info