Skip site navigation (1) Skip section navigation (2)

Re: AsciiRow

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: bbadger(at)openskills(dot)com
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: AsciiRow
Date: 2002-12-16 18:13:26
Message-ID: 19954.1040062406@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-interfaces
Bruce Badger <bruce_badger(at)BadgerSE(dot)com> 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

In response to

  • AsciiRow at 2002-12-16 00:24:21 from Bruce Badger

pgsql-hackers by date

Next:From: Tom LaneDate: 2002-12-16 18:21:40
Subject: Re: PageGetMaxOffsetNumber
Previous:From: Patrick MacdonaldDate: 2002-12-16 17:59:03
Subject: Re: FW: Duplicate oids!

pgsql-interfaces by date

Next:From: Markus JaisDate: 2002-12-16 21:28:53
Subject: RPMS for Redhat 7.3 ??
Previous:From: Gerhard HaeringDate: 2002-12-16 02:51:21
Subject: Re: python bug

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group