X-Original-To: pgsql-interfaces-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id D44999FA432 for ; Tue, 12 Sep 2006 15:15:20 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 72730-08 for ; Tue, 12 Sep 2006 15:14:49 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from fep04.ttnet.net.tr (mail.ttnet.net.tr [212.175.13.129]) by postgresql.org (Postfix) with ESMTP id 182BD9FA0B9 for ; Tue, 12 Sep 2006 15:14:47 -0300 (ADT) Received: from alamut ([85.100.180.34]) by fep04.ttnet.net.tr with ESMTP id <20060912181446.UEYG13992.fep04.ttnet.net.tr@alamut>; Tue, 12 Sep 2006 21:14:46 +0300 Date: Tue, 12 Sep 2006 21:12:48 +0300 From: Volkan YAZICI To: Andro Cc: "Jeroen T. Vermeulen" , pgsql-interfaces@postgresql.org Subject: Re: cursors on prepared queries Message-ID: <20060912181248.GA1373@alamut> References: <24793.125.24.222.234.1158058065.squirrel@webmail.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.876 tagged_above=0 required=5 tests=AWL, SPF_PASS X-Spam-Level: * X-Archive-Number: 200609/5 X-Sequence-Number: 6250 On Sep 12 02:34, Andro wrote: > I just found this interesting link > http://lists.initd.org/pipermail/psycopg/2005-October/003999.html > about psycopg python interface which looks like able to make the use of > prepared statements within cursors. > > That means the protocol handles it but not libpq, right? No. Cursor understanding of Python DB adapters are quite different from the cursor - we create with DECLARE - in an RDBMS. psycopg just tries to imitate the cursor behaviour we're familiar with. OTOH, psycopg2 uses libpq too. It's quite unfeasible to think a feature psycopg supports that libpq does not. Regards.