Received: from ns.infoset.cz (ns.infoset.cz [194.213.32.210]) by hub.org (8.9.3/8.9.3) with ESMTP id IAA58391 for ; Wed, 29 Sep 1999 08:27:38 -0400 (EDT) (envelope-from dpeder@infoset.cz) Received: from WinProxy.anywhere ([62.168.15.178]) by ns.infoset.cz (8.8.7/8.8.7) with SMTP id OAA32492; Wed, 29 Sep 1999 14:28:06 +0200 Received: from 192.168.1.1 by 192.168.1.3 (WinProxy); Wed, 29 Sep 1999 14:29:46 +0100 Received: by Dan with Microsoft Mail id <01BF0A86.94B44200@Dan>; Wed, 29 Sep 1999 14:26:12 +0100 Message-ID: <01BF0A86.94B44200@Dan> From: =?iso-8859-2?Q?Daniel_P=E9der?= To: "'pgsql-sql@postgresql.org'" Cc: "'pgsql-hackers@postgres.org'" Subject: extended cursor-FETCH usage Date: Wed, 29 Sep 1999 14:26:11 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit is there any possibility to use output from FETCH directly to -for example- creating a new table? Something like: FETCH 10 FROM MyCursor INTO TEMP TABLE MyTempTable ( x int4, y text ); Why do I need it? It could be sometimes faster/much effective to do this first and then do JOIN operations on table/dataset reduced this way. -- Dan Peder dpeder@infoset.cz