From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | David Fetter <david(at)fetter(dot)org>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Dollar Quoting doc patch--resend. |
Date: | 2004-05-06 04:41:37 |
Message-ID: | 200405060441.i464fb327641@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Neil Conway wrote:
> On 5-May-04, at 10:42 AM, Bruce Momjian wrote:
> > I disagree. I think swiching between single quote and $$ based on the
> > content is just too confusing. I would just use $$ in all cases unless
> > $$ appears in the function (which should be rare), in which case I
> > would
> > use $quote$ or something generic.
>
> Well, the function definition in CREATE FUNCTION is a string literal
> like any other. Based on the reasoning above, would you argue for using
> $$ for every other string literal in the documentation rather than
> single quotes? If not, then we're not being consistent anyway, so I
> don't find the argument very convincing.
>
> Why not use whatever quoting mechanism is clearest for a particular
> example? In some cases that will be single-quotes, in others it will be
> dollar quoting via $$, and in still others it will be dollar quoting
> via $tag$
OK. I am just afraid if we show 4 functions, and three use $$, and one
doesn't use single-quotes inside, so we quote with single-quotes, that
it would look strange.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2004-05-06 04:44:32 | Re: Dollar Quoting doc patch--resend. |
Previous Message | Neil Conway | 2004-05-06 03:45:36 | Re: Dollar Quoting doc patch--resend. |