Re: Show max_identifier_length causes heavy query execution - Mailing list pgsql-odbc

From Hiroshi Inoue
Subject Re: Show max_identifier_length causes heavy query execution
Date
Msg-id 4A1F2693.3080706@tpf.co.jp
Whole thread Raw
In response to Re: Show max_identifier_length causes heavy query execution  (Moreno D. <moreno.d@hotmail.it>)
Responses Re: Show max_identifier_length causes heavy query execution  (Moreno D. <moreno.d@hotmail.it>)
List 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
turnedoff. 

Please look at the attached documentation especially about Parse
  Statements, ServerSide Prepare or Disallow Premature options.

regards,
Hiroshi Inoue

pgsql-odbc by date:

Previous
From: Moreno D.
Date:
Subject: Re: Show max_identifier_length causes heavy query execution
Next
From: Pragadheeswaran Gopalakrishnan
Date:
Subject: Pragadheeswaran Gopalakrishnan sent you a Friend Request on Yaari