Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 63628475B8F for ; Fri, 22 Nov 2002 18:59:37 -0500 (EST) Received: from localhost.localdomain (m017-251.nv.iinet.net.au [203.217.17.251]) by postgresql.org (Postfix) with ESMTP id 841E5475A9E for ; Fri, 22 Nov 2002 18:59:35 -0500 (EST) Received: from BadgerSE.com (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.11.6/8.11.6) with ESMTP id gAMNxb804405 for ; Sat, 23 Nov 2002 10:59:37 +1100 Message-ID: <3DDEC4E9.8030201@BadgerSE.com> Date: Sat, 23 Nov 2002 10:59:37 +1100 From: Bruce Badger User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en MIME-Version: 1.0 Cc: pgsql-interfaces@postgresql.org Subject: Re: Frontend/Backend protocol changes? References: <200211221546.gAMFkBi21622@candle.pha.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200211/109 X-Sequence-Number: 3357 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.