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: [EMAIL PROTECTED] fax: (312) 850-3930 web: http://www.soliantconsulting.com ======================================================= ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
