Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Two fixes for plpgsql.sgml
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: Bruce Momjian <bruce(at)momjian(dot)us>
- Cc: Guillaume Lelarge <guillaume(at)lelarge(dot)info>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-docs(at)postgresql(dot)org
- Subject: Re: Two fixes for plpgsql.sgml
- Date: Wed, 28 Nov 2007 15:38:01 -0500
Bruce Momjian <bruce(at)momjian(dot)us> writes: > Agreed. I couldn't find any value to that phrase and couldn't find better > wording, so I removed it. Patch attached and applied. This is not an improvement. The point of the original wording is that you have to say RETURNS SETOF sometype you can't just say, eg, RETURNS SET Your new wording would lead the reader to the assumption that he can just declare a function as returning "set". Please revert the change. regards, tom lane
- Follow-Ups:
- Re: Two fixes for plpgsql.sgml
- From: Bruce Momjian
- Re: Two fixes for plpgsql.sgml
- References:
- Re: Two fixes for plpgsql.sgml
- From: Bruce Momjian
- Re: Two fixes for plpgsql.sgml
- Prev by Date: Partition: use triggers instead of rules
- Next by Date: Re: Partition: use triggers instead of rules
- Previous by thread: Re: Two fixes for plpgsql.sgml
- Next by thread: Re: Two fixes for plpgsql.sgml
- Indexes: