From: | "Johann" <johann(at)tygerpos(dot)com> |
---|---|
To: | pgsql-odbc(at)postgresql(dot)org |
Subject: | queries run twice unless 'parse statements' checked? |
Date: | 2005-02-07 04:20:04 |
Message-ID: | 6.1.0.6.0.20050206211234.01d4aac0@pop.dnvr.uswest.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Running PostgreSQL 8.0, client is Visual Basic program using ADO, test case
has one adodc and a bound grid.
Queries involving a 188,000 row table were slow, even when query was on
single value in uniquely keyed index.
Turns out - from checking the plsqlodbc file, it was executing the query
once like I said:
select something from somewhere where thing=value
[returning one row]
then it ran the query again without the where clause [really!]
SELECT something FROM somewhere (The second query had the keywords turned
to upper case, if that helps identify what's going on.)
[returning 188,000 rows]
Naturally, this made things run slowly. I fiddled around and eventually
found that by checking "Parse Statements", this behavior stopped.
Anyway - is it supposed to work this way?
- Johann
From | Date | Subject | |
---|---|---|---|
Next Message | Layet Benjamin | 2005-02-07 07:04:07 | ODBC & character encoding |
Previous Message | Marco Tamanti | 2005-02-06 03:35:41 | varchar problem after installing postgresql-8.0.1 on windows |