Subject Re: [Firebird-Architect] Database Capabilities
Author Helen Borrie
At 07:30 AM 22/07/2005 -0400, you wrote:

>Helen Borrie wrote:
> >
> >Agreed - Jim, do you have some wires crossed here? Your suggestion was
> >aimed at a mechanism to report the attributes of the database engine, i.e.,
> >presumably a service call of some sort; but then you proceed to suggest
> >that it could be a *database* info structure. Why would you write the
> >engine capabilities into databases? Isn't it the ODS level that matters
> >when considering what a database can support?
> >
> >
>The database info call can give information about either the engine or
>the attached database, for example the version strings of the engine and
>various transmission layers. It's always been that way. understood your proposal was to provide some kind of info
structure packaging up the ENGINE capabilities. AFAIK, what has "always
been that way" was the server version string, which is contingent on a
connection to a database.