Received: from dobiecenter.com (mrx@r21014-5886.dobiecenter.com [208.247.21.14]) by hub.org (8.9.2/8.9.1) with ESMTP id SAA61806 for ; Sat, 13 Feb 1999 18:45:10 -0500 (EST) (envelope-from taral@cyberjunkie.com) Received: from taral.dobiecenter.com (mrx@localhost [127.0.0.1]) by dobiecenter.com (8.8.7/8.8.7) with SMTP id RAA11034; Sat, 13 Feb 1999 17:44:53 -0600 From: Taral To: Matthew Hagerty , pgsql-interfaces@postgreSQL.org Subject: Re: [INTERFACES] (libpq question) Holy cow, what's all this fluff?! Date: Sat, 13 Feb 1999 17:44:17 -0600 X-Mailer: KMail [version 1.0.14] Content-Type: text/plain References: <4.1.19990213182304.0095d400@mail.venux.net> MIME-Version: 1.0 Message-Id: <99021317445301.11018@taral.dobiecenter.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.org id SAA61809 On Sat, 13 Feb 1999, Matthew Hagerty wrote: >Greetings, > >When using the PQgetvalue() function of libpq, the results, at least char >fields, return the value in full, i.e. a char(20) field with the text >"Matthew" for example returns "Matthew " (all 20 characters, >padded with spaces). You want a varchar (or is it bpchar?), not a char. char(x) will always return x characters, with space padding if necessary. Taral