Dmitry,
>> SELECT rdb$get_context('SYSTEM', 'ENGINE_64BITS') from
>> rdb$database; True/False SELECT rdb$get_context('SYSTEM',
>> 'ENGINE_IMPLEMENTATION') from rdb$database; 66 and
>> IMPLEMENTATION_NAME "Firebird/linux AMD64",
>
> Why is it necessary? I see no sense in knowing that information
> inside procedures/triggers. As for regular users, they'd better ask
> sysadmin about the used server architecture.
Knowing that information might be required for
installation/configuration purposes (f. ex. tailoring DECLARE FUNCTION
statements) in cases when automation is necessary, which rules out
asking a sysadmin (not to mention that a vast number or Firebird
installations run in places where sysadmin is an unknown word). Getting
it through the SQL interface is just a proven and universal way which
will work for everyone. The Services API might/should support it as well
for the sake of completeness, although I wouldn't lose sleep on it
(personally I have never bought the point of SAPI itself - much better
would be, IMO, to expose the same features through SQL statements
executed in a connection to a well-known system pseudo-database).
I'd use something more open than 'ENGINE_64BITS', though. Maybe
'SYSTEM_ARCHITECTURE'.
My 2c.
--
Nando Dessena
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
