diff options
| author | Charles Cabergs <me@cacharle.xyz> | 2020-07-27 10:05:23 +0200 |
|---|---|---|
| committer | Charles Cabergs <me@cacharle.xyz> | 2020-07-27 10:05:23 +0200 |
| commit | 5bf66662a9bdd62c5bccab15e607cd95cfb8fcab (patch) | |
| tree | 39a1a4629749056191c05dfd899f931701b7acf3 /srcs/phpmyadmin/vendor/williamdes/mariadb-mysql-kbs/test/data | |
| parent | 5afd237bbd22028b85532b8c0b3fcead49a00764 (diff) | |
| download | ft_server-5bf66662a9bdd62c5bccab15e607cd95cfb8fcab.tar.gz ft_server-5bf66662a9bdd62c5bccab15e607cd95cfb8fcab.tar.bz2 ft_server-5bf66662a9bdd62c5bccab15e607cd95cfb8fcab.zip | |
Removed wordpress and phpmyadmin, my server doesn't handle it well and it brings shame on my famillyHEADmaster
Diffstat (limited to 'srcs/phpmyadmin/vendor/williamdes/mariadb-mysql-kbs/test/data')
4 files changed, 0 insertions, 1836 deletions
diff --git a/srcs/phpmyadmin/vendor/williamdes/mariadb-mysql-kbs/test/data/mysql_test_case_1.html b/srcs/phpmyadmin/vendor/williamdes/mariadb-mysql-kbs/test/data/mysql_test_case_1.html deleted file mode 100644 index 5855c10..0000000 --- a/srcs/phpmyadmin/vendor/williamdes/mariadb-mysql-kbs/test/data/mysql_test_case_1.html +++ /dev/null @@ -1,235 +0,0 @@ -<html> - -<div class="itemizedlist"> - <ul class="itemizedlist" style="list-style-type: disc; "> - <li class="listitem"> - <p><a name="option_mysqld_ndbcluster"></a> - <a class="indexterm" name="idm139716308207376"></a> - - <a class="indexterm" name="idm139716308205888"></a> - - <a class="link" href="mysql-cluster-options-variables.html#option_mysqld_ndbcluster"><code - class="option">--ndbcluster</code></a> - </p> - <div class="table"> - <a name="ndbcluster-detailtable"></a> - <p class="title"><b>Table 21.207 - Type and value information for ndbcluster</b></p> - <div class="table-contents"> - <table> - <colgroup> - <col width="35%"> - <col width="65%"> - </colgroup> - <thead> - <tr> - <th scope="col">Property</th> - <th scope="col">Value</th> - </tr> - </thead> - <tbody> - <tr> - <td scope="row">Name</td> - <td><code - class="literal"><a class="link" href="mysql-cluster-options-variables.html#option_mysqld_ndbcluster">ndbcluster</a></code> - </td> - </tr> - <tr> - <td scope="row">Command Line</td> - <td>Yes</td> - </tr> - <tr> - <td scope="row">System Variable</td> - <td>No</td> - </tr> - <tr> - <td scope="row">Status Variable</td> - <td>No</td> - </tr> - <tr> - <td scope="row">Option File</td> - <td>Yes</td> - </tr> - <tr> - <td scope="row">Scope</td> - <td></td> - </tr> - <tr> - <td scope="row">Dynamic</td> - <td>No</td> - </tr> - <tr> - <td scope="row">Type</td> - <td></td> - </tr> - <tr> - <td scope="row">Default, Range</td> - <td>FALSE (Version: NDB 7.5-7.6)</td> - </tr> - <tr> - <td scope="row">Notes</td> - <td> - <p> - DESCRIPTION: Enable NDB Cluster (if this version - of MySQL supports it) - </p> - <p> - Disabled by - <a class="link" - href="mysql-cluster-options-variables.html#option_mysqld_skip-ndbcluster"><code - class="option">--skip-ndbcluster</code></a>. - </p> - </td> - </tr> - </tbody> - </table> - </div> - <div class="table-contents"> - <table cellpadding="0" cellspacing="0" - style="position: fixed; top: 0px; display: none; left: 431px; width: 705px;"> - <thead> - <tr> - <th scope="col" style="width: 247px;">Property</th> - <th scope="col" style="width: 457px;">Value</th> - </tr> - </thead> - </table> - </div> - - </div> - <br class="table-break"> - <p> - The <a class="link" href="mysql-cluster.html" - title="Chapter 21 MySQL NDB Cluster 7.5 and NDB Cluster 7.6"><code - class="literal">NDBCLUSTER</code></a> storage engine - is necessary for using NDB Cluster. If a - <a class="link" href="mysqld.html" title="4.3.1 mysqld — The MySQL Server"><span - class="command"><strong>mysqld</strong></span></a> binary includes support for the - <a class="link" href="mysql-cluster.html" - title="Chapter 21 MySQL NDB Cluster 7.5 and NDB Cluster 7.6"><code - class="literal">NDBCLUSTER</code></a> storage engine, - the engine is disabled by default. Use the - <a class="link" href="mysql-cluster-options-variables.html#option_mysqld_ndbcluster"><code - class="option">--ndbcluster</code></a> option to - enable it. Use <code class="option">--skip-ndbcluster</code> to - explicitly disable the engine. - </p> - <p> - It is not necessary or desirable to use this option - together with <a class="link" href="server-options.html#option_mysqld_initialize"><code - class="option">--initialize</code></a>. - Beginning with NDB 7.5.4, <code class="option">--ndbcluster</code> is - ignored (and the <code class="literal">NDB</code> storage engine is - <span class="emphasis"><em>not</em></span> enabled) if - <code class="option">--initialize</code> is also used. (Bug #81689, - Bug #23518923) - </p> - </li> - <li class="listitem"> - <p><a name="option_mysqld_ndb-allow-copying-alter-table"></a> - <a class="indexterm" name="idm139716308160304"></a> - - <a class="indexterm" name="idm139716308158800"></a> - - <code class="option">--ndb-allow-copying-alter-table=[ON|OFF]</code> - </p> - <div class="table"> - <a name="ndb-allow-copying-alter-table-detailtable"></a> - <p class="title"><b>Table 21.208 - Type and value information for ndb-allow-copying-alter-table</b></p> - <div class="table-contents"> - <table> - <colgroup> - <col width="35%"> - <col width="65%"> - </colgroup> - <thead> - <tr> - <th scope="col">Property</th> - <th scope="col">Value</th> - </tr> - </thead> - <tbody> - <tr> - <td scope="row">Name</td> - <td><code - class="literal"><a class="link" href="mysql-cluster-options-variables.html#option_mysqld_ndb-allow-copying-alter-table">ndb-allow-copying-alter-table</a></code> - </td> - </tr> - <tr> - <td scope="row">Command Line</td> - <td>Yes</td> - </tr> - <tr> - <td scope="row">System Variable</td> - <td>Yes</td> - </tr> - <tr> - <td scope="row">Status Variable</td> - <td>No</td> - </tr> - <tr> - <td scope="row">Option File</td> - <td>Yes</td> - </tr> - <tr> - <td scope="row">Scope</td> - <td>Both</td> - </tr> - <tr> - <td scope="row">Dynamic</td> - <td>Yes</td> - </tr> - <tr> - <td scope="row">Type</td> - <td></td> - </tr> - <tr> - <td scope="row">Default, Range</td> - <td>ON (Version: NDB 7.5-7.6)</td> - </tr> - <tr> - <td scope="row">Notes</td> - <td> - <p> - DESCRIPTION: Set to OFF to keep ALTER TABLE from - using copying operations on NDB tables - </p> - </td> - </tr> - </tbody> - </table> - </div> - <div class="table-contents"> - <table cellpadding="0" cellspacing="0" - style="position: fixed; top: 0px; display: none; left: 431px; width: 911px;"> - <thead> - <tr> - <th scope="col" style="width: 319px;">Property</th> - <th scope="col" style="width: 591px;">Value</th> - </tr> - </thead> - </table> - </div> - - </div> - <br class="table-break"> - <p> - Let <a class="link" href="alter-table.html" title="13.1.8 ALTER TABLE Syntax"><code - class="literal">ALTER TABLE</code></a> and other - DDL statements use copying operations on - <code class="literal">NDB</code> tables. Set to - <code class="literal">OFF</code> to keep this from happening; doing - so may improve performance of critical applications. - </p> - </li> - <li class="listitem"> - <p><a name="option_mysqld_ndb-batch-size"></a> - <a class="indexterm" name="idm139716308121008"></a> - - <a class="indexterm" name="idm139716308119520"></a> - - <code class="option">--ndb-batch-size=<em class="replaceable"><code>#</code></em></code> - </p> - -</html> diff --git a/srcs/phpmyadmin/vendor/williamdes/mariadb-mysql-kbs/test/data/mysql_test_case_2.html b/srcs/phpmyadmin/vendor/williamdes/mariadb-mysql-kbs/test/data/mysql_test_case_2.html deleted file mode 100644 index 2c3c1c5..0000000 --- a/srcs/phpmyadmin/vendor/williamdes/mariadb-mysql-kbs/test/data/mysql_test_case_2.html +++ /dev/null @@ -1,1211 +0,0 @@ -<html> -<div class="itemizedlist"> - <ul class="itemizedlist" style="list-style-type: disc; "> - <li class="listitem"> - <p><a name="sysvar_binlog_gtid_simple_recovery"></a> - <a class="indexterm" name="idm140532554077552"></a> - - <a class="indexterm" name="idm140532554076512"></a> - - <a class="link" href="replication-options-gtids.html#sysvar_binlog_gtid_simple_recovery"><code - class="literal">binlog_gtid_simple_recovery</code></a> - </p> - <div class="informaltable"> - <table frame="box" rules="all" summary="Properties for binlog_gtid_simple_recovery"> - <colgroup> - <col width="30%"> - <col width="70%"> - </colgroup> - <thead> - <tr> - <th scope="col">Property</th> - <th scope="col">Value</th> - </tr> - </thead> - <tbody> - <tr> - <td scope="row"><span class="bold"><strong>Command-Line Format</strong></span></td> - <td><code class="literal">--binlog-gtid-simple-recovery[={OFF|ON}]</code></td> - </tr> - <tr> - <td scope="row"><span class="bold"><strong>System Variable</strong></span></td> - <td><code - class="literal"><a class="link" href="replication-options-gtids.html#sysvar_binlog_gtid_simple_recovery">binlog_gtid_simple_recovery</a></code> - </td> - </tr> - <tr> - <td scope="row"><span class="bold"><strong>Scope</strong></span></td> - <td>Global</td> - </tr> - <tr> - <td scope="row"><span class="bold"><strong>Dynamic</strong></span></td> - <td>No</td> - </tr> - <tr> - <td scope="row"><span class="bold"><strong><a class="link" - href="optimizer-hints.html#optimizer-hints-set-var" - title="Variable-Setting Hint Syntax"><code - class="literal">SET_VAR</code></a> Hint Applies</strong></span></td> - <td>No</td> - </tr> - <tr> - <td scope="row"><span class="bold"><strong>Type</strong></span></td> - <td>Boolean</td> - </tr> - <tr> - <td scope="row"><span class="bold"><strong>Default Value</strong></span></td> - <td><code class="literal">ON</code></td> - </tr> - </tbody> - </table> - </div> - <p> - This variable controls how binary log files are iterated - during the search for GTIDs when MySQL starts or restarts. - </p> - <p> - When - <a class="link" href="replication-options-gtids.html#sysvar_binlog_gtid_simple_recovery"><code - class="literal">binlog_gtid_simple_recovery=TRUE</code></a>, - which is the default in MySQL 8.0, the values of - <a class="link" href="replication-options-gtids.html#sysvar_gtid_executed"><code - class="literal">gtid_executed</code></a> and - <a class="link" href="replication-options-gtids.html#sysvar_gtid_purged"><code - class="literal">gtid_purged</code></a> are computed at - startup based on the values of - <code class="literal">Previous_gtids_log_event</code> in the most recent - and oldest binary log files. For a description of the - computation, see - <a class="xref" href="replication-gtids-lifecycle.html#replication-gtids-gtid-purged" - title="The gtid_purged System Variable">The <code class="literal">gtid_purged</code> System - Variable</a>. This setting - accesses only two binary log files during server restart. If - all binary logs on the server were generated using MySQL 5.7.8 - or later, - <a class="link" href="replication-options-gtids.html#sysvar_binlog_gtid_simple_recovery"><code - class="literal">binlog_gtid_simple_recovery=TRUE</code></a> - can always safely be used. - - - </p> - <p> - If any binary logs from MySQL 5.7.7 or older are present on - the server (for example, following an upgrade of an older - server to MySQL 8.0), with - <a class="link" href="replication-options-gtids.html#sysvar_binlog_gtid_simple_recovery"><code - class="literal">binlog_gtid_simple_recovery=TRUE</code></a>, - <a class="link" href="replication-options-gtids.html#sysvar_gtid_executed"><code - class="literal">gtid_executed</code></a> and - <a class="link" href="replication-options-gtids.html#sysvar_gtid_purged"><code - class="literal">gtid_purged</code></a> might be - initialized incorrectly in the following two situations: - </p> - <div class="itemizedlist"> - <ul class="itemizedlist" style="list-style-type: circle; "> - <li class="listitem"> - <p> - The newest binary log was generated by MySQL 5.7.5 or - earlier, and <a class="link" href="replication-options-gtids.html#sysvar_gtid_mode"><code - class="literal">gtid_mode</code></a> - was <code class="literal">ON</code> for some binary logs but - <code class="literal">OFF</code> for the newest binary log. - </p> - </li> - <li class="listitem"> - <p> - A <code class="literal">SET @@GLOBAL.gtid_purged</code> statement - was issued on MySQL 5.7.7 or earlier, and the binary log - that was active at the time of the <code class="literal">SET - @@GLOBAL.gtid_purged</code> statement has not yet been - purged. - - - </p> - </li> - </ul> - </div> - <p> - If an incorrect GTID set is computed in either situation, it - will remain incorrect even if the server is later restarted - with - <a class="link" href="replication-options-gtids.html#sysvar_binlog_gtid_simple_recovery"><code - class="literal">binlog_gtid_simple_recovery=FALSE</code></a>. - If either of these situations apply or might apply on the - server, set - <a class="link" href="replication-options-gtids.html#sysvar_binlog_gtid_simple_recovery"><code - class="literal">binlog_gtid_simple_recovery=FALSE</code></a> - before starting or restarting the server. - </p> - <p> - When - <a class="link" href="replication-options-gtids.html#sysvar_binlog_gtid_simple_recovery"><code - class="literal">binlog_gtid_simple_recovery=FALSE</code></a> - is set, the method of computing - <a class="link" href="replication-options-gtids.html#sysvar_gtid_executed"><code - class="literal">gtid_executed</code></a> and - <a class="link" href="replication-options-gtids.html#sysvar_gtid_purged"><code - class="literal">gtid_purged</code></a> as described in - <a class="xref" href="replication-gtids-lifecycle.html#replication-gtids-gtid-purged" - title="The gtid_purged System Variable">The <code class="literal">gtid_purged</code> System - Variable</a> is changed to - iterate the binary log files as follows: - </p> - <div class="itemizedlist"> - <ul class="itemizedlist" style="list-style-type: circle; "> - <li class="listitem"> - <p> - Instead of using the value of - <code class="literal">Previous_gtids_log_event</code> and GTID log - events from the newest binary log file, the computation - for <a class="link" href="replication-options-gtids.html#sysvar_gtid_executed"><code - class="literal">gtid_executed</code></a> - iterates from the newest binary log file, and uses the - value of <code class="literal">Previous_gtids_log_event</code> and - any GTID log events from the first binary log file where - it finds a <code class="literal">Previous_gtids_log_event</code> - value. If the server's most recent binary log files do not - have GTID log events, for example if - <a class="link" href="replication-options-gtids.html#sysvar_gtid_mode"><code - class="literal">gtid_mode=ON</code></a> was used but - the server was later changed to - <a class="link" href="replication-options-gtids.html#sysvar_gtid_mode"><code - class="literal">gtid_mode=OFF</code></a>, this - process can take a long time. - </p> - </li> - <li class="listitem"> - <p> - Instead of using the value of - <code class="literal">Previous_gtids_log_event</code> from the - oldest binary log file, the computation for - <a class="link" href="replication-options-gtids.html#sysvar_gtid_purged"><code - class="literal">gtid_purged</code></a> iterates from - the oldest binary log file, and uses the value of - <code class="literal">Previous_gtids_log_event</code> from the first - binary log file where it finds either a nonempty - <code class="literal">Previous_gtids_log_event</code> value, or at - least one GTID log event (indicating that the use of GTIDs - starts at that point). If the server's older binary log - files do not have GTID log events, for example if - <a class="link" href="replication-options-gtids.html#sysvar_gtid_mode"><code - class="literal">gtid_mode=ON</code></a> was only set - recently on the server, this process can take a long time. - </p> - </li> - </ul> - </div> - </li> - <li class="listitem"> - <p><a name="sysvar_enforce_gtid_consistency"></a> - <a class="link" href="replication-options-gtids.html#sysvar_enforce_gtid_consistency"><code - class="literal">enforce_gtid_consistency</code></a> - </p><a class="indexterm" name="idm140532554003024"></a><a class="indexterm" name="idm140532554001920"></a> - <div class="informaltable"> - <table frame="box" rules="all" summary="Properties for enforce_gtid_consistency"> - <colgroup> - <col width="30%"> - <col width="70%"> - </colgroup> - <thead> - <tr> - <th scope="col">Property</th> - <th scope="col">Value</th> - </tr> - </thead> - <tbody> - <tr> - <td scope="row"><span class="bold"><strong>Command-Line Format</strong></span></td> - <td><code class="literal">--enforce-gtid-consistency[=value]</code></td> - </tr> - <tr> - <td scope="row"><span class="bold"><strong>System Variable</strong></span></td> - <td><code - class="literal"><a class="link" href="replication-options-gtids.html#sysvar_enforce_gtid_consistency">enforce_gtid_consistency</a></code> - </td> - </tr> - <tr> - <td scope="row"><span class="bold"><strong>Scope</strong></span></td> - <td>Global</td> - </tr> - <tr> - <td scope="row"><span class="bold"><strong>Dynamic</strong></span></td> - <td>Yes</td> - </tr> - <tr> - <td scope="row"><span class="bold"><strong><a class="link" - href="optimizer-hints.html#optimizer-hints-set-var" - title="Variable-Setting Hint Syntax"><code - class="literal">SET_VAR</code></a> Hint Applies</strong></span></td> - <td>No</td> - </tr> - <tr> - <td scope="row"><span class="bold"><strong>Type</strong></span></td> - <td>Enumeration</td> - </tr> - <tr> - <td scope="row"><span class="bold"><strong>Default Value</strong></span></td> - <td><code class="literal">OFF</code></td> - </tr> - <tr> - <td scope="row"><span class="bold"><strong>Valid Values</strong></span></td> - <td> - <p class="valid-value"><code class="literal">OFF</code></p> - <p class="valid-value"><code class="literal">ON</code></p> - <p class="valid-value"><code class="literal">WARN</code></p> - </td> - </tr> - </tbody> - </table> - </div> - <p> - Depending on the value of this variable, the server enforces - GTID consistency by allowing execution of only statements that - can be safely logged using a GTID. You - <span class="emphasis"><em>must</em></span> set this variable to - <code class="literal">ON</code> before enabling GTID based replication. - </p> - <p> - The values that - <a class="link" href="replication-options-gtids.html#sysvar_enforce_gtid_consistency"><code - class="literal">enforce_gtid_consistency</code></a> can - be configured to are: - </p> - <div class="itemizedlist"> - <ul class="itemizedlist" style="list-style-type: circle; "> - <li class="listitem"> - <p> - <code class="literal">OFF</code>: all transactions are allowed to - violate GTID consistency. - </p> - </li> - <li class="listitem"> - <p> - <code class="literal">ON</code>: no transaction is allowed to - violate GTID consistency. - </p> - </li> - <li class="listitem"> - <p> - <code class="literal">WARN</code>: all transactions are allowed to - violate GTID consistency, but a warning is generated in - this case. - </p> - </li> - </ul> - </div> - <p> - Only statements that can be logged using GTID safe statements - can be logged when - <a class="link" href="replication-options-gtids.html#sysvar_enforce_gtid_consistency"><code - class="literal">enforce_gtid_consistency</code></a> is - set to <code class="literal">ON</code>, so the operations listed here - cannot be used with this option: - </p> - <div class="itemizedlist"> - <ul class="itemizedlist" style="list-style-type: circle; "> - <li class="listitem"> - <p> - <a class="link" href="create-table-select.html" - title="13.1.20.5 CREATE TABLE ... SELECT Syntax"><code class="literal">CREATE - TABLE ... SELECT</code></a> statements - </p> - </li> - <li class="listitem"> - <p> - <a class="link" href="create-table.html" title="13.1.20 CREATE TABLE Syntax"><code - class="literal">CREATE - TEMPORARY TABLE</code></a> or - <a class="link" href="drop-table.html" title="13.1.32 DROP TABLE Syntax"><code - class="literal">DROP TEMPORARY - TABLE</code></a> statements inside transactions - </p> - </li> - <li class="listitem"> - <p> - Transactions or statements that update both transactional - and nontransactional tables. There is an exception that - nontransactional DML is allowed in the same transaction or - in the same statement as transactional DML, if all - <span class="emphasis"><em>nontransactional</em></span> tables are - temporary. - </p> - </li> - </ul> - </div> - <p> - <a class="link" href="replication-options-gtids.html#sysvar_enforce_gtid_consistency"><code - class="option">--enforce-gtid-consistency</code></a> only - takes effect if binary logging takes place for a statement. If - binary logging is disabled on the server, or if statements are - not written to the binary log because they are removed by a - filter, GTID consistency is not checked or enforced for the - statements that are not logged. - </p> - <p> - For more information, see - <a class="xref" href="replication-gtids-restrictions.html" - title="17.1.3.6 Restrictions on Replication with GTIDs">Section 17.1.3.6, “Restrictions on - Replication with GTIDs”</a>. - </p> - <p> - Prior to MySQL 5.7 and in early releases in that release - series, the boolean - <a class="link" href="replication-options-gtids.html#sysvar_enforce_gtid_consistency"><code - class="literal">enforce_gtid_consistency</code></a> - defaulted to <code class="literal">OFF</code>. To maintain compatibility - with these earlier releases, the enumeration defaults to - <code class="literal">OFF</code>, and setting - <a class="link" href="replication-options-gtids.html#sysvar_enforce_gtid_consistency"><code - class="option">--enforce-gtid-consistency</code></a> - without a value is interpreted as setting the value to - <code class="literal">ON</code>. The variable also has multiple textual - aliases for the values: <code class="literal">0=OFF=FALSE</code>, - <code class="literal">1=ON=TRUE</code>,<code class="literal">2=WARN</code>. This - differs from other enumeration types but maintains - compatibility with the boolean type used in previous releases. - These changes impact on what is returned by the variable. - Using <code class="literal">SELECT @@ENFORCE_GTID_CONSISTENCY</code>, - <code class="literal">SHOW VARIABLES LIKE - 'ENFORCE_GTID_CONSISTENCY'</code>, and <code class="literal">SELECT * - FROM INFORMATION_SCHEMA.VARIABLES WHERE 'VARIABLE_NAME' = - 'ENFORCE_GTID_CONSISTENCY'</code>, all return the textual - form, not the numeric form. This is an incompatible change, - since <code class="literal">@@ENFORCE_GTID_CONSISTENCY</code> returns - the numeric form for booleans but returns the textual form for - <code class="literal">SHOW</code> and the Information Schema. - </p> - </li> - <li class="listitem"> - <p><a name="sysvar_gtid_executed"></a> - <a class="indexterm" name="idm140532553933872"></a> - - <a class="indexterm" name="idm140532553932816"></a> - - <a class="link" href="replication-options-gtids.html#sysvar_gtid_executed"><code - class="literal">gtid_executed</code></a> - </p> - <div class="informaltable"> - <table frame="box" rules="all" summary="Properties for gtid_executed"> - <colgroup> - <col width="30%"> - <col width="70%"> - </colgroup> - <thead> - <tr> - <th scope="col">Property</th> - <th scope="col">Value</th> - </tr> - </thead> - <tbody& |