From: slane <slane@moyergroup.com>
To: pgsql-admin@postgresql.org
Cc: Jamie Thomas <jthomas@soliantconsulting.com>
Subject: PG 7.2 varchar change
Date: Thu, 12 Aug 2004 22:30:14 -0500
Message-ID: <BD419FF6.1880F%slane@moyergroup.com> (raw)
In-Reply-To: <4001DEAF7DF9BD498B58B45051FBEA650146C600@25exch1.vicorpower.vicr.com>
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¹t
understand.
Here¹s 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 Œtext¹? And what was the old behavior?
Thanks for any insight. This is the only change that¹s really concerning us
deeply right now.
-- sgl
=======================================================
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
=======================================================
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: slane@moyergroup.com, jthomas@soliantconsulting.com
Subject: Re: PG 7.2 varchar change
In-Reply-To: <BD419FF6.1880F%slane@moyergroup.com>
References: <4001DEAF7DF9BD498B58B45051FBEA650146C600@25exch1.vicorpower.vicr.com> <BD419FF6.1880F%slane@moyergroup.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox