| From: | Alex Pilosov <alex(at)pilosoft(dot)com> |
|---|---|
| To: | Andrew Sullivan <andrew(at)libertyrms(dot)com> |
| Cc: | PostgreSQL general list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: moving char() to varchar() |
| Date: | 2001-09-07 20:03:59 |
| Message-ID: | Pine.BSO.4.10.10109071603200.17071-100000@spider.pilosoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 7 Sep 2001, Andrew Sullivan wrote:
> 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?
Yes. varchar preserves padding, but does not add additional. char does add
additional.
> 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!)
Similar to what?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-09-07 20:20:01 | Re: What Is The Firing Order? |
| Previous Message | Bruce Momjian | 2001-09-07 20:01:46 | Re: What Is The Firing Order? |