From: Bruce Badger <bbadger@BadgerSE.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: Frontend/Backend protocol changes?
Date: Sat, 23 Nov 2002 10:59:37 +1100
Message-ID: <3DDEC4E9.8030201@BadgerSE.com> (raw)
References: <200211221546.gAMFkBi21622@candle.pha.pa.us>
Bruce Momjian wrote:
>What exactly was the change? As I remember, it was something we didn't
>think would affect anybody, but it did affect you.
>
Here's the comment from the code (in the CursorResponseMessage class) I
patched ....
"Due to a change in the fontend-backend protocol version 0 2 0 0, I must
check to see if another CursorResponseMessage follows right after the
one that led to my creation. If there is, I take the last one as being
the 'correct' one"
Note: the "I" and "my" in the comment refer to a
CursorResponseMessage instance.
Also, there was a discussion on this list between Tom and I about the
change and the direction it implied. The gist as I recall centered
around the question of whether every side-effect of a query should
return a distinct CursorResponseMessage in addition to the one for the
explicitly invoked query.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: bbadger@BadgerSE.com
Subject: Re: Frontend/Backend protocol changes?
In-Reply-To: <3DDEC4E9.8030201@BadgerSE.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox