Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id E166347654A for ; Mon, 16 Dec 2002 13:13:39 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 87C7F476515 for ; Mon, 16 Dec 2002 13:13:31 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id gBGIDQpd019955; Mon, 16 Dec 2002 13:13:27 -0500 (EST) To: bbadger@openskills.com Cc: pgsql-interfaces@postgresql.org Subject: Re: AsciiRow In-reply-to: <3DFD1D35.8090907@BadgerSE.com> References: <3DFD1D35.8090907@BadgerSE.com> Comments: In-reply-to Bruce Badger message dated "Mon, 16 Dec 2002 11:24:21 +1100" Date: Mon, 16 Dec 2002 13:13:26 -0500 Message-ID: <19954.1040062406@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200212/55 X-Sequence-Number: 3468 Bruce Badger writes: > The description of AsciiRow says that for each field it contains "the > value of the field itself in ASCII characters". The description is here: > http://postgresql.org/users-lounge/docs/7.3/postgres/protocol-message-formats.html > Looking at the bytes comming over the Frontend/Backend protocol, > however, it seems that the field is really always a String encoded > according to the settings in the database - is that right? I believe this documentation's reference to ASCII shouldn't be taken very literally; it really just means "text" (as opposed to some internal binary representation) and is not meant to imply anything about one character set encoding versus another. You're correct that the data would actually appear in the currently-selected client encoding, assuming that the backend is configured to support encoding conversions. regards, tom lane