From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [SQL] how to change the type |
Date: | 2001-12-07 21:41:46 |
Message-ID: | 20011207132327.H38113-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-sql |
On Fri, 7 Dec 2001, Tom Lane wrote:
> Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> writes:
> > Going down is
> > problematic, because if you have a varchar(5) field where one value is say
> > 'abcd' and you make it varchar(3) what happens?
>
> What would actually happen right now is nothing: the value would still
> be 'abcd' and would still read out that way. The 3-char limit would
> only get enforced during inserts and updates of the column.
That's what I figured, but I also assume that'd be "wrong" in a pure sense
since the value is invalid for the new datatype, so I figure its safer
to say up only. :)
From | Date | Subject | |
---|---|---|---|
Next Message | Philip Warner | 2001-12-07 23:02:50 | Re: pg_dump: Sorted output, referential integrity |
Previous Message | Tom Lane | 2001-12-07 21:38:48 | Re: Using Cursor in PostgreSQL 7.2 |
From | Date | Subject | |
---|---|---|---|
Next Message | Ligia Pimentel | 2001-12-07 22:06:02 | How to rename a database? |
Previous Message | Jonathan Nichols | 2001-12-07 21:14:59 | Variable Length Binary String (not large) |