| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | hannu(at)trust(dot)ee (Hannu Krosing) |
| Cc: | gerhardr(at)tech-edv(dot)co(dot)at, avd(at)avd(dot)garsib(dot)ru, pgsql-interfaces(at)postgreSQL(dot)org, byronn(at)insightdist(dot)com |
| Subject: | Re: [INTERFACES] Re: ODBC driver and Dates |
| Date: | 1998-04-19 01:16:22 |
| Message-ID: | 199804190116.VAA07618@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
> 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(at)candle(dot)pha(dot)pa(dot)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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julia A.Case | 1998-04-19 08:50:01 | Re: [INTERFACES] Re: ODBC 16 bit support |
| Previous Message | The Hermit Hacker | 1998-04-18 18:09:36 | Re: ODBC 16 bit support |