-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=US-ASCII">
Log communications to/from the backend to that file. This is good
for debugging problems.<br /> </li>
-<li><b>Parse Statements:</b> If enabled,
+<li><b>Parse Statements:</b> Tell the driver how to gather the information about result columns of queries. See also <em>Disallow Premature</em> and <em>ServerSide Prepare</em> options.<br>
+The driver checks this option first. If disabled then it checks the Server Side Prepare option. If disabled also it checks the Disallow Premature option.<br>
+If neither of them is specified the driver would execute the prepared statement prematurely when the application inquires the result columns' info.<br><br>
+
+If this option is enabled,
the driver will parse an SQL query statement to identify the columns and
tables and gather statistics about them such as precision, nullability,
aliases, etc. It then reports this information in SQLDescribeCol,
<li><b>Disallow Premature:</b>
Mainly for 7.1 to 7.3 servers. <b><em>Server side prepare</em></b> is a more preferable option for 7.4+ servers.<br>
+Tell the driver how to gather the information about result columns. See also <em>Parse Staements</em> and <em>Server Side Prepare</em> options.<br>
This is an option to compensate for the lack of a server's <em>Prepare</em> functionality.
For example, (Middleware) applications issue the following ODBC API calls.<br><br>
<li><b>True is -1:</b> Represent TRUE as -1 for compatibility with some applications.
<br /> </li>
-<li><b>Server side prepare:</b> Available for 7.3+ servers and <em>recommended for 7.4+.</em><br /> 
-(7.4+) By using extended query protocol the driver replies to the inquiry for the information of columns or parameters correctly and effectively.<br> 
-(7.3+) When using prepared statements, prepare them on the server rather than in the driver. This can give a slight performance advantage as the server<br> 
-doesn't need to re-parse the statement each time it is used.<br /> </li>
+<li><b>Server side prepare:</b> Applicable for 7.3+ servers and <em>recommended for 7.4+.</em><br /> 
+(7.4+) Tell the driver how to gather the information about result columns. See also <em>Parse Statement</em> and <em>Disallow Premature</em> options.<br>        By using extended query protocol the driver replies to the inquiry correctly and effectively.<br> 
+(7.4+) By using extended query protocol the driver replies to the inquiry for the information of parameters.<br> 
+(7.3+) When using prepared statements, prepare them on the server rather than in the driver. This can give a slight performance advantage as the server<br>
+        doesn't need to re-parse the statement each time it is used.<br /> </li>
<li><b>Int8 As:</b> Define what datatype to report int8 columns as.<br /> </li>
projects / psqlodbc.git / commitdiff