| From: | Hiroshi Inoue <inoue(at)tpf(dot)co(dot)jp> |
|---|---|
| To: | "Moreno D(dot)" <moreno(dot)d(at)hotmail(dot)it> |
| Cc: | laurenz(dot)albe(at)wien(dot)gv(dot)at, pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: Show max_identifier_length causes heavy query execution |
| Date: | 2009-05-29 00:04:35 |
| Message-ID: | 4A1F2693.3080706@tpf.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
Moreno D. wrote:
>> If that is the cause of your problem, then setting "Parse=1"
>> will fix it.
>>
>> In ODBC Administrator on Windows, this option is called "Parse Statements"
>> and can be found in the advanced options page 1 (Button "Datasource").
>
> Thank you Laurenz, setting "Parse=1" solved my problem!
> Anyway, another problem appeared at another point in the application, i think this is the reason why that flag was turned off.
Please look at the attached documentation especially about Parse
Statements, ServerSide Prepare or Disallow Premature options.
regards,
Hiroshi Inoue
| Attachment | Content-Type | Size |
|---|---|---|
| config.html | text/html | 13.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pragadheeswaran Gopalakrishnan | 2009-05-30 08:44:14 | Pragadheeswaran Gopalakrishnan sent you a Friend Request on Yaari |
| Previous Message | Moreno D. | 2009-05-28 13:42:52 | Re: Show max_identifier_length causes heavy query execution |