Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Rhinorhino on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Query Documentation

Status
Not open for further replies.

Felgar

Programmer
Joined
May 17, 2001
Messages
17
Location
CA
This is something that I've been sort of struggling with for a while now. I work at a software company, and so the situation often arises where we need to tweak someone else's query or where down the road our own queries will need to be completely understood by others.

So I'm wondering if anyone has any good solutions in terms of how a query/view can be documented. Views are even a more complex issue because they often cascade down a number of levels. But even some recursive queries can be fairly tough to fully understand by just looking the query itself over.

Any thoughts/ideas?
 
The most popular way of documenting views (as well as tables) is adding COMMENTS.

COMMENT ON COLUMN foo.bar IS 'This is bar colum of table foo and its meaning is outstanding'

View code may be queried from all_views, thus in this way it's self-documented (using comments in code).

Though to use this comments your customer should at least be aware of their existence Regards, Dima
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top