>
>You could create a table in the database to hold this info. What would
>having it stored in the "metadata" get you that this would not?

When IBO or IB Console dumps the metadata, it produces something like the
following :

SET SQL DIALECT 3;

/* CREATE DATABASE 'localhost/3051:d:\temp\firebird\mydb01.fdb' PAGE_SIZE 4096

DEFAULT CHARACTER SET NONE */
/* Domain definitions */
CREATE DOMAIN "LOGICAL" AS CHAR(1)
DEFAULT 'N'
CHECK ( VALUE IN ( 'Y', 'N', 'T', 'F', 'y', 'n', 't', 'f')) NOT NULL;


What I would like to do is have it dump something like the following :

SET SQL DIALECT 3;

/*

ThisApplication version 1.022
ThatApplication version 5.432
Database version 0.091

*/

/* CREATE DATABASE 'localhost/3051:d:\temp\firebird\mydb01.fdb' PAGE_SIZE 4096

DEFAULT CHARACTER SET NONE */
/* Domain definitions */
CREATE DOMAIN "LOGICAL" AS CHAR(1)
DEFAULT 'N'
CHECK ( VALUE IN ( 'Y', 'N', 'T', 'F', 'y', 'n', 't', 'f')) NOT NULL;

Putting it in a table won't do that for me unless I have the engineer do it
on installation, which kind of defeats the purpose. :-)

Not only that, but in some dbms's (Sybase, for example) you can comment you
sps line for line, as you would comment code, so that other people can
understand what is going on. This isn't a description field - this is held
in the metadata itself, as in - line comments are in code.

Regards

Tim


[Non-text portions of this message have been removed]