Greetings,
I want to discuss this before posting it to the wish list section of the
bug tracker to see if others see value in the suggestion or have a better
suggestion for implementation.
I am currently using a diagramming tool that allows extensive comments upon
referential integrity constraints and it helps with the long term
documentation/support of a database, but, I notice that there is no method
of storing such comments in the database itself. It also allows comments
upon the security grants between users, roles and sql objects.
Currently the "comment on" command supports the following
COMMENT ON *<object>* IS {'*sometext*' | NULL}
*<object>* ::= DATABASE
| *<basic-type>* *objectname*
| COLUMN *relationname*.*fieldname*
| PARAMETER *procname*.*paramname*
*<basic-type>* ::= CHARACTER SET | COLLATION | DOMAIN | EXCEPTION
| EXTERNAL FUNCTION | FILTER | GENERATOR | INDEX
| PROCEDURE | ROLE | SEQUENCE | TABLE | TRIGGER | VIEW
I would suggest the following would be helpful if possible
COMMENT ON *<object>* IS {'*sometext*' | NULL}
*<object>* ::= DATABASE
| *<basic-type>* *objectname*
| COLUMN *relationname*.*fieldname*
| PARAMETER *procname*.*paramname*
*<basic-type>* ::= CHARACTER SET | COLLATION | DOMAIN | EXCEPTION
| EXTERNAL FUNCTION | FILTER | GENERATOR | INDEX
| PROCEDURE | ROLE | SEQUENCE | TABLE | TRIGGER | VIEW
| CONSTRAINT |PRIVILEGE
Now the last one is for comments upon security privileges as in why a
particular user or role would need that specific security right.
>From what I can see, there is no place to hold the descriptions for these
new comments so a system table change would be needed if this was
implemented.
Also, from a users perspective, I can not find any documentation on how to
see the comments upon an object except by querying the system tables.
Should there not be a command that alleviates the users needs to touch the
system tables - perhaps a SQL command such as the following
DESCRIBE *<object>*
*<object>* ::= DATABASE
| *<basic-type>* *objectname*
| COLUMN *relationname*.*fieldname*
| PARAMETER *procname*.*paramname*
*<basic-type>* ::= CHARACTER SET | COLLATION | DOMAIN | EXCEPTION
| EXTERNAL FUNCTION | FILTER | GENERATOR | INDEX
| PROCEDURE | ROLE | SEQUENCE | TABLE | TRIGGER | VIEW
| CONSTRAINT | PRIVILEGE
I am only suggesting "DESCRIBE" as I do not know of a SQL standard command
for doing what I am suggesting.
Of coarse the above would also need to be adjusted if we where to use
SCHEMA name-spaces/security spaces in the future.
Thoughts?
Best regards
Dalton
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
