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
