From: Bruce Momjian <maillist@candle.pha.pa.us>
Message-Id: <199804190116.VAA07618@candle.pha.pa.us>
Subject: Re: [INTERFACES] Re: ODBC driver and Dates
To: hannu@trust.ee (Hannu Krosing)
Date: Sat, 18 Apr 1998 21:16:22 -0400 (EDT)
Cc: gerhardr@tech-edv.co.at, avd@avd.garsib.ru,
	pgsql-interfaces@postgreSQL.org, byronn@insightdist.com
In-Reply-To: <35387C24.43F04F82@sid.trust.ee> from "Hannu Krosing" at Apr 18,
	98 01:10:44 pm
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

> It has nothing to do with representation, but how data is transferred 
> between client and server. The representation is done et a completely 
> different level. It is due to PostgreSQL lacking a common universal 
> binary transfer format that these problems have emerged in the first 
> place - there is no sharp distinction between internal protocol and 
> external representation. 
> 
> I think it was not meant to be that way at first, as there are special 
> placed reserved in pg_type for both type conversion functions : 
> typinput/typoutput (presumably machine dependent ones) and 
> typreceive/typsend (presumably network-neutral ones), 
> somehow they are always the same .
> 
> I think that getting a common network-neutral binary format should also
> be in the TODO. Bruce?

This is an interesting idea.  It would be good to have more discussion
before I put something on the TODO list.  Not sure exactly where we are
going with this.

-- 
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)