From: | Ludek Finstrle <luf(at)pzkagis(dot)cz> |
---|---|
To: | Zoltan Boszormenyi <zboszor(at)dunaweb(dot)hu> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: PsqlODBC slow on UNION queries |
Date: | 2006-01-10 21:15:59 |
Message-ID: | 20060110211559.GB8098@soptik.pzkagis.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
> > If I set only Declare/Fetch or both to ON, opening the VIEW in Access
> > comes close to what I experinced in psql, e.g. it appears almost instantly
> > when using UNION ALL, and just under 7 seconds when using UNION.
> >
> > I don't remember which ODBC settings I used for the Windows2000 client
> > and PowerBuilder, I am not near that machine. I will recheck it when
> > I get back to my workplace next monday.
>
> There is another thing. psqlODBC driver simulate SQLColAttributes (I wrote
> it on the fly so it could be different ODBC API) throught call
> the query and then get the columns information before query is already
> open. So it could be the time bottleneck.
> I try describe it better:
> SQLPrepare, SQLColAttributes (this call the statement for getting columns
> information), SQLExecute (this call the statement for result).
>
> If you want trace it down the good start point is turn mylog output on
> and read the result in C:\mylog_XXXX.log (or txt extension?).
I forgot. Feel free to send the mylog output here to list. We can
help you to decode it ;-)
Regards,
Luf
From | Date | Subject | |
---|---|---|---|
Next Message | Milton | 2006-01-10 21:39:09 | Re: I can't read the data in the second time |
Previous Message | Ludek Finstrle | 2006-01-10 21:05:51 | Re: I can't read the data in the second time |