Postgres Pro
Downloads
Home   >   mailing lists

Re: Inconsistency: varchar is equivalent to varchar(255) and also not equivalent? - Mailing list pgsql-general

From Scott Ribe
Subject Re: Inconsistency: varchar is equivalent to varchar(255) and also not equivalent?
Date
Msg-id E2EF5EAD-2EDD-429A-BC73-4E5157DCA9B6@elevated-dev.com
Whole thread Raw
In response to Inconsistency: varchar is equivalent to varchar(255) and also not equivalent?  (Boszormenyi Zoltan <zb@cybertec.at>)
Responses Re: Inconsistency: varchar is equivalent to varchar(255) and also not equivalent?  (Boszormenyi Zoltan <zb@cybertec.at>)
List pgsql-general
Tree view 
On Oct 3, 2011, at 10:12 AM, Boszormenyi Zoltan wrote:

> But I would like to know why isn't the type conversion from unlimited varchar
> to varchar(255) invoked in the pl/pgsql function?

What if t1 || t2 is longer than 255? You need to explicitly specify.

--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice

pgsql-general by date:

Previous
From: Boszormenyi Zoltan
Date:
Subject: Re: Inconsistency: varchar is equivalent to varchar(255) and also not equivalent?
Next
From: Alban Hertroys
Date:
Subject: Re: Inconsistency: varchar is equivalent to varchar(255) and also not equivalent?