autodoc.git / traditional.xml

version» Context lines:

autodoc.git/traditional.xml:1:   <?xml version='1.0' encoding='utf-8'?> - <manual time-stamp='2020-02-28' version='Pike v8.0.967'> + <manual time-stamp='2020-03-06' version='Pike v8.0.969'>    <dir name='./traditional_manual'>    <file name='./traditional_manual/index.html'>    <chapter title='Table of Contents' unnumbered='1'>    <dl><dt><url href='index.html'>Table of Contents</url></dt>   <dt><url href='chapter_1.html'>1. Introduction</url></dt>   <dd><url href='chapter_1.html#1.1'>1.1. Overview</url></dd>   <dd><url href='chapter_1.html#1.2'>1.2. The history of Pike</url></dd>   <dd><url href='chapter_1.html#1.3'>1.3. A comparison with other languages</url></dd>   <dd><url href='chapter_1.html#1.4'>1.4. What is Pike</url></dd>   <dd><url href='chapter_1.html#1.5'>1.5. Pike License</url></dd>
autodoc.git/traditional.xml:42692:   </text></group><group><member><type><int/></type><index>"text_query"</index></member><text><p>Send queries to and retrieve results from the database using text    instead of the, generally more efficient, default native binary method.    Turning this on will allow multiple statements per query separated    by semicolons (not recommended).</p>   </text></group><group><member><type><int/></type><index>"sync_parse"</index></member><text><p>Set it to zero to turn synchronous parsing off for statements.    Setting this to off can cause surprises because statements could    be parsed before the previous statements have been executed    (e.g. references to temporary tables created in the preceding    statement),    but it can speed up parsing due to increased parallelism.</p> - </text></group><group><member><type><int/></type><index>"cache_autoprepared_statements"</index></member><text><p>If set to zero, it disables the automatic statement prepare and + </text></group><group><member><type><int/></type><index>"cache_autoprepared_statements"</index></member><text><p>If set to one, it enables the automatic statement prepare and    cache logic; caching prepared statements can be problematic    when stored procedures and tables are redefined which leave stale -  references in the already cached prepared statements.</p> +  references in the already cached prepared statements. +  The default is off, because PostgreSQL 10.1 (at least) +  has a bug that makes it spike to 100% CPU sometimes when this is on.</p>   </text></group><group><member><type><string/></type><index>"client_encoding"</index></member><text><p>Character encoding for the client side, it defaults to using    the default encoding specified by the database, e.g.    <expr>"UTF8"</expr> or <expr>"SQL_ASCII"</expr>.</p>   </text></group><group><member><type><string/></type><index>"standard_conforming_strings"</index></member><text><p>When on, backslashes in strings must not be escaped any longer,    <ref resolved='predef::Sql.pgsql.quote'>quote()</ref> automatically adjusts quoting strategy accordingly.</p>   </text></group><group><member><type><string/></type><index>"escape_string_warning"</index></member><text><p>When on, a warning is issued if a backslash (\) appears in an    ordinary string literal and <expr>"standard_conforming_strings"</expr>    is off, defaults to on.</p>   </text></group></mapping><p>For the numerous other options please check the PostgreSQL manual.</p>   </text></group><group><note/><text><p>You need to have a database selected before using the SQL-object,