Received: from localhost.localdomain (postgresql.org [64.49.215.8]) by localhost (Postfix) with ESMTP id CEB3C47683D for ; Tue, 18 Jun 2002 20:40:21 -0400 (EDT) Received: from brown.ursa-minor.com (unknown [66.152.196.35]) by postgresql.org (Postfix) with ESMTP id 12491477047 for ; Tue, 18 Jun 2002 19:26:44 -0400 (EDT) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by brown.ursa-minor.com (Postfix) with ESMTP id 8C3091C31E7; Tue, 18 Jun 2002 19:31:46 -0400 (EDT) Subject: Re: text vs varchar From: Michelle Murrain To: Wei Weng Cc: pgsql-sql@postgresql.org In-Reply-To: <1024438061.16895.2.camel@Monet> References: <1024438061.16895.2.camel@Monet> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.5 Date: 18 Jun 2002 19:31:46 -0400 Message-Id: <1024443106.15580.380.camel@brown.ursa-minor.com> Mime-Version: 1.0 X-Archive-Number: 200206/234 X-Sequence-Number: 8199 On Tue, 2002-06-18 at 18:07, Wei Weng wrote: > Is there any disadvantage of using TEXT datatype as opposed to a VARCHAR > datatype with a maximum length, especially when I do searches on them? There is one big disadvantage that I've found, but might be utterly unimportant to you. Some applications (particularly Crystal Reports) do not like unbounded text fields, and make it quite difficult to do any manipulations of them. This might be an odbc issue, rather than an application issue, but it can be a big deal sometimes. -- .Michelle ------------------------------ Michelle Murrain, Technology Consulting tech@murrain.net http://www.murrain.net 413-253-2874 413-222-6350 cell 413-825-0288 fax