X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 9D6E45E46D1 for ; Fri, 13 Aug 2004 00:30:19 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 11386-10 for ; Fri, 13 Aug 2004 03:30:23 +0000 (GMT) Received: from mammoth.utopiasystems.net (meridian1.utopiasystems.net [66.150.45.40]) by svr1.postgresql.org (Postfix) with ESMTP id BFB455E46C8 for ; Fri, 13 Aug 2004 00:30:12 -0300 (ADT) Received: from [192.168.1.100] ([67.173.111.107]) by mammoth.utopiasystems.net with Microsoft SMTPSVC(6.0.3790.0); Thu, 12 Aug 2004 23:28:42 -0400 User-Agent: Microsoft-Entourage/10.1.4.030702.0 Date: Thu, 12 Aug 2004 22:30:14 -0500 Subject: PG 7.2 varchar change From: slane To: Cc: Jamie Thomas Message-ID: In-Reply-To: <4001DEAF7DF9BD498B58B45051FBEA650146C600@25exch1.vicorpower.vicr.com> Mime-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable X-OriginalArrivalTime: 13 Aug 2004 03:28:42.0234 (UTC) FILETIME=[A1B905A0:01C480E5] X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=RCVD_IN_RFCI X-Spam-Level: X-Archive-Number: 200408/97 X-Sequence-Number: 14492 Hello all: I am upgrading a web application from postgres 7.1.2 to 7.4.3 (too long in coming to that point, I know). I have sifted through the history files and identified a restricted number of changes that potentially impact the app, a few of which I don=B9t understand. Here=B9s the currently most alarming, a change that is recorded for 7.2: CHAR(), VARCHAR() now reject strings that are too long (Peter E) What does this mean? Or how do I find out what it means? My understanding was that varchar fields had no text limit. But these are written like functions. Does this refer to coercion functions that now reject strings that are longer than the specified size of the underlying column? What if the column was specified as type =8Ctext=B9? And what was the old behavior? Thanks for any insight. This is the only change that=B9s really concerning = us deeply right now. -- sgl =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D Steve Lane Vice President Soliant Consulting 14 North Peoria St Suite 2H Chicago, IL 60607 voice: (312) 850-3930 email: slane@soliantconsulting.com fax: (312) 850-3930 web: http://www.soliantconsulting.com =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D