Re: small doc patch for regexp_replace

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Joachim Wieland <joe(at)mcknight(dot)de>, pgsql-patches(at)postgresql(dot)org
Subject: Re: small doc patch for regexp_replace
Date: 2006-05-18 02:59:01
Message-ID: 7317.1147921141@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-patches

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Seems there is some inconsistency there. There are two types of
> function listings, one with just the types, and another with param_name
> and then type. We use "string" instead of "text" because varchar() and
> char() can also be used.

Where did that come from? The actual functions generally take "text",
relying on implicit conversions to handle the other types. Since we do
not have any type named "string", I think the locution <type>string</>
is a contradiction in terms.

IMHO these should all go back to <type>text</>.

regards, tom lane

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Bruce Momjian 2006-05-18 03:20:39 Re: small doc patch for regexp_replace
Previous Message Bruce Momjian 2006-05-18 00:54:37 Re: small doc patch for regexp_replace

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2006-05-18 03:20:39 Re: small doc patch for regexp_replace
Previous Message Bruce Momjian 2006-05-18 02:31:49 Re: BEGIN inside transaction should be an error