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.
Description: text/html (13.8 KB)
In response to
pgsql-odbc by date
|Next:||From: Pragadheeswaran Gopalakrishnan||Date: 2009-05-30 08:44:14|
|Subject: Pragadheeswaran Gopalakrishnan sent you a Friend Request on Yaari|
|Previous:||From: Moreno D.||Date: 2009-05-28 13:42:52|
|Subject: Re: Show max_identifier_length causes heavy query execution|