Re: [DOCS] [PATCHES] small doc patch for regexp_replace
Tom Lane wrote: > Bruce Momjian 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. There are many mentions of string used a function arguments in func.sgml. Should those be changed to text? -- Bruce Momjian http://candle.pha.pa.us EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
Re: [DOCS] [PATCHES] small doc patch for regexp_replace
Bruce Momjian writes: > There are many mentions of string used a function > arguments in func.sgml. Should those be changed to text? string is fine, especially if the function actually has a separate variant for bpchar. I was just unhappy with string, which is a lie. regards, tom lane ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [DOCS] [PATCHES] small doc patch for regexp_replace
Tom Lane wrote: > Bruce Momjian writes: > > There are many mentions of string used a function > > arguments in func.sgml. Should those be changed to text? > > string is fine, especially if the function actually has a > separate variant for bpchar. I was just unhappy with string, FYI, in most cases, they don't have bpchar variants. -- Bruce Momjian http://candle.pha.pa.us EnterpriseDBhttp://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
