Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 2394F9FA49F for ; Wed, 17 Jan 2007 09:26:37 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-new, port 10024) with ESMTP id 38235-07 for ; Wed, 17 Jan 2007 09:26:05 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4 Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by postgresql.org (Postfix) with ESMTP id 2D4E69FA2D4 for ; Wed, 17 Jan 2007 09:26:10 -0400 (AST) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1H7Ana-0005XE-9m for pgsql-sql@postgresql.org; Wed, 17 Jan 2007 14:25:54 +0100 Received: from pc035-72.amg.gda.pl ([153.19.72.35]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 17 Jan 2007 14:25:54 +0100 Received: from mstepnicki by pc035-72.amg.gda.pl with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 17 Jan 2007 14:25:54 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-sql@postgresql.org From: =?iso-8859-2?q?Marcin_St=EApnicki?= Subject: Re: Postgresql & Oracle Heteregenous services - strange behaviour Date: Wed, 17 Jan 2007 14:25:41 +0100 Organization: Linux.PL Lines: 28 Message-ID: References: <20070117125857.GD19527@phlogiston.dyndns.org> <45AE1EDC.7090005@archonet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: pc035-72.amg.gda.pl User-Agent: Pan/0.14.2.91 (As She Crawled Across the Table (Debian GNU/Linux)) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.227 tagged_above=0 required=5 tests=AWL, BAYES_20, INFO_TLD, SPF_HELO_PASS, SPF_PASS X-Spam-Level: X-Archive-Number: 200701/70 X-Sequence-Number: 27222 Dnia Wed, 17 Jan 2007 13:04:28 +0000, Richard Huxton napisał(a): > Andrew Sullivan wrote: >> I bet it's getting the column list from the table or some such thing. >> This is a lousy way to do it (the information_schema would be more >> correct, although maybe no faster). > > That'd be my guess. And then it's not fetching any rows, expecting > cursor-like behaviour. Of course we fetch all the rows before returning > any results. Bingo! select * from from "zew_patients"@my_postgresql results in select a1.col1, a1.col2, a1.col3 from zew_patients in postgresql logs. > The real solution would be to add "LIMIT 0" or "LIMIT 1" to the > column-finding query, but I doubt that's possible with the Oracle plugin. > Perhaps check if there's a "fetch N rows at a time" option for the ODBC > setup that might help you. Thank you both, I'll poke around and drop a note when I find something :). -- | And Do What You Will be the challenge | http://apcoln.linuxpl.org | So be it in love that harms none | http://biznes.linux.pl | For this is the only commandment. | http://www.juanperon.info `---* JID: Aragorn_Vime@jabber.org *---' http://www.naszedzieci.org