[ psqlodbc-Bugs-1000625 ] Serious performance issue with Delphi

Поиск
Список
Период
Сортировка
От
Тема [ psqlodbc-Bugs-1000625 ] Serious performance issue with Delphi
Дата
Msg-id 20060503123713.8521986C5C9@pgfoundry.org
обсуждение исходный текст
Список pgsql-odbc
Bugs item #1000625, was opened at 2006-05-03 09:01
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000625&group_id=1000125

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: Serious performance issue with Delphi

Initial Comment:
Greetings,
I'm using PostgreSQL 8.1 on Windows XP with the included ODBC driver (8.01.02.00 according to Control Panel) in Delphi
6or 2006, ADO components, MS OLE DB Provider for ODBC Drivers. 

I create an ADOQuery with a SELECT statement, and when issuing Open, it takes very long time to return (several
seconds,even if the SELECT is a very simple one fetching a couple of fields of a single record, for example). Enabling
logoutput to mylog I see that, for some reason, a WHERE-less SELECT * is performed right after my select, also inside
thesame Open. My table contains binary data (pictures), hence the long latency. The result of the SELECT * is
apparentlydiscarded, and the correct data from my select is returned by TADOQuery.Open. 

I can't understand who is performing the SELECT * and why, but it seems it only happens in Delphi. In the PostgreSQL
IRCchannel I've been suggested to try the QTADO query tool, and it runs smooth instead, with the very same setup. The
samedatabase served by MySQL does not show the problem using the MySQL ODBC driver, though. Perhaps some
incompatibilitybetween the Postgres ODBC driver and the Delphi database library? 

Thanks,
   Salvo
   salvois at users.sourceforge.net

----------------------------------------------------------------------

>Comment By: Ludek Finstrle (luf)
Date: 2006-05-03 14:37

Message:
Delphi sends the WHERE less command. The problem is that the Delphi doesn't get the right column information. The
solutionis in turning on the option Parse Statement in ODBC Datasource (or changing the connection string). 

Regards,

Luf

----------------------------------------------------------------------

You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000625&group_id=1000125

В списке pgsql-odbc по дате отправления:

Предыдущее
От:
Дата:
Сообщение: [ psqlodbc-Bugs-1000626 ] Follow-up to 1000625
Следующее
От:
Дата:
Сообщение: [ psqlodbc-Bugs-1000627 ] can't use stored functions