Re: [INTERFACES] (libpq question) Holy cow, what's all this fluff?! - Mailing list pgsql-interfaces

From Matthew Hagerty
Subject Re: [INTERFACES] (libpq question) Holy cow, what's all this fluff?!
Date
Msg-id 4.1.19990214001552.009894c0@mail.venux.net
Whole thread Raw
In response to Re: [INTERFACES] (libpq question) Holy cow, what's all this fluff?!  ("Thomas G. Lockhart" <lockhart@alumni.caltech.edu>)
Responses Re: [INTERFACES] (libpq question) Holy cow, what's all this fluff?!  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-interfaces
At 04:30 AM 2/14/99 +0000, Thomas G. Lockhart wrote:
>> You want a varchar (or is it bpchar?), not a char. char(x) will always
>> return x characters, with space padding if necessary.
>
>"bpchar" == "blank padded char", which is what char() is mapped to
>internally. As Matthew has already learned, he probably really wants to
>be using varchar(), or fix it up with trim().
>
>                       - Tom

Yeah, but the docs say you get a performance hit for using varchar, text,
and the like.  Which is worse, the database performance hit or the extra
call to trim for every char field?

Matthew


pgsql-interfaces by date:

Previous
From: "Thomas G. Lockhart"
Date:
Subject: Re: [INTERFACES] (libpq question) Holy cow, what's all this fluff?!
Next
From: Goda Attila
Date:
Subject: ODBC and wxWindows