On Mon, 2006-08-07 at 14:11, MargaretGillon@xxxxxxxxxxxxxx wrote: > >"Uwe C. Schroeder" <uwe@xxxxxxxxx> wrote on 08/07/2006 11:30:28 AM: > > Well, you cast all those fields to be concatenated to text. Why > should the db > > make a varchar out of that? I seriously doubt that 7.x made a > varchar of that > > - but then, 7.2 is very very old. > > So either cast your fields to varchar (i.e. c.refullname::varchar || > > d.enname::varchar) or cast the result of the concatenation to a > varchar. > > > > UC > > FYI in 8.1.4 if the cast is changed to varchar the result still comes > out as a text field > >> SELECT (c.refullname::varchar || d.enname::varchar || > f.evname::varchar) AS evlinkname1, > results in evlinkname1 as text Just FYI, text and varchar are, internally, pretty much the same types. varchar has an optional precision setting as in varchar(200) while text does not allow one. All the text ops are written for text types, so varchar gets cast as text (as do char types) before being operated on. Note that you can cast the result of that select above to varchar: SELECT (c.refullname || d.enname || f.evname)::varchar AS evlinkname1
