Tom Lane wrote:
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
Why the random switching between newline-before and newline-after
styles? Please be consistent.
I thought they were all "after". On second glance, they still seem
all after?
Oh, my mistake, I had failed to see that the patch
"Greg Sabino Mullane" <[EMAIL PROTECTED]> writes:
>> Why the random switching between newline-before and newline-after
>> styles? Please be consistent.
> I thought they were all "after". On second glance, they still seem
> all after?
Oh, my mistake, I had failed to see that the patch was getting
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
>> Attached patch puts the "metadata" about a function, especially the
>> language name, at the top of the CREATE FUNCTION statement, above the
>> possibly long, multi-line function definition.
> Why the random switching between newline-before
Greg Sabino Mullane <[EMAIL PROTECTED]> writes:
> Attached patch puts the "metadata" about a function, especially the
> language name, at the top of the CREATE FUNCTION statement, above the
> possibly long, multi-line function definition.
Why the random switching between newline-before and newline
Attached patch puts the "metadata" about a function, especially the
language name, at the top of the CREATE FUNCTION statement, above the
possibly long, multi-line function definition.
--
Greg Sabino Mullane
Index: pg_dump.c
===
RCS
