From: Matthew Hagerty <matthew@venux.net>
To: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] (libpq question) Holy cow, what's all this fluff?!
Date: Sun, 14 Feb 1999 00:17:59 -0500
Message-ID: <4.1.19990214001552.009894c0@mail.venux.net> (raw)
In-Reply-To: <36C65170.6AE6E97A@alumni.caltech.edu>
References: <4.1.19990213182304.0095d400@mail.venux.net>
<99021317445301.11018@taral.dobiecenter.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: matthew@venux.net
Subject: Re: [INTERFACES] (libpq question) Holy cow, what's all this fluff?!
In-Reply-To: <4.1.19990214001552.009894c0@mail.venux.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox