Subject | Re: [Firebird-Architect] Database Capabilities |
---|---|
Author | Jim Starkey |
Post date | 2005-07-22T11:30:38Z |
Helen Borrie wrote:
the attached database, for example the version strings of the engine and
various transmission layers. It's always been that way.
>The database info call can give information about either the engine or
>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 attached database, for example the version strings of the engine and
various transmission layers. It's always been that way.
>
>
>
>