Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 97451475F5F for ; Fri, 4 Oct 2002 06:22:07 -0400 (EDT) Received: from news.hub.org (news.hub.org [64.49.215.80]) by postgresql.org (Postfix) with ESMTP id 2F6D9475F4F for ; Fri, 4 Oct 2002 06:22:07 -0400 (EDT) Received: by news.hub.org (Postfix, from userid 8) id 5FBE6381635; Fri, 4 Oct 2002 06:22:06 -0400 (EDT) From: g.hintermayer@inode.at (Gerhard Hintermayer) X-Newsgroups: comp.databases.postgresql.interfaces Subject: libpgtcl/pg_execute undocumented feature ? Date: 4 Oct 2002 03:16:33 -0700 Organization: http://groups.google.com/ Lines: 7 Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: groups-abuse@google.com To: pgsql-interfaces@postgresql.org X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/3 X-Sequence-Number: 3165 I was just trying to implement a -numAffected option to pg_result to get the number of affected tuples when invoking INSERT/UPDATE/DELETE when I saw, that there is already a command that does give me the number of affected tuples. Will pg_execute be dropped in uncoming releases ? Gerhard Hintermayer