Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA53207 for ; Thu, 13 May 1999 10:12:47 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id KAA08552; Thu, 13 May 1999 10:11:32 -0400 (EDT) To: henrik@steffen.stade.net cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] VARCHAR(50), CHAR(50) or TEXT ? In-reply-to: Your message of Thu, 13 May 1999 13:14:15 +0200 <373AB407.15E84C71@city-map.de> Date: Thu, 13 May 1999 10:11:32 -0400 Message-ID: <8550.926604692@sss.pgh.pa.us> From: Tom Lane Henrik Steffen writes: > But, what is the difference between VARCHAR and TEXT ? Almost none. VARCHAR won't let you go beyond the stated maximum length, whereas TEXT has no specific upper limit. Otherwise they are stored in exactly the same way. (At least in Postgres ... dunno about other DBMSs.) I'd be inclined to use TEXT unless the maximum length were really an important part of the semantics of the data for my application. If you find yourself saying "Well, I *think* it'll never go beyond N characters, but maybe I should add a little slop for safety" then I'd say forget all about VARCHAR and use TEXT. If you find yourself saying "it *had better not* go beyond N characters, because that app over there will crash if it does" then use VARCHAR to enforce the limit. regards, tom lane