Re: protocol change in 7.4

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: snpe <snpe(at)snpe(dot)co(dot)yu>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: protocol change in 7.4
Date: 2002-12-10 22:28:22
Message-ID: 200212102228.gBAMSNO14729@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


I have added the following TODO item on protocol changes:

> * Wire Protocol Changes
> o Show transaction status in psql
> o Allow binding of query parameters, support for prepared queries
> o Add optional textual message to NOTIFY
> o Remove hard-coded limits on user/db/password names
> o Remove unused elements of startup packet (unused, tty, passlength)
> o Fix COPY/fastpath protocol?
> o Replication support?
> o Error codes
> o Dynamic character set handling
> o Special passing of binary values in platform-neutral format (bytea?)
> o ecpg improvements?
> o Add decoded type, length, precision

---------------------------------------------------------------------------

snpe wrote:
> On Thursday 07 November 2002 09:50 pm, korry wrote:
> > > > b) Send a decoded version of atttypmod - specifically, decode the
> > > > precision and scale for numeric types.
> > >
> > >I want decode type,length,precision and scale
> >
> > Type is returned by PQftype(), length is returned by PQfsize(). Precision
> > and scale are encoded in the return value from PQfmod() and you have to
> > have a magic decoder ring to understand them. (Magic decoder rings are
> > available, you just have to read the source code :-)
> >
> > PQftype() is not easy to use because it returns an OID instead of a name
> > (or a standardized symbol), but I can't think of anything better to return
> > to the client. Of course if you really want to make use of PQftype(), you
> > can preload a client-side cache of type definitions. I seem to remember
> > seeing a patch a while back that would build the cache and decode precision
> > and scale too.
> >
> > PQfsize() is entertaining, but not often what you really want (you really
> > want the width of the widest value in the column after conversion to some
> > string format - it seems reasonable to let the client applicatin worry
> > about that, although maybe that would be a useful client-side libpq
> > function).
> >
> >
> I want this in any catalog view
>
> regards
> Haris Peco
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-12-10 23:36:04 Re: PQnotifies() in 7.3 broken?
Previous Message Rod Taylor 2002-12-10 22:23:49 Re: Problems with ALTER DOMAIN patch