On 15-6-2018 17:25, Dimitry Sibiryakov wrote:
15.06.2018 17:19, Mark Rotteveel wrote:
Having to rely on external lists like the Firebird 2.5 language
reference is a bit too brittle for my tastes, I'd like the truth
according to the Firebird itself.
But documentation is the only place where you can see name of
variable and its meaning. Knowledge of names without meaning is
pointless. What can you do with variable 'FOO' having value 'BAR'
(except simple display to an user which also have no idea what they are
for)?
Have you ever considered I simply want to list all values of all system
context variables. The tool doing that won't care about its meaning,
that will be the job of the person consulting the output.
Having to explicitly list all values within my sources is brittle as it
will miss values introduced in newer versions and gives additional
maintenance overhead.
And alternatively, Firebird could consider to make it self-documenting,
by including a description. That would be similar to what - for example
- PostgreSQL's pg_settings view does. Although the existing SYSTEM
namespace variables are relatively self-descriptive anyway.
Mark
--
Mark Rotteveel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
