Re: [HACKERS] Re: [PATCHES] COMMENT ON patch

--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> writes:
> > On Sun, 24 Oct 1999, Mike Mascari wrote:
> >> So in the example you gave above, you could put a comment
> >> on each of the two functions which compose the operator
> >> and a command on the operator itself.
>
> Two functions? An operator only has one underlying function.
> (Aggregates have as many as three though.)

I'm sorry...it was late a night. I meant you could comment on left
and right hand sides of the operator (the types) as well as the function
and also on the operator itself. I also spelled comment as command)...

>
> > Try \do and see for yourself. The fix should be rather simple but I'm
> not
> > sure where those descriptions are generated actually.
>
> The default contents of pg_description come from the DESCR() macros in
> include/catalog/*.h. It looks like only pg_proc and pg_type have any
> useful info in them in the current state of the source. I'm guessing
> that psql's \do actually looks for a description attached to the
> underlying function, rather than one attached to the operator.

Perhaps this behavior should continue. But I thought it would be
nice to comment on the function of the operator without respect to the
function.

Mike Mascari
(mascarim(at)yahoo(dot)com)

=====

__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com