Leyne, Sean wrote:

>
> It seems, however, that users are looking for a method to access the
> version string(s) without needing to calling the API -- like an
> SP/Trigger variable or a new 'virtual' column in RDB$Database.
>
> I have opened tracker case # 1018 for this issue.

Right. The current API gives the version for each level of the
API - remote interface, remote server, and engine in most cases.
Would you want a separate field for each? And if the connection
used the "routing" protocol that goes through several layers of
remote access, how should that be handled? (That's generally
disabled as a security measure, but still exists.)

SQL> show version;
ISQL Version: WI-V2.0.0.4921 Vulcan 1.0 Development
Firebird/x86/Windows NT (access method), version
"WI-V2.0.0.12745 Firebird 2.0 Release Candidate 5"
Firebird/x86/Windows NT (remote server), version
"WI-V2.0.0.12745 Firebird 2.0 Release Candidate 5/tcp hotspur)/P10"
Firebird/x86/Windows NT (remote interface), version
"WI-V2.0.0.4921 Vulcan 1.0 Development/tcp (hotspur)/P10"
on disk structure version 11.0
SQL>


Regards,


Ann