From bd56a73c40bc7636cac242b9286ef1d9fb85b662 Mon Sep 17 00:00:00 2001 From: Hiroshi Inoue Date: Fri, 15 Sep 2006 15:03:34 +0000 Subject: [PATCH] Documentation update. --- docs/config.html | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-) diff --git a/docs/config.html b/docs/config.html index 6d9f6f9..cf0b757 100644 --- a/docs/config.html +++ b/docs/config.html @@ -1,4 +1,4 @@ - +!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> @@ -48,7 +48,11 @@ the old podbc32.
  Log communications to/from the backend to that file. This is good for debugging problems.
  -
  • Parse Statements: If enabled, +
  • Parse Statements: Tell the driver how to gather the information about result columns of queries. See also Disallow Premature and ServerSide Prepare options.
    +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.
    +If neither of them is specified the driver would execute the prepared statement prematurely when the application inquires the result columns' info.

    + +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, @@ -169,6 +173,7 @@ versioning feature to be used.
     
  • Disallow Premature: Mainly for 7.1 to 7.3 servers. Server side prepare is a more preferable option for 7.4+ servers.
    +Tell the driver how to gather the information about result columns. See also Parse Staements and Server Side Prepare options.
    This is an option to compensate for the lack of a server's Prepare functionality. For example, (Middleware) applications issue the following ODBC API calls.

    @@ -199,10 +204,11 @@ immediately.
     
  • True is -1: Represent TRUE as -1 for compatibility with some applications.
     
    • -
  • Server side prepare: Available for 7.3+ servers and recommended for 7.4+.
      -(7.4+) By using extended query protocol the driver replies to the inquiry for the information of columns or parameters correctly and effectively.
      -(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
      -doesn't need to re-parse the statement each time it is used.
     
    • +
  • Server side prepare: Applicable for 7.3+ servers and recommended for 7.4+.
      +(7.4+) Tell the driver how to gather the information about result columns. See also Parse Statement and Disallow Premature options.
            By using extended query protocol the driver replies to the inquiry correctly and effectively.
      +(7.4+) By using extended query protocol the driver replies to the inquiry for the information of parameters.
      +(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
    +        doesn't need to re-parse the statement each time it is used.
     
  • Int8 As: Define what datatype to report int8 columns as.
     
    • -- 2.39.5