From: | "Mitch Vincent" <mvincent(at)cablespeed(dot)com> |
---|---|
To: | "Andrew Sullivan" <andrew(at)libertyrms(dot)com>, "PostgreSQL general list" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: moving char() to varchar() |
Date: | 2001-09-07 19:50:33 |
Message-ID: | 008201c137d6$5b8a16b0$1e51000a@mitch |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> 1. I thought the SQL spec required varchar() not to pad. Is it
> just that, because of the way pg_dump saved the char() data (as
> blank-padded) that the varchar() field preserves the padded data?
A dump from a char() field keeps the NULL padding even in the dump file I
assume, so when you went to import it you were importing data with NULLs
attached..
> 2. I could _swear_ I did something very similar to this some
> time ago (version 6.5.x? something like that?). Am I just imagining
> things? (I'm perfectly prepared to accept that, by the way. My
> memory is about as reliable these days as the DIMM I took out of my
> PC last week. That's why I need a good DBMS like postgres!)
I can't say one way or another on that.. But I feel your pain on the memory
problems :-)
-Mitch
From | Date | Subject | |
---|---|---|---|
Next Message | Brent R. Matzelle | 2001-09-07 19:54:58 | Re: moving char() to varchar() |
Previous Message | Thomas T. Thai | 2001-09-07 19:46:35 | Re: Idea: jobs.postgresql.org |