Re: C++ interfaces - Mailing list pgsql-interfaces

From Randy Jonasz
Subject Re: C++ interfaces
Date
Msg-id Pine.BSF.4.21.0010101821470.65416-100000@nietzsche.jaded.net
Whole thread Raw
In response to Re: C++ interfaces  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-interfaces
Thanks for the info!  I've managed to look at all of the packets the
back-end and front end send to each other and have a fairly good idea of
what is expected.  Now for the hard part ...   

On Sat, 7 Oct 2000, Tom Lane wrote:

> Randy Jonasz <rjonasz@click2net.com> writes:
> > I'm currently looking at the packet structures that the back-end and
> > clients must use.  I've found that many packets are terminated with
> > 0x5A.  The docs don't mention this so I was wondering if anyone could
> > suggest why.
> 
> I suspect you are confusing the logically-separate ReadyForQuery
> message (which is a single byte 'Z') with the preceding data message.
> See http://www.postgresql.org/docs/postgres/protocol.htm, particularly
> the description of the basic Query cycle:
> 
> : A Query cycle is initiated by the frontend sending a Query message to
> : the backend. The backend then sends one or more response messages
> : depending on the contents of the query command string, and finally a
> : ReadyForQuery response message. ReadyForQuery informs the frontend that
> : it may safely send a new query or function call.
> 
>             regards, tom lane
> 
> 

Randy Jonasz
Software Engineer
Click2net Inc.
Web:  http://www.click2net.com
Phone: (905) 271-3550

"You cannot possibly pay a philosopher what he's worth,
but try your best" -- Aristotle



pgsql-interfaces by date:

Previous
From: Dnesbitt@encryptix.com
Date:
Subject: RE: Announcing PgSQL - a Python DB-API 2.0 compliant interface to PostgreSQL
Next
From: The Hermit Hacker
Date:
Subject: Re: Announcing PgSQL - a Python DB-API 2.0 compliant interface to PostgreSQL