[Sommaire] [Imprimer]

   1  <?xml version="1.0" encoding="ISO-8859-1"?>
   2  <!-- ***** BEGIN LICENSE BLOCK *****
   3     - This file is part of DotClear.
   4     - Copyright (c) 2004-2005 Olivier Meunier and contributors. All rights
   5     - reserved.
   6     -
   7     - DotClear is free software; you can redistribute it and/or modify
   8     - it under the terms of the GNU General Public License as published by
   9     - the Free Software Foundation; either version 2 of the License, or
  10     - (at your option) any later version.
  11     -
  12     - DotClear is distributed in the hope that it will be useful,
  13     - but WITHOUT ANY WARRANTY; without even the implied warranty of
  14     - MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  15     - GNU General Public License for more details.
  16     -
  17     - You should have received a copy of the GNU General Public License
  18     - along with DotClear; if not, write to the Free Software
  19     - Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
  20     -
  21     - ***** END LICENSE BLOCK ***** -->
  22  <html>
  23      <head>
  24          <title>MySQL</title>
  25      </head>
  26  
  27      <body>
  28          <h1>MySQL</h1>
  29  
  30          <h2>Abstract</h2>
  31          <p>The MySQL plugin allows you to perform some maintenance tasks on your
  32          DotClear database through a web interface.</p>
  33  
  34          <p>This release lets you:</p>
  35          <ul>
  36              <li><a href="#optimize">optimize your database</a>,</li>
  37              <li><a href="#backup">backup your database</a> in a SQL script,</li>
  38              <li><a href="#restore">restore your database</a> from a SQL script created by the plugin.</li>
  39          </ul>
  40  
  41          <h2 id="optimize">Optimize</h2>
  42          <p>A MySQL database can be seen as a set of files. Each deletion or modification adds fragmentation to it.</p>
  43          <p>The <strong>Optimize</strong> operation performs an OPTIMIZE TABLE request on every DotClear table in order to compact them.</p>
  44          <p>On most setups, you do not have to use <strong>Optimize</strong> daily.
  45          Even if you often update your posts, it is enough to launch this procedure on a monthly basis.</p>
  46          <p>Such a procedure has no impact whatsoever on your data's integrity. It is totally risk-free.</p>
  47  
  48          <h2 id="backup">backup</h2>
  49          <p>One cannot repeat too often how important it is to make regular backups of your data.<br>With the <strong>Backup</strong> procedure, it has no more reasons to not become an automatism.</p>
  50          <p>This procedure creates a complete "dump" of your DotClear database. We call "dump" a SQL script containing the instructions to recreate your DotClear database.<br>This file is gzip compressed to save space.</p>
  51          <p>Should you wish to do so, this dump still can be used directly in phpMyAdmin.</p>
  52  
  53          <dl>
  54              <dt id="send_it">Immediate download</dt>
  55              <dd>This option allows you to select whether your wish the plug in to save the dump or to download it.<br>The default setting is to have it checked, you directly download the file on your computer and there is no local save on the server.<br>By unselecting it, the file will be saved to a <strong>mysql/</strong>  sub-folder in your DotClear <strong>share/</strong> folder.</dd>
  56          </dl>
  57  
  58          <h2 id="restore">Restore</h2>
  59          <p>It is the opposite of the backup procedure. This one allows you to load a backup file in the eventuality of a problem with your MySQL database.</p>
  60          <p>Hopefully, it should be the less used procedure of this plugin.</p>
  61          <p>The restore runs every SQL request of the dump file. It means that <strong>every piece of data still to be found in your DotClear database will be overwritten</strong>.<br>
  62          The users accounts will be affected too.</p>
  63          <dl>
  64              <dt id="dumpfile">Dumpfile to restore</dt>
  65              <dd>Use the <strong>browse...</strong> button to select, on your hard drive, the SQL dump to restore.</dd>
  66          </dl>
  67  
  68      </body>
  69  </html>