forgot to commit changelog...
[phpmyadmin/last10db.git] / Documentation.html
blobb8717c759fa817144cf22868ea5122d8fd73c0ad
1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
2 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en-US"
4 version="-//W3C//DTD XHTML 1.1//EN" dir="ltr">
5 <!-- $Id$ -->
6 <!--
7 vim: expandtab ts=4 sw=4 sts=4 tw=78
8 -->
10 <head>
11 <link rel="icon" href="./favicon.ico" type="image/x-icon" />
12 <link rel="shortcut icon" href="./favicon.ico" type="image/x-icon" />
13 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
14 <title>phpMyAdmin 2.10.0-dev - Documentation</title>
15 <link rel="stylesheet" type="text/css" href="docs.css" />
16 </head>
18 <body id="top">
20 <!-- TOP MENU -->
21 <ul class="header">
22 <li><a href="#top">Top</a></li>
23 <li><a href="#require">Requirements</a></li>
24 <li><a href="#intro">Introduction</a></li>
25 <li><a href="#setup">Installation</a></li>
26 <li><a href="#setup_script">Setup script</a></li>
27 <li><a href="#config">Configuration</a></li>
28 <li><a href="#transformations">Transformations</a></li>
29 <li><a href="#faq"><abbr title="Frequently Asked Questions">FAQ</abbr></a></li>
30 <li><a href="#developers">Developers</a></li>
31 <li><a href="#credits">Credits</a></li>
32 <li><a href="translators.html">Translators</a></li>
33 <li><a href="#glossary">Glossary</a></li>
34 </ul>
36 <h1>phpMyAdmin 2.10.0-dev Documentation</h1>
38 <ul><li><a href="http://www.phpmyadmin.net/">
39 phpMyAdmin homepage</a></li>
40 <li><a href="https://sf.net/projects/phpmyadmin/">
41 SourceForge phpMyAdmin project page</a></li>
42 <li>Local documents:
43 <ul><li>Version history: <a href="changelog.php">ChangeLog</a></li>
44 <li>General notes: <a href="readme.php">README</a></li>
45 <li>License: <a href="license.php">LICENSE</a></li>
46 </ul>
47 </li>
48 <li>Documentation version:
49 <i>$Id$</i>
50 </li>
51 </ul>
53 <!-- REQUIREMENTS -->
54 <h2 id="require">Requirements</h2>
56 <ul><li><b>PHP</b>
57 <ul><li>You need PHP 4.1.0 or newer, with <tt>session</tt> support
58 (<a href="#faq1_31">see
59 <abbr title="Frequently Asked Questions">FAQ</abbr> 1.31</a>)
60 </li>
61 <li>You need GD2 support in PHP to display inline
62 thumbnails of JPEGs (&quot;image/jpeg: inline&quot;) with their
63 original aspect ratio</li>
64 <li>You need PHP 4.3.0 or newer to use the
65 &quot;text/plain: external&quot; MIME-based transformation</li>
66 </ul>
67 </li>
68 <li><b>MySQL</b> 3.23.32 or newer (<a href="#faq1_17">details</a>);</li>
69 <li>Not really a requirement but a <b>strong suggestion</b>: if you are using
70 the &quot;cookie&quot; authentication method, having the <tt>mcrypt</tt>
71 PHP extension on your web server accelerates not only the login
72 phase but every other action that you do in phpMyAdmin.</li>
73 <li><b>Web browser</b> with cookies enabled.</li>
74 </ul>
76 <!-- INTRODUCTION -->
77 <h2 id="intro">Introduction</h2>
79 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
80 a single database. To accomplish the latter you'll need a properly set up
81 MySQL user who can read/write only the desired database. It's up to you to
82 look up the appropriate part in the MySQL manual.
83 </p>
85 <h3>Currently phpMyAdmin can:</h3>
87 <ul><li>browse and drop databases, tables, views, fields and indexes</li>
88 <li>create, copy, drop, rename and alter databases, tables, fields and
89 indexes</li>
90 <li>maintenance server, databases and tables, with proposals on server
91 configuration</li>
92 <li>execute, edit and bookmark any
93 <abbr title="structured query language">SQL</abbr>-statement, even
94 batch-queries</li>
95 <li>load text files into tables</li>
96 <li>create<a href="#footnote_1"><sup>1</sup></a> and read dumps of tables
97 </li>
98 <li>export<a href="#footnote_1"><sup>1</sup></a> data to various formats:
99 <abbr title="comma separated values">CSV</abbr>,
100 <abbr title="Extensible Markup Language">XML</abbr>,
101 <abbr title="Portable Document Format">PDF</abbr>,
102 <abbr title="International Standards Organisation">ISO</abbr>/<abbr
103 title="International Electrotechnical Commission">IEC</abbr> 26300 -
104 OpenDocument Text and Spreadsheet,
105 <abbr title="Microsoft Word 2000">Word</abbr>,
106 <abbr title="Microsoft Excel 2000">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
107 </li>
108 <li>administer multiple servers</li>
109 <li>manage MySQL users and privileges</li>
110 <li>check referential integrity in MyISAM tables</li>
111 <li>using Query-by-example (QBE), create complex queries automatically
112 connecting required tables</li>
113 <li>create <abbr title="Portable Document Format">PDF</abbr> graphics of
114 your Database layout</li>
115 <li>search globally in a database or a subset of it</li>
116 <li>transform stored data into any format using a set of predefined
117 functions, like displaying BLOB-data as image or download-link
118 </li>
119 <li>support InnoDB tables and foreign keys <a href="#faq3_6">(see
120 <abbr title="Frequently Asked Questions">FAQ</abbr> 3.6)</a></li>
121 <li>support mysqli, the improved MySQL extension <a href="#faq1_17">
122 (see <abbr title="Frequently Asked Questions">FAQ</abbr> 1.17)</a></li>
123 <li>communicate in <a href="./translators.html">50 different languages</a>
124 </li>
125 </ul>
127 <h4>A word about users:</h4>
128 <p> Many people have difficulty
129 understanding the concept of user management with regards to phpMyAdmin. When
130 a user logs in to phpMyAdmin, that username and password are passed directly
131 to MySQL. phpMyAdmin does no account management on its own (other than
132 allowing one to manipulate the MySQL user account information); all users
133 must be valid MySQL users.</p>
135 <p class="footnote" id="footnote_1">
136 <sup>1)</sup> phpMyAdmin can compress (Zip, GZip -RFC 1952- or Bzip2 formats)
137 dumps and <abbr title="comma seperated values">CSV</abbr> exports if you use
138 PHP with Zlib support (<tt>--with-zlib</tt>) and/or Bzip2 support
139 (<tt>--with-bz2</tt>). Proper support may also need changes in
140 <tt>php.ini</tt>.</p>
142 <!-- INSTALLATION -->
143 <h2 id="setup">Installation</h2>
145 <ol><li><a href="#quick_install">Quick Install</a></li>
146 <li><a href="#setup_script">Setup script usage</a></li>
147 <li><a href="#linked-tables">Linked-tables infrastructure</a></li>
148 <li><a href="#upgrading">Upgrading from an older version</a></li>
149 <li><a href="#authentication_modes">Using authentication modes</a></li>
150 </ol>
152 <p class="important">
153 phpMyAdmin does not apply any special security methods to the MySQL database
154 server. It is still the system administrator's job to grant permissions on
155 the MySQL databases properly. phpMyAdmin's &quot;Privileges&quot; page can
156 be used for this.
157 </p>
159 <p class="important">
160 Warning for <acronym title="Apple Macintosh">Mac</acronym> users:<br />
161 if you are on a <acronym title="Apple Macintosh">Mac</acronym>
162 <abbr title="operating system">OS</abbr> version before
163 <abbr title="operating system">OS</abbr> X, StuffIt unstuffs with
164 <acronym title="Apple Macintosh">Mac</acronym> formats.<br />
165 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
166 before uploading them to your server, as PHP seems not to like
167 <acronym title="Apple Macintosh">Mac</acronym>-style end of lines character
168 (&quot;<tt>\r</tt>&quot;).</p>
170 <h3 id="quick_install">Quick Install</h3>
171 <ol><li>Untar or unzip the distribution (be sure to unzip the subdirectories):
172 <tt>tar -xzvf phpMyAdmin_x.x.x.tar.gz</tt> in your webserver's
173 document root. If you don't have direct access to your document root,
174 put the files in a directory on your local machine, and, after step 3,
175 transfer the directory on your web server using, for example, ftp.</li>
176 <li>Ensure that all the scripts have the appropriate owner (if PHP is
177 running in safe mode, having some scripts with an owner different
178 from the owner of other scripts will be a
179 problem). See <a href="#faq4_2">
180 <abbr title="Frequently Asked Questions">FAQ</abbr> 4.2</a> and
181 <a href="#faq1_26"><abbr title="Frequently Asked Questions">FAQ</abbr>
182 1.26</a> for suggestions.</li>
183 <li>Now you must configure your installation. There are two methods that
184 can be used. Traditionally, users have hand-edited a copy of
185 config.inc.php, but now a wizard-style setup script is provided for
186 those who prefer a graphical installation. Creating a config.inc.php is
187 still a quick way to get started and needed for some advanced features.
188 <ul><li>To manually create the file, simply use your text editor to
189 create the file <tt>config.inc.php</tt> (you can copy
190 <tt>config.sample.inc.php</tt> to get minimal configuration
191 file) in the main (top-level) phpMyAdmin directory (the one
192 that contains <tt>index.php</tt>). phpMyAdmin first loads
193 <tt>libraries/config.default.php</tt> and then overrides those
194 values with anything found in <tt>config.inc.php</tt>. If the
195 default value is okay for a particular setting, there is no
196 need to include it in <tt>config.inc.php</tt>. You'll need a
197 few directives to get going, a simple configuration may look
198 like this:
199 <pre>
200 &lt;?php
201 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
203 $i=0;
204 $i++;
205 $cfg['Servers'][$i]['auth_type'] = 'cookie';
206 ?&gt;
207 </pre>
208 Or, if you prefer to not be prompted every time you log in:
209 <pre>
210 &lt;?php
212 $i=0;
213 $i++;
214 $cfg['Servers'][$i]['user'] = 'root';
215 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
216 ?&gt;
217 </pre>
218 For a full explanation of possible configuration values, see the
219 <a href="#config">Configuration Section</a> of this document.</li>
220 <li id="setup_script">Instead of manually editing
221 <tt>config.inc.php</tt>, you can use the
222 <a href="scripts/setup.php">Setup Script</a>. First you must
223 manually create a folder <tt>config</tt> in the phpMyAdmin
224 directory. This is a security measure. On a Linux/Unix system you
225 can use the following commands:
226 <pre>
227 cd phpMyAdmin
228 mkdir config # create directory for saving
229 chmod o+rw config # give it world writable permissions
230 </pre>
231 And to edit an existing configuration, copy it over first:
232 <pre>
233 cp config.inc.php config/ # copy current configuration for editing
234 chmod o+w config/config.inc.php # give it world writable permissions
235 </pre>
236 On other platforms, simply create the folder and ensure that your
237 web server has read and write access to it. <a href="#faq1_26">FAQ
238 1.26</a> can help with this.<br /><br />
240 Next, open <tt><a href="scripts/setup.php">scripts/setup.php</a>
241 </tt>in your browser. Note that <strong>changes are not saved to
242 disk until explicitly choose <tt>Save</tt></strong> from the
243 <i>Configuration</i> area of the screen. Normally the script saves
244 the new config.inc.php to the <tt>config/</tt> directory, but if
245 the webserver does not have the proper permissions you may see the
246 error "Cannot load or save configuration." Ensure that the <tt>
247 config/</tt> directory exists and has the proper permissions -
248 or use the <tt>Download</tt> link to save the config file locally
249 and upload (via FTP or some similar means) to the proper location.<br /><br />
251 Once the file has been saved, it must be moved out of the <tt>
252 config/</tt> directory and the permissions must be reset, again
253 as a security measure:
254 <pre>
255 mv config/config.inc.php . # move file to current directory
256 chmod o-rw config.inc.php # remove world read and write permissions
257 </pre>
258 Now the file is ready to be used. You can choose to review or edit
259 the file with your favorite editor, if you prefer to set some
260 advanced options which the setup script does not provide.</li></ul></li>
261 <li>If you are using the
262 <tt>auth_type</tt> &quot;config&quot;, it is suggested that you
263 protect the phpMyAdmin installation directory because using
264 config does not require a user to
265 enter a password to access the phpMyAdmin installation. Use of an alternate
266 authentication method is recommended, for example with
267 HTTP&#8211;AUTH in a <a href="#glossary"><i>.htaccess</i></a> file or switch to using
268 <tt>auth_type</tt> cookie or http. See the
269 <a href="#faqmultiuser"> multi&#8211;user sub&#8211;section</a> of this
270 <abbr title="Frequently Asked Questions">FAQ</abbr> for additional
271 information, especially <a href="#faq4_4">
272 <abbr title="Frequently Asked Questions">FAQ</abbr> 4.4</a>.</li>
273 <li>Open the <a href="index.php">main phpMyAdmin directory</a>
274 in your browser. phpMyAdmin should now display a welcome screen
275 and your databases, or a login dialog if using
276 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie
277 authentication mode.</li>
278 <li>You should deny access to the <tt>./libraries</tt> subfolder in your
279 webserver configuration. For Apache you can use supplied .htaccess file
280 in that folder, for other webservers, you should configure this yourself.
281 Such configuration prevents from possible path exposure and cross side
282 scripting vulnerabilities that might happen to be found in that code.</li>
283 </ol>
285 <h3 id="linked-tables">Linked-tables infrastructure</h3>
287 <p> For a whole set of new features (bookmarks, comments,
288 <abbr title="structured query language">SQL</abbr>-history,
289 <abbr title="Portable Document Format">PDF</abbr>-generation, field contents
290 transformation, etc.) you need to create a set of special tables. Those
291 tables can be located in your own database, or in a central database for a
292 multi-user installation (this database would then be accessed by the
293 controluser, so no other user should have rights to it).</p>
295 <p> Please look at your <tt>./scripts/</tt> directory, where you should find a
296 file called <i>create_tables.sql</i>. (If you are using a Windows server, pay
297 special attention to <a href="#faq1_23">
298 <abbr title="Frequently Asked Questions">FAQ</abbr> 1.23</a>).</p>
300 <p> If your MySQL server's version is 4.1.2 or later, please use
301 <i>./scripts/create_tables_mysql_4_1_2+.sql</i> instead, for a new
302 installation.</p>
304 <p> If you already had this infrastructure and upgraded to MySQL 4.1.2
305 or later, please use <i>./scripts/upgrade_tables_mysql_4_1_2+.sql</i>.</p>
307 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
308 that you may need special (administrator) privileges to create the database
309 and tables, and that the script may need some tuning, depending on the
310 database name.</p>
312 <p> After having imported the <i>./scripts/create_tables.sql</i> file, you
313 should specify the table names in your <i>./config.inc.php</i> file. The
314 directives used for that can be found in the <a href="#config">Configuration
315 section</a>. You will also need to have a controluser with the proper rights
316 to those tables (see section <a href="#authentication_modes">Using
317 authentication modes</a> below).</p>
319 <h3 id="upgrading">Upgrading from an older version</h3>
321 <p> Simply copy <i>./config.inc.php</i> from your previous installation into the newly
322 unpacked one. Configuration files from very old versions (2.3.0 or older) may
323 require some tweaking as some options have been changed or removed.</p>
325 <p> You should <strong>not</strong> copy <tt>libraries/config.default.php</tt>
326 over <tt>config.inc.php</tt> because the default configuration file
327 is version-specific.</p>
329 <p> If you have upgraded your MySQL server from a version older than 4.1.2 to
330 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
331 you should run the SQL script found in
332 <tt>scripts/upgrade_tables_mysql_4_1_2+.sql</tt>.</p>
334 <h3 id="authentication_modes">Using authentication modes</h3>
336 <ul><li><abbr title="HyperText Transfer Protocol">HTTP</abbr> and cookie
337 authentication modes are recommended in a <b>multi-user environment</b>
338 where you want to give users access to their own database and don't want
339 them to play around with others.<br />
340 Nevertheless be aware that MS Internet Explorer seems to be really buggy
341 about cookies, at least till version 6, and PHP 4.1.1 is also a bit buggy
342 in this area!<br />
343 Even in a <b>single-user environment</b>, you might prefer to use
344 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie mode so
345 that your user/password pair are not in clear in the configuration file.
346 </li>
348 <li><abbr title="HyperText Transfer Protocol">HTTP</abbr> and cookie
349 authentication modes are more secure: the MySQL login information does
350 not need to be set in the phpMyAdmin configuration file (except possibly
351 for the <a href="#controluser">controluser</a>).<br />
352 However, keep in mind that the password travels in plain text, unless
353 you are using the HTTPS protocol.<br />
354 In cookie mode, the password is stored, encrypted with the blowfish
355 algorithm, in a temporary cookie.</li>
357 <li>Note: starting with phpMyAdmin 2.6.1, this section is only applicable if
358 your MySQL server is older than 4.1.2, or is running with
359 <tt>--skip-show-database</tt>.<br /><br />
361 For '<abbr title="HyperText Transfer Protocol">HTTP</abbr>' and 'cookie'
362 modes, phpMyAdmin needs a controluser that has <b>only</b> the
363 <tt>SELECT</tt> privilege on the <i>`mysql`.`user` (all columns except
364 `Password`)</i>, <i>`mysql`.`db` (all columns)</i>, <i>`mysql`.`host`
365 (all columns)</i> and <i>`mysql`.`tables_priv` (all columns except
366 `Grantor` and `Timestamp`)</i> tables.<br /> You must specify the details
367 for the <a href="#controluser">controluser</a> in the <tt>config.inc.php</tt>
368 file under the
369 <tt><a href="#cfg_Servers_controluser" class="configrule">
370 $cfg['Servers'][$i]['controluser']</a></tt> and
371 <tt><a href="#cfg_Servers_controlpass" class="configrule">
372 $cfg['Servers'][$i]['controlpass']</a></tt> settings.<br />
373 The following example assumes you want to use <tt>pma</tt> as the
374 controluser and <tt>pmapass</tt> as the controlpass, but <b>this is
375 only an example: use something else in your file!</b> Input these
376 statements from the phpMyAdmin SQL Query window or mysql command&#8211;line
377 client.<br />
378 Of course you have to replace <tt>localhost</tt> with the webserver's host
379 if it's not the same as the MySQL server's one.
381 <pre>
382 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
383 GRANT SELECT (
384 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
385 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
386 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
387 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
388 Execute_priv, Repl_slave_priv, Repl_client_priv
389 ) ON mysql.user TO 'pma'@'localhost';
390 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
391 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
392 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
393 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
395 If you are using an old MySQL version (below 4.0.2), please replace
396 the first GRANT SELECT query by this one:
398 <pre>
399 GRANT SELECT (
400 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
401 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
402 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv
403 ) ON mysql.user TO 'pma'@'localhost';</pre>
405 ... and if you want to use the many new relation and bookmark features:
407 <pre>
408 GRANT SELECT, INSERT, UPDATE, DELETE ON &lt;pma_db&gt;.* TO 'pma'@'localhost';
409 </pre>
411 (this of course requires that your <a href="#linked-tables">linked-tables
412 infrastructure</a> be set up).<br />
413 Of course, the above queries only work if your MySQL version supports
414 the GRANT command. This is the case since 3.22.11.</li>
416 <li>Then each of the <i>true</i> users should be granted a set of privileges
417 on a set of particular databases. Normally you shouldn't give global
418 privileges to an ordinary user, unless you understand the impact of those
419 privileges (for example, you are creating a superuser).<br />
420 For example, to grant the user <i>real_user</i> with all privileges on
421 the database <i>user_base</i>:<br />
423 <pre>
424 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
425 </pre>
427 What the user may now do is controlled entirely by the MySQL user
428 management system.<br />
429 With <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie
430 authentication mode, you don't need to fill the user/password fields
431 inside the <a href="#cfg_Servers" class="configrule">$cfg['Servers']</a>
432 array.</li>
433 </ul>
435 <h4>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication mode</h4>
437 <ul><li>Uses <abbr title="HyperText Transfer Protocol">HTTP</abbr> Basic authentication
438 method and allows you to log in as any valid MySQL user.</li>
439 <li>Is supported with most PHP configurations. For
440 <abbr title="Internet Information Services">IIS</abbr>
441 (<abbr title="Internet Server Application Programming Interface">ISAPI</abbr>)
442 support using <abbr title="Common Gateway Interface">CGI</abbr> PHP see
443 <a href="#faq1_32"><abbr title="Frequently Asked Questions">FAQ</abbr>
444 1.32</a>, for using with Apache
445 <abbr title="Common Gateway Interface">CGI</abbr> see
446 <a href="#faq1_35"><abbr title="Frequently Asked Questions">FAQ</abbr>
447 1.35</a>.</li>
448 <li>See also <a href="#faq4_4">
449 <abbr title="Frequently Asked Questions">FAQ</abbr> 4.4</a> about not
450 using the <i>.htaccess</i> mechanism along with
451 '<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication
452 mode.</li>
453 </ul>
455 <h4>'cookie' authentication mode</h4>
457 <ul><li>You can use this method as a replacement for the
458 <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication
459 (for example, if you're running
460 <abbr title="Internet Information Services">IIS</abbr>).</li>
461 <li>Obviously, the user must enable cookies in the browser, but this is
462 now a requirement for all authentication modes.</li>
463 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
464 with the same username.</li>
465 <li>If you want to log in to arbitrary server see
466 <a href="#AllowArbitraryServer" class="configrule">
467 $cfg['AllowArbitraryServer']</a> directive.</li>
468 <li>As mentioned in the <a href="#require">requirements</a> section, having
469 the <tt>mcrypt</tt> extension will speed up access considerably, but is
470 not required.</li>
471 </ul>
473 <h4>'config' authentication mode</h4>
475 <ul><li>This mode is the less secure one because it requires you to fill the
476 <a href="#servers_user" class="configrule">
477 $cfg['Servers'][$i]['user']</a> and
478 <a href="#servers_user" class="configrule">
479 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
480 can read your config.inc.php can discover your username and password).
481 <br />
482 But you don't need to setup a &quot;controluser&quot; here: using the
483 <a href="#servers_only_db" class="configrule">
484 $cfg['Servers'][$i]['only_db']</a> might be enough.</li>
485 <li>In the <a href="#faqmultiuser">
486 <abbr title="Internet service provider">ISP</abbr>
487 <abbr title="Frequently Asked Questions">FAQ</abbr></a> section, there
488 is an entry explaining how to protect your configuration file.</li>
489 <li>For additional security in this mode, you may wish to consider the Host
490 authentication
491 <a href="#servers_allowdeny_order" class="configrule">
492 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
493 <a href="#servers_allowdeny_rules" class="configrule">
494 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
495 directives.</li>
496 <li>Unlike cookie and http, does not require a user to log in when first
497 loading the phpMyAdmin site. This is by design but could allow any
498 user to access your installation. Use of some restriction method is
499 suggested, perhaps a <a href="#glossary">.htaccess</a> file with the
500 HTTP-AUTH directive or disallowing incoming HTTP requests at
501 one&#8217;s router or firewall will suffice (both of which
502 are beyond the scope of this manual but easily searchable with Google).</li>
503 </ul>
505 <!-- CONFIGURATION -->
506 <h2 id="config">Configuration</h2>
508 <p> <span class="important">Warning for <acronym title="Apple Macintosh">Mac</acronym>
509 users:</span> PHP does not seem to like
510 <acronym title="Apple Macintosh">Mac</acronym> end of lines character
511 (&quot;<tt>\r</tt>&quot;). So ensure you choose the option that allows to use
512 the *nix end of line character (&quot;<tt>\n</tt>&quot;) in your text editor
513 before saving a script you have modified.</p>
515 <p> <span class="important">Configuration note:</span>
516 Almost all configurable data is placed in <tt>config.inc.php</tt>. If this file
517 does not exist, please refer to the <a href="#setup">Quick install</a>
518 section to create one. This file only needs to contain the parameters you want to
519 change from their corresponding default value in
520 <tt>libraries/config.default.php</tt>.</p>
522 <p> The parameters which relate to design (like colors) are placed in
523 <tt>themes/themename/layout.inc.php</tt>. You might also want to create
524 <i>config.footer.inc.php</i> and <i>config.header.inc.php</i> files to add
525 your site specific code to be included on start and end of each page.</p>
527 <dl><dt id="cfg_PmaAbsoluteUri">$cfg['PmaAbsoluteUri'] string</dt>
528 <dd>Sets here the complete <abbr title="Uniform Resource Locator">URL</abbr>
529 (with full path) to your phpMyAdmin installation's directory.
530 E.g. <tt>http://www.your_web.net/path_to_your_phpMyAdmin_directory/</tt>.
531 Note also that the <abbr title="Uniform Resource Locator">URL</abbr> on
532 some web servers are case&#8211;sensitive.
533 Don&#8217;t forget the trailing slash at the end.<br /><br />
535 Starting with version 2.3.0, it is advisable to try leaving this
536 blank. In most cases phpMyAdmin automatically detects the proper
537 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
538 href="https://sf.net/tracker/index.php?func=detail&amp;aid=1340187&amp;group_id=23067&amp;atid=377409">more info</a>).
539 A good test is to browse a table, edit a row and save it. There should
540 be an error message if phpMyAdmin is having trouble auto&#8211;detecting
541 the correct value. If you get an error that this must be set or if
542 the autodetect code fails to detect your path, please post a bug
543 report on our bug tracker so we can improve the code.</dd>
545 <dt id="cfg_PmaNoRelation_DisableWarning">$cfg['PmaNoRelation_DisableWarning'] boolean</dt>
546 <dd>Starting with version 2.3.0 phpMyAdmin offers a lot of features to work
547 with master / foreign &#8211; tables (see
548 <a href="#pmadb" class="configrule">$cfg['Servers'][$i]['pmadb']</a>).
549 <br />
550 If you tried to set this up and it does not work for you, have a look on
551 the &quot;Structure&quot; page of one database where you would like to
552 use it. You will find a link that will analyze why those features have
553 been disabled.<br />
554 If you do not want to use those features set this variable to
555 <tt>TRUE</tt> to stop this message from appearing.</dd>
557 <dt id="cfg_blowfish_secret">$cfg['blowfish_secret'] string</dt>
558 <dd>The &quot;cookie&quot; auth_type uses blowfish
559 algorithm to encrypt the password.<br />
560 If you are using the &quot;cookie&quot; auth_type, enter here a random
561 passphrase of your choice. It will be used internally by the blowfish
562 algorithm: you won&#8217;t be prompted for this passphrase. The maximum
563 number of characters for this parameter seems to be 46.</dd>
565 <dt id="cfg_Servers">$cfg['Servers'] array</dt>
566 <dd>Since version 1.4.2, phpMyAdmin supports the administration of multiple
567 MySQL servers. Therefore, a
568 <a href="#cfg_Servers" class="configrule">$cfg['Servers']</a>-array has
569 been added which contains the login information for the different servers.
570 The first
571 <a href="#cfg_Servers_host" class="configrule">$cfg['Servers'][$i]['host']</a>
572 contains the hostname of the first server, the second
573 <a href="#cfg_Servers_host" class="configrule">$cfg['Servers'][$i]['host']</a>
574 the hostname of the second server, etc. In
575 <tt>./libraries/config.default.php</tt>, there is only one section for
576 server definition, however you can put as many as you need in
577 <tt>./config.inc.php</tt>, copy that block or needed parts (you don't
578 have to define all settings, just those you need to change).</dd>
580 <dt id="cfg_Servers_host">$cfg['Servers'][$i]['host'] string</dt>
581 <dd>The hostname or <abbr title="Internet Protocol">IP</abbr> address of your
582 $i-th MySQL-server. E.g. localhost.</dd>
584 <dt id="cfg_Servers_port">$cfg['Servers'][$i]['port'] string</dt>
585 <dd>The port-number of your $i-th MySQL-server. Default is 3306 (leave
586 blank). If you use &quot;localhost&quot; as the hostname, MySQL
587 ignores this port number and connects with the socket, so if you want
588 to connect to a port different from the default port, use
589 &quot;127.0.0.1&quot; or the real hostname in
590 <a href="#cfg_Servers_host" class="configrule">$cfg['Servers'][$i]['host']</a>.
591 </dd>
593 <dt id="cfg_Servers_socket">$cfg['Servers'][$i]['socket'] string</dt>
594 <dd>The path to the socket to use. Leave blank for default.<br />
595 To determine the correct socket, check your MySQL configuration or, using the
596 <tt>mysql</tt> command&#8211;line client, issue the <tt>status</tt> command.
597 Among the resulting information displayed will be the socket used.</dd>
599 <dt id="cfg_Servers_connect_type">$cfg['Servers'][$i]['connect_type'] string</dt>
600 <dd>What type connection to use with the MySQL server. Your options are
601 <tt>'socket'</tt> and <tt>'tcp'</tt>. It defaults to 'tcp' as that
602 is nearly guaranteed to be available on all MySQL servers, while
603 sockets are not supported on some platforms.<br /><br />
605 To use the socket mode, your MySQL server must be on the same machine
606 as the Web server.</dd>
608 <dt id="cfg_Servers_extension">$cfg['Servers'][$i]['extension'] string</dt>
609 <dd>What php MySQL extension to use for the connection. Valid options are:
610 <br /><br />
612 <tt><i>mysql</i></tt> :
613 The classic MySQL extension. This is the recommended and default
614 method at this time.<br /><br />
616 <tt><i>mysqli</i></tt> :
617 The improved MySQL extension. This extension became available
618 with php 5.0.0 and is the recommended way to connect to a server
619 running MySQL 4.1.x.</dd>
621 <dt id="cfg_Servers_compress">$cfg['Servers'][$i]['compress'] boolean</dt>
622 <dd>Whether to use a compressed protocol for the MySQL server connection
623 or not (experimental).<br />
624 This feature requires PHP&nbsp;&gt;=&nbsp;4.3.0.</dd>
626 <dt id="controluser">
627 <span id="cfg_Servers_controluser">$cfg['Servers'][$i]['controluser']</span> string<br />
628 <span id="cfg_Servers_controlpass">$cfg['Servers'][$i]['controlpass']</span> string
629 </dt>
630 <dd>This special account is used for 2 distinct purposes: to make possible
631 all relational features (see
632 <a href="#pmadb" class="configrule">$cfg['Servers'][$i]['pmadb']</a>)
633 and, for a MySQL server older than 4.1.2 or running with
634 <tt>--skip-show-database</tt>, to enable a multi-user installation
635 (<abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie
636 authentication mode).<br /><br />
638 When using <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
639 cookie authentication modes (or 'config'
640 authentication mode since phpMyAdmin 2.2.1), you need to supply the
641 details of a MySQL account that has <tt>SELECT</tt> privilege on the
642 <i>mysql.user (all columns except &quot;Password&quot;)</i>,
643 <i>mysql.db (all columns)</i> and <i>mysql.tables_priv (all columns
644 except &quot;Grantor&quot; and &quot;Timestamp&quot;) </i>tables.
645 This account is used to check what databases the user will see at
646 login.<br />
647 Please see the <a href="#setup">install section</a> on
648 &quot;Using authentication modes&quot; for more information.<br /><br />
650 In phpMyAdmin versions before 2.2.5, those were called
651 &quot;stduser/stdpass&quot;.</dd>
653 <dt id="cfg_Servers_auth_type">$cfg['Servers'][$i]['auth_type'] string
654 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'cookie'|'config']</tt></dt>
655 <dd>Whether config or cookie or
656 <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication
657 should be used for this server.
658 <ul><li>'config' authentication (<tt>$auth_type&nbsp;=&nbsp;'config'</tt>)
659 is the plain old way: username and password are stored in
660 <i>config.inc.php</i>.</li>
661 <li>'cookie' authentication mode
662 (<tt>$auth_type&nbsp;=&nbsp;'cookie'</tt>) as introduced in
663 2.2.3 allows you to log in as any valid MySQL user with the
664 help of cookies. Username and password are stored in
665 cookies during the session and password is deleted when it
666 ends. This can also allow you to log in in arbitrary server if
667 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
668 </li>
669 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in older versions)
670 (<tt>$auth_type&nbsp;=&nbsp;'<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
671 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
672 <li>'signon' authentication mode
673 (<tt>$auth_type&nbsp;=&nbsp;'signon'</tt>)
674 as introduced in 2.10.0 allows you to log in from prepared PHP
675 session data. This is useful for implementing single signon
676 from another application. Sample way how to seed session is in
677 signon example: <code>scripts/signon.php</code>. You need to
678 configure <a href="#cfg_Servers_SignonSession"
679 class="configrule">session name</a> and <a
680 href="#cfg_Servers_SignonURL" class="configrule">signon
681 URL</a> to use this authentication method.
682 </ul>
684 Please see the <a href="#setup">install section</a> on &quot;Using authentication modes&quot;
685 for more information.
686 </dd>
687 <dt id="servers_user">
688 <span id="cfg_Servers_user">$cfg['Servers'][$i]['user']</span> string<br />
689 <span id="cfg_Servers_password">$cfg['Servers'][$i]['password']</span> string
690 </dt>
691 <dd>
692 When using auth_type = 'config', this is the user/password-pair
693 which phpMyAdmin will use to connect to the
694 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
695 cookie authentication is used and should be empty.</dd>
696 <dt id="servers_nopassword">
697 <span
698 id="cfg_Servers_nopassword">$cfg['Servers'][$i]['nopassword']</span> boolean
699 </dt>
700 <dd>
701 Allow attempt to log in without password when a login with password
702 fails. This can be used together with http authentication, when
703 authentication is done some other way and phpMyAdmin gets user name
704 from auth and uses empty password for connecting to MySQL. Password
705 login is still tried first, but as fallback, no password method is
706 tried.</dd>
707 <dt id="servers_only_db">
708 <span id="cfg_Servers_only_db">$cfg['Servers'][$i]['only_db']</span> string or array
709 </dt>
710 <dd>
711 If set to a (an array of) database name(s), only this (these) database(s)
712 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
713 database(s) name(s) may contain MySQL wildcards characters
714 (&quot;_&quot; and &quot;%&quot;): if you want to use literal instances
715 of these characters, escape them (I.E. use <tt>'my\_db'</tt> and not
716 <tt>'my_db'</tt>).<br />
717 This setting is an efficient way to lower the server load since the
718 latter does not need to send MySQL requests to build the available
719 database list. But <span class="important">it does not replace the
720 privileges rules of the MySQL database server</span>. If set, it just
721 means only these databases will be displayed but
722 <span class="important">not that all other databases can't be used.</span>
723 <br /><br />
725 An example of using more that one database:
726 <tt>$cfg['Servers'][$i]['only_db'] = array('db1', 'db2');</tt>
727 <br /><br />
729 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
730 databases in the left frame, so that you can individually arrange your databases.<br />
731 If you want to have certain databases at the top, but don't care about the others, you do not
732 need to specify all other databases. Use:
733 <tt>$cfg['Servers'][$i]['only_db'] = array('db3', 'db4', '*');</tt>
734 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
735 order.</dd>
737 <dt><span id="cfg_Servers_hide_db">$cfg['Servers'][$i]['hide_db']</span> string
738 </dt>
739 <dd>Regular expression for hiding some databases. This only hides them
740 from listing, but a user is still able to access them (using, for example,
741 the SQL query area). To limit access, use the MySQL privilege system.
742 <br /><br />
743 For example, to hide all databases starting with the letter &#34;a&#34;, use<br />
744 <pre>$cfg['Servers'][$i]['hide_db'] = '^a';</pre>
745 and to hide both &#34;db1&#34; and &#34;db2&#34; use <br />
746 <pre>$cfg['Servers'][$i]['hide_db'] = '(db1|db2)';</pre>
747 More information on regular expressions can be found in the
748 <a href="http://php.net/manual/en/reference.pcre.pattern.syntax.php">
749 PCRE pattern syntax</a> portion of the PHP reference manual.
750 </dd>
752 <dt id="cfg_Servers_verbose">$cfg['Servers'][$i]['verbose'] string</dt>
753 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
754 this string will be displayed instead of the hostname in the pull-down
755 menu on the main page. This can be useful if you want to show only
756 certain databases on your system, for example.</dd>
758 <dt id="pmadb">
759 <span id="cfg_Servers_pmadb">$cfg['Servers'][$i]['pmadb']</span> string
760 </dt>
761 <dd>The name of the database containing the linked-tables infrastructure.
762 <br /><br />
764 See the <a href="#linked-tables">Linked-tables infrastructure</a>
765 section in this document to see the benefits of this infrastructure,
766 and for a quick way of creating this database and the needed tables.
767 <br /><br />
769 If you are the only user of this phpMyAdmin installation, you can
770 use your current database to store those special tables; in this
771 case, just put your current database name in
772 <tt>$cfg['Servers'][$i]['pmadb']</tt>. For a multi-user installation,
773 set this parameter to the name of your central database containing
774 the linked-tables infrastructure.</dd>
776 <dt id="bookmark">
777 <span id="cfg_Servers_bookmarktable">$cfg['Servers'][$i]['bookmarktable']</span> string
778 </dt>
779 <dd>Since release 2.2.0 phpMyAdmin allows users to bookmark queries. This can be
780 useful for queries you often run.<br /><br />
782 To allow the usage of this functionality:
783 <ul><li>set up <a href="#pmadb">pmadb</a> and the linked-tables infrastructure</li>
784 <li>enter the table name in
785 <tt>$cfg['Servers'][$i]['bookmarktable']</tt></li>
786 </ul>
787 </dd>
789 <dt id="relation">
790 <span id="cfg_Servers_relation">$cfg['Servers'][$i]['relation']</span> string
791 </dt>
792 <dd>Since release 2.2.4 you can describe, in a special 'relation' table,
793 which field is a key in another table (a foreign key). phpMyAdmin
794 currently uses this to
795 <ul><li>make clickable, when you browse the master table, the data values
796 that point to the foreign table;</li>
797 <li>display in an optional tool-tip the &quot;display field&quot;
798 when browsing the master table, if you move the mouse to a column
799 containing a foreign key (use also the 'table_info' table);<br />
800 (see <a href="#faqdisplay"><abbr title="Frequently Asked Questions">
801 FAQ</abbr> 6.7</a>)</li>
802 <li>in edit/insert mode, display a drop-down list of possible foreign
803 keys (key value and &quot;display field&quot; are shown)<br />
804 (see <a href="#faq6_21"><abbr title="Frequently Asked Questions">
805 FAQ</abbr> 6.21</a>)</li>
806 <li>display links on the table properties page, to check referential
807 integrity (display missing foreign keys) for each described key;
808 </li>
809 <li>in query-by-example, create automatic joins (see <a href="#faq6_6">
810 <abbr title="Frequently Asked Questions">FAQ</abbr> 6.6</a>)</li>
811 <li>enable you to get a <abbr title="Portable Document Format">PDF</abbr>
812 schema of your database (also uses the table_coords table).</li>
813 </ul>
815 The keys can be numeric or character.<br /><br />
817 To allow the usage of this functionality:
819 <ul><li>set up <a href="#pmadb">pmadb</a> and the linked-tables
820 infrastructure</li>
821 <li>put the relation table name in
822 <tt>$cfg['Servers'][$i]['relation']</tt></li>
823 <li>now as normal user open phpMyAdmin and for each one of your
824 tables where you want to use this feature, click
825 &quot;Structure/Relation view/&quot; and choose foreign fields.
826 </li>
827 </ul>
829 Please note that in the current version, <tt>master_db</tt>
830 must be the same as <tt>foreign_db</tt>. Those fields have been put in
831 future development of the cross-db relations.
832 </dd>
834 <dt id="table_info">
835 <span id="cfg_Servers_table_info">$cfg['Servers'][$i]['table_info']</span> string
836 </dt>
837 <dd>
838 Since release 2.3.0 you can describe, in a special 'table_info'
839 table, which field is to be displayed as a tool-tip when moving the
840 cursor over the corresponding key.<br />
841 This configuration variable will hold the name of this special
842 table. To allow the usage of this functionality:
843 <ul><li>set up <a href="#pmadb">pmadb</a> and the linked-tables infrastructure</li>
844 <li>put the table name in
845 <tt>$cfg['Servers'][$i]['table_info']</tt></li>
846 <li>then for each table where you want to use this feature,
847 click &quot;Structure/Relation view/Choose field to display&quot;
848 to choose the field.</li>
849 </ul>
850 Usage tip: <a href="#faqdisplay">Display field</a>.
851 </dd>
852 <dt id="table_coords">
853 <span id="cfg_Servers_table_coords">$cfg['Servers'][$i]['table_coords']</span> string<br />
854 <span id="cfg_Servers_pdf_pages">$cfg['Servers'][$i]['pdf_pages']</span> string
855 </dt>
856 <dd>Since release 2.3.0 you can have phpMyAdmin create
857 <abbr title="Portable Document Format">PDF</abbr> pages showing
858 the relations between your tables. To do this it needs two tables
859 &quot;pdf_pages&quot; (storing information about the available
860 <abbr title="Portable Document Format">PDF</abbr>
861 pages) and &quot;table_coords&quot; (storing coordinates where each
862 table will be placed on a <abbr title="Portable Document Format">PDF</abbr>
863 schema output).<br /><br />
865 You must be using the &quot;relation&quot; feature.<br /><br />
867 To allow the usage of this functionality:
869 <ul><li>set up <a href="#pmadb">pmadb</a> and the linked-tables
870 infrastructure</li>
871 <li>put the correct table names in
872 <tt>$cfg['Servers'][$i]['table_coords']</tt> and
873 <tt>$cfg['Servers'][$i]['pdf_pages']</tt></li>
874 </ul>
876 Usage tips: <a href="#faqpdf"><abbr title="Portable Document Format">PDF</abbr> output</a>.
877 </dd>
879 <dt id="col_com">
880 <span id="cfg_Servers_column_info">$cfg['Servers'][$i]['column_info']</span> string
881 </dt>
882 <dd><!-- This part requires a content update! -->
883 Since release 2.3.0 you can store comments to describe each column for
884 each table. These will then be shown on the &quot;printview&quot;.
885 <br /><br />
887 Starting with release 2.5.0, comments are consequently used on the table
888 property pages and table browse view, showing up as tool-tips above the
889 column name (properties page) or embedded within the header of table in
890 browse view. They can also be shown in a table dump. Please see the
891 relevant configuration directives later on.<br /><br />
893 Also new in release 2.5.0 is a MIME-transformation system which is also
894 based on the following table structure. See <a href="#transformations">
895 Transformations</a> for further information. To use the
896 MIME-transformation system, your column_info table has to have the three
897 new fields 'mimetype', 'transformation', 'transformation_options'.
898 <br /><br />
900 To allow the usage of this functionality:
901 <ul><li>set up <a href="#pmadb">pmadb</a> and the linked-tables
902 infrastructure</li>
903 <li>put the table name in
904 <tt>$cfg['Servers'][$i]['column_info']</tt></li>
905 <li>to update your PRE-2.5.0 Column_comments Table use this:
907 <pre>
908 ALTER TABLE `pma_column_comments`
909 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
910 ADD `transformation` VARCHAR( 255 ) NOT NULL,
911 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
912 </pre>
914 and remember that the Variable in <i>config.inc.php</i> has been
915 renamed from<br />
916 <tt>$cfg['Servers'][$i]['column_comments']</tt> to
917 <tt>$cfg['Servers'][$i]['column_info']</tt></li>
918 </ul>
919 </dd>
921 <dt id="history">
922 <span id="cfg_Servers_history">$cfg['Servers'][$i]['history']</span> string
923 </dt>
924 <dd>Since release 2.5.0 you can store your
925 <abbr title="structured query language">SQL</abbr> history, which means
926 all queries you entered manually into the phpMyAdmin interface. If you
927 don't want to use a table-based history, you can use the JavaScript-based
928 history. Using that, all your history items are deleted when closing the
929 window.<br /><br />
931 Using
932 <a href="#cfg_QueryHistoryMax" class="configrule">$cfg['QueryHistoryMax']</a>
933 you can specify an amount of history items you want to have on hold. On
934 every login, this list gets cut to the maximum amount.<br /><br />
936 The query history is only available if JavaScript is enabled in your
937 browser.<br /><br />
939 To allow the usage of this functionality:
941 <ul><li>set up <a href="#pmadb">pmadb</a> and the linked-tables
942 infrastructure</li>
943 <li>put the table name in <tt>$cfg['Servers'][$i]['history']</tt>
944 </li>
945 </ul>
946 </dd>
948 <dt><span id="cfg_Servers_verbose_check">$cfg['Servers'][$i]['verbose_check']</span> boolean
949 </dt>
950 <dd>Because release 2.5.0 introduced the new MIME-transformation support, the
951 column_info table got enhanced with three new fields. If the above variable
952 is set to <tt>TRUE</tt> (default) phpMyAdmin will check if you have the
953 latest table structure available. If not, it will emit a warning to the
954 superuser.<br /><br />
956 You can disable this checking behavior by setting the variable to false,
957 which should offer a performance increase.<br /><br />
959 Recommended to set to FALSE, when you are sure, your table structure is
960 up to date.</dd>
961 <dt><span id="cfg_Servers_AllowRoot">$cfg['Servers'][$i]['AllowRoot']</span>
962 boolean</dt>
963 <dd>Whether to allow root access. This is just simplification of rules below.
964 </dd>
965 <dt id="servers_allowdeny_order">
966 <span id="cfg_Servers_AllowDeny_order">$cfg['Servers'][$i]['AllowDeny']['order']</span> string
967 </dt>
968 <dd>If your rule order is empty, then <abbr title="Internet Protocol">IP</abbr>
969 authentication is disabled.<br /><br />
971 If your rule order is set to <tt>'deny,allow'</tt> then the system applies
972 all deny rules followed by allow rules. Access is allowed by default. Any
973 client which does not match a Deny command or does match an Allow command
974 will be allowed access to the server. <br /><br />
976 If your rule order is set to <tt>'allow,deny'</tt> then the system
977 applies all allow rules followed by deny rules. Access is denied by
978 default. Any client which does not match an Allow directive or does
979 match a Deny directive will be denied access to the server.<br /><br />
981 If your rule order is set to 'explicit', the authentication is
982 performed in a similar fashion to rule order 'deny,allow', with the
983 added restriction that your host/username combination <b>must</b> be
984 listed in the <i>allow</i> rules, and not listed in the <i>deny</i>
985 rules. This is the <b>most</b> secure means of using Allow/Deny rules,
986 and was available in Apache by specifying allow and deny rules without
987 setting any order.
988 </dd>
989 <dt id="servers_allowdeny_rules">
990 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
991 </dt>
992 <dd>The general format for the rules is as such:
994 <pre>
995 &lt;'allow' | 'deny'&gt; &lt;username&gt; [from] &lt;ipmask&gt;
996 </pre>
998 If you wish to match all users, it is possible to use a <tt>'%'</tt> as
999 a wildcard in the <i>username</i> field.<br />
1000 There are a few shortcuts you can use in the <i>ipmask</i> field as
1001 well (please note that those containing SERVER_ADDRESS might not be
1002 available on all webservers):
1003 <pre>
1004 'all' -&gt; 0.0.0.0/0
1005 'localhost' -&gt; 127.0.0.1/8
1006 'localnetA' -&gt; SERVER_ADDRESS/8
1007 'localnetB' -&gt; SERVER_ADDRESS/16
1008 'localnetC' -&gt; SERVER_ADDRESS/24
1009 </pre>
1011 Having an empty rule list is equivalent to either using
1012 <tt>'allow % from all'</tt> if your rule order is set to
1013 <tt>'deny,allow'</tt> or <tt>'deny % from all'</tt> if your rule order
1014 is set to <tt>'allow,deny'</tt> or <tt>'explicit'</tt>.<br /><br />
1016 For the <abbr title="Internet Protocol">IP</abbr> matching system, the
1017 following work:<br />
1018 <tt>xxx.xxx.xxx.xxx</tt> (an exact <abbr title="Internet Protocol">IP</abbr> address)<br />
1019 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1020 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1021 But the following does not work:<br />
1022 <tt>xxx.xxx.xxx.xx[yyy-zzz]</tt> (partial
1023 <abbr title="Internet Protocol">IP</abbr> address range)
1024 </dd>
1025 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1026 <dd>Name of session which will be used for signon authentication method.
1027 </dd>
1028 <dt><span id="cfg_Servers_SignonURL">$cfg['Servers'][$i]['SignonURL']</span> string</dt>
1029 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1030 </dd>
1031 <dt><span id="cfg_Servers_LogoutURL">$cfg['Servers'][$i]['LogoutURL']</span> string</dt>
1032 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1033 </dd>
1035 <dt id="cfg_ServerDefault">$cfg['ServerDefault'] integer</dt>
1036 <dd>If you have more than one server configured, you can set
1037 <tt>$cfg['ServerDefault']</tt> to any one of them to autoconnect to
1038 that server when phpMyAdmin is started, or set it to 0 to be given a
1039 list of servers without logging in.<br />
1040 If you have only one server configured, <tt>$cfg['ServerDefault']</tt>
1041 MUST be set to that server.</dd>
1043 <dt id="cfg_OBGzip">$cfg['OBGzip'] string/boolean</dt>
1044 <dd>Defines whether to use GZip output buffering for increased
1045 speed in <abbr title="HyperText Transfer Protocol">HTTP</abbr> transfers.<br />
1046 Set to true/false for enabling/disabling. When set to 'auto' (string),
1047 phpMyAdmin tries to enable output buffering and will automatically disable
1048 it if your browser has some problems with buffering. IE6 with a certain patch
1049 is known to cause data corruption when having enabled buffering.</dd>
1051 <dt id="cfg_PersistentConnections">$cfg['PersistentConnections'] boolean</dt>
1052 <dd>Whether persistent connections should be used or not (mysql_connect or
1053 mysql_pconnect).</dd>
1055 <dt id="cfg_ForceSSL">$cfg['ForceSSL'] boolean</dt>
1056 <dd>Whether to force using https while accessing phpMyAdmin.</dd>
1058 <dt id="cfg_ExecTimeLimit">$cfg['ExecTimeLimit'] integer [number of seconds]</dt>
1059 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1060 to zero, no time limit is imposed.<br />
1061 This setting is used while importing/exporting dump files but has no
1062 effect when PHP is running in safe mode.</dd>
1064 <dt id="cfg_MemoryLimit">$cfg['MemoryLimit'] integer [number of bytes]</dt>
1065 <dd>Set the number of bytes a script is allowed to allocate. If number set
1066 to zero, no limit is imposed.<br />
1067 This setting is used while importing/exporting dump files but has no
1068 effect when PHP is running in safe mode.<br />
1069 You can also use any string as in php.ini, eg. '16M'.</dd>
1071 <dt id="cfg_SkipLockedTables">$cfg['SkipLockedTables'] boolean</dt>
1072 <dd>Mark used tables and make it possible to show databases with locked
1073 tables (since MySQL 3.23.30).</dd>
1075 <dt id="cfg_ShowSQL">$cfg['ShowSQL'] boolean</dt>
1076 <dd>Defines whether <abbr title="structured query language">SQL</abbr> queries
1077 generated by phpMyAdmin should be displayed or not.</dd>
1079 <dt id="cfg_AllowUserDropDatabase">$cfg['AllowUserDropDatabase'] boolean</dt>
1080 <dd>Defines whether normal users (non-administrator) are allowed to
1081 delete their own database or not. If set as FALSE, the link &quot;Drop
1082 Database&quot; will not be shown, and even a &quot;DROP DATABASE
1083 mydatabase&quot; will be rejected. Quite practical for
1084 <abbr title="Internet service provider">ISP</abbr>'s with many
1085 customers.<br />
1086 Please note that this limitation of SQL queries is not as strict as
1087 when using MySQL privileges. This is due to nature of SQL queries
1088 which might be quite complicated. So this choice should be viewed as
1089 help to avoid accidental dropping rather than strict privilege
1090 limitation.</dd>
1092 <dt id="cfg_Confirm">$cfg['Confirm'] boolean</dt>
1093 <dd>Whether a warning (&quot;Are your really sure...&quot;) should be
1094 displayed when you're about to lose data.</dd>
1096 <dt id="cfg_LoginCookieRecall">$cfg['LoginCookieRecall'] boolean</dt>
1097 <dd>Define whether the previous login should be recalled or not in cookie
1098 authentication mode.</dd>
1100 <dt id="cfg_LoginCookieValidity">$cfg['LoginCookieValidity'] integer [number of seconds]</dt>
1101 <dd>Define how long is login cookie valid.</dd>
1103 <dt id="cfg_LoginCookieStore">$cfg['LoginCookieStore'] integer [number of seconds]</dt>
1104 <dd>Define how long is login cookie should be stored in browser. Default 0
1105 means that it will be kept for existing session. This is recommended
1106 for not trusted environments.</dd>
1108 <dt id="cfg_LoginCookieDeleteAll">$cfg['LoginCookieDeleteAll'] boolean</dt>
1109 <dd>If enabled (default), logout deletes cookies for all servers,
1110 otherwise only for current one. Setting this to false makes it easy to
1111 forget to log out from other server, when you are using more of
1112 them.</dd>
1114 <dt id="cfg_UseDbSearch">$cfg['UseDbSearch'] boolean</dt>
1115 <dd>Define whether the "search string inside database" is enabled or not.</dd>
1117 <dt id="cfg_IgnoreMultiSubmitErrors">$cfg['IgnoreMultiSubmitErrors'] boolean</dt>
1118 <dd>Define whether phpMyAdmin will continue executing a multi-query
1119 statement if one of the queries fails. Default is to abort execution.</dd>
1121 <dt id="cfg_VerboseMultiSubmit">$cfg['VerboseMultiSubmit'] boolean</dt>
1122 <dd>Define whether phpMyAdmin will output the results of each query of a
1123 multi-query statement embedded into the
1124 <abbr title="structured query language">SQL</abbr> output as inline
1125 comments. Defaults to <tt>TRUE</tt>.</dd>
1126 <dt id="AllowArbitraryServer">
1127 <span id="cfg_AllowArbitraryServer">$cfg['AllowArbitraryServer']</span> boolean</dt>
1128 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1129 <br /><br />
1131 <b>NOTE:</b> Please use this carefully, as this may allow users access to
1132 MySQL servers behind the firewall where your
1133 <abbr title="HyperText Transfer Protocol">HTTP</abbr> server is placed.
1134 </dd>
1136 <dt id="cfg_LeftFrameLight">$cfg['LeftFrameLight'] boolean</dt>
1137 <dd>Defines whether to use a select-based menu and display only the current
1138 tables in the left frame (smaller page). Only in Non-Lightmode you can
1139 use the feature to display nested folders using
1140 <a href="#cfg_LeftFrameTableSeparator" class="configrule">$cfg['LeftFrameTableSeparator']</a>
1141 </dd>
1143 <dt id="cfg_LeftFrameDBTree">$cfg['LeftFrameDBTree'] boolean</dt>
1144 <dd>In light mode, defines whether to display the names of databases (in the
1145 selector) using a tree, see also
1146 <a href="#cfg_LeftFrameDBSeparator" class="configrule">$cfg['LeftFrameDBSeparator']</a>.
1147 </dd>
1149 <dt id="cfg_LeftFrameDBSeparator">$cfg['LeftFrameDBSeparator'] string</dt>
1150 <dd>The string used to separate the parts of the database name when showing
1151 them in a tree.</dd>
1153 <dt id="cfg_LeftFrameTableSeparator">$cfg['LeftFrameTableSeparator'] string</dt>
1154 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1155 This means if you have tables like 'first__second__third' this will be
1156 shown as a three-level hierarchy like: first &gt; second &gt; third.
1157 If set to FALSE or empty, the feature is disabled. NOTE: You should
1158 not use this separator at the beginning or end of a
1159 table name or multiple times after another without any other
1160 characters in between.</dd>
1162 <dt id="cfg_LeftFrameTableLevel">$cfg['LeftFrameTableLevel'] string</dt>
1163 <dd>Defines how many sublevels should be displayed when splitting
1164 up tables by the above separator.</dd>
1166 <dt id="cfg_ShowTooltip">$cfg['ShowTooltip'] boolean</dt>
1167 <dd>Defines whether to display table comment as tool-tip in left frame or
1168 not.</dd>
1170 <dt id="cfg_ShowTooltipAliasDB">$cfg['ShowTooltipAliasDB'] boolean</dt>
1171 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1172 comment and the real name. That means that if you have a table called
1173 'user0001' and add the comment 'MyName' on it, you will see the name
1174 'MyName' used consequently in the left frame and the tool-tip shows
1175 the real name of the DB.</dd>
1177 <dt id="cfg_ShowTooltipAliasTB">$cfg['ShowTooltipAliasTB'] boolean/string</dt>
1178 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1180 When setting this to 'nested', the Alias of the Tablename is only used
1181 to split/nest the tables according to the
1182 <a href="#cfg_LeftFrameTableSeparator" class="configrule">$cfg['LeftFrameTableSeparator']</a>
1183 directive. So only the folder is called like the Alias, the tablename itself
1184 stays the real tablename.</dd>
1186 <dt id="cfg_LeftDisplayLogo">$cfg['LeftDisplayLogo'] boolean</dt>
1187 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1188 Defaults to <tt>TRUE</tt>.</dd>
1189 <dt id="cfg_LeftLogoLink">$cfg['LeftLogoLink'] string</dt>
1190 <dd>Enter URL where logo in left frame will point to. For use especially
1191 with self made theme which changes this.</dd>
1192 <dt id="cfg_LeftDisplayServers">$cfg['LeftDisplayServers'] boolean</dt>
1193 <dd>Defines whether or not to display a server choice at the top of the left frame.
1194 Defaults to FALSE.</dd>
1195 <dt id="cfg_DisplayServersList">$cfg['DisplayServersList'] boolean</dt>
1196 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1197 Defaults to FALSE (drop-down).</dd>
1198 <dt id="cfg_ShowStats">$cfg['ShowStats'] boolean</dt>
1199 <dd>Defines whether or not to display space usage and statistics about databases
1200 and tables.<br />
1201 Note that statistics requires at least MySQL 3.23.3 and that, at this
1202 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1204 <dt><span id="cfg_ShowPhpInfo">$cfg['ShowPhpInfo'] </span>boolean<br />
1205 <span id="cfg_ShowChgPassword">$cfg['ShowChgPassword'] </span>boolean<br />
1206 <span id="cfg_ShowCreateDb">$cfg['ShowCreateDb'] </span>boolean
1207 </dt>
1208 <dd>Defines whether to display the &quot;PHP information&quot; and
1209 &quot;Change password &quot; links and form for creating database or
1210 not at the starting main (right) frame. This setting
1211 does not check MySQL commands entered directly.<br /><br />
1213 Please note that to block the usage of phpinfo() in scripts, you
1214 have to put this in your <i>php.ini</i>:
1216 <pre>disable_functions = phpinfo()</pre>
1218 Also note that enabling the &quot;Change password &quot; link has no
1219 effect with &quot;config&quot; authentication mode: because of the
1220 hard coded password value in the configuration file, end users can't
1221 be allowed to change their passwords.</dd>
1223 <dt id="cfg_SuggestDBName">$cfg['SuggestDBName'] boolean</dt>
1224 <dd>Defines whether to suggest a database name on the
1225 &quot;Create Database&quot; form or to keep the textfield empty.</dd>
1227 <dt id="cfg_ShowBlob">$cfg['ShowBlob'] boolean</dt>
1228 <dd>Defines whether or not <tt>BLOB</tt> fields are shown when browsing a table's
1229 content.</dd>
1231 <dt id="cfg_NavigationBarIconic">$cfg['NavigationBarIconic'] string</dt>
1232 <dd>Defines whether navigation bar buttons and the right panel top menu
1233 contain text or symbols only. A value of TRUE displays icons, FALSE
1234 displays text and 'both' displays both icons and text.</dd>
1236 <dt id="cfg_ShowAll">$cfg['ShowAll'] boolean</dt>
1237 <dd>Defines whether a user should be displayed a
1238 &quot;show all (records)&quot; button in browse mode or not.</dd>
1240 <dt id="cfg_MaxRows">$cfg['MaxRows'] integer</dt>
1241 <dd>Number of rows displayed when browsing a result set. If the result set
1242 contains more rows, &quot;Previous&quot; and &quot;Next&quot; links will be shown.</dd>
1244 <dt id="cfg_Order">$cfg['Order'] string [<tt>DESC</tt>|<tt>ASC</tt>|<tt>SMART</tt>]</dt>
1245 <dd>Defines whether fields are displayed in ascending (<tt>ASC</tt>) order,
1246 in descending (<tt>DESC</tt>) order or in a &quot;smart&quot;
1247 (<tt>SMART</tt>) order - I.E. descending order for fields of type TIME,
1248 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1250 <dt id="cfg_ProtectBinary">$cfg['ProtectBinary'] boolean or string</dt>
1251 <dd>Defines whether <tt>BLOB</tt> or <tt>BINARY</tt> fields are protected
1252 from editing when browsing a table's content. Valid values are:
1253 <ul><li><tt>FALSE</tt> to allow editing of all fields;</li>
1254 <li><tt>'blob'</tt> to allow editing of all fields except <tt>BLOBS</tt>;</li>
1255 <li><tt>'all'</tt> to disallow editing of all <tt>BINARY</tt> or
1256 <tt>BLOB</tt> fields.</li>
1257 </ul>
1258 </dd>
1260 <dt id="cfg_ShowFunctionFields">$cfg['ShowFunctionFields'] boolean</dt>
1261 <dd>Defines whether or not MySQL functions fields should be displayed in
1262 edit/insert mode.</dd>
1264 <dt id="cfg_CharEditing">$cfg['CharEditing'] string</dt>
1265 <dd>Defines which type of editing controls should be used for CHAR and
1266 VARCHAR fields. Possible values are:
1267 <ul><li>input - this allows to limit size of text to size of field in
1268 MySQL, but has problems with newlines in fields</li>
1269 <li>textarea - no problems with newlines in fields, but also no
1270 length limitations</li>
1271 </ul>
1272 Default is old behavior so input.</dd>
1274 <dt id="cfg_InsertRows">$cfg['InsertRows'] integer</dt>
1275 <dd>Defines the maximum number of concurrent entries for the Insert page.</dd>
1277 <dt id="cfg_ForeignKeyMaxLimit">$cfg['ForeignKeyMaxLimit'] integer</dt>
1278 <dd>If there are fewer items than this in the set of foreign keys, then a
1279 drop-down box of foreign keys is presented, in the style described by the
1280 <a href="#cfg_ForeignKeyDropdownOrder" class="configrule">$cfg['ForeignKeyDropdownOrder']</a>
1281 setting.</dd>
1283 <dt id="cfg_ForeignKeyDropdownOrder">$cfg['ForeignKeyDropdownOrder'] array</dt>
1284 <dd>For the foreign key drop-down fields, there are several methods of
1285 display, offering both the key and value data. The contents of the
1286 array should be one or both of the following strings:
1287 <i>'content-id'</i>, <i>'id-content'</i>.</dd>
1289 <dt><span id="cfg_ZipDump">$cfg['ZipDump'] </span>boolean<br />
1290 <span id="cfg_GZipDump">$cfg['GZipDump'] </span>boolean<br />
1291 <span id="cfg_BZipDump">$cfg['BZipDump'] </span>boolean
1292 </dt>
1293 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1294 creating a dump file</dd>
1296 <dt><span id="cfg_CompressOnFly">$cfg['CompressOnFly'] </span>boolean<br />
1297 </dt>
1298 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1299 compressed exports. This doesn't affect smaller dumps and allows users to
1300 create larger dumps that won't otherwise fit in memory due to php
1301 memory limit. Produced files contain more GZip/BZip2 headers, but all
1302 normal programs handle this correctly.</dd>
1304 <dt id="cfg_LightTabs">$cfg['LightTabs'] boolean</dt>
1305 <dd>If set to <tt>TRUE</tt>, use less graphically intense tabs on the top of the
1306 mainframe.</dd>
1308 <dt id="cfg_PropertiesIconic">$cfg['PropertiesIconic'] string</dt>
1309 <dd>If set to <tt>TRUE</tt>, will display icons instead of text for db and table
1310 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1311 set to <tt>'both'</tt> if you want icons AND text.<br />
1312 When set to <tt>FALSE</tt>, will only show text.</dd>
1314 <dt id="cfg_PropertiesNumColumns">$cfg['PropertiesNumColumns'] integer</dt>
1315 <dd>How many columns will be utilized to display the tables on the
1316 database property view? Default is 1 column. When setting this to a
1317 value larger than 1, the type of the database will be omitted for more
1318 display space.</dd>
1321 <dt id="cfg_DefaultTabServer">$cfg['DefaultTabServer'] string</dt>
1322 <dd>Defines the tab displayed by default on server view. Possible
1323 values: &quot;main.php&quot; (recommended for multi-user setups),
1324 &quot;server_databases.php&quot;, &quot;server_status.php&quot;,
1325 &quot;server_variables.php&quot;, &quot;server_privileges.php&quot;
1326 or &quot;server_processlist.php&quot;.</dd>
1328 <dt id="cfg_DefaultTabDatabase">$cfg['DefaultTabDatabase'] string</dt>
1329 <dd>Defines the tab displayed by default on database view. Possible
1330 values: &quot;db_details_structure.php&quot;,
1331 &quot;db_details.php&quot; or &quot;db_search.php&quot;.</dd>
1333 <dt id="cfg_DefaultTabTable">$cfg['DefaultTabTable'] string</dt>
1334 <dd>Defines the tab displayed by default on table view. Possible
1335 values: &quot;tbl_properties_structure.php&quot;,
1336 &quot;tbl_properties.php&quot;, &quot;tbl_select.php&quot;,
1337 &quot;tbl_change.php&quot; or &quot;sql.php&quot;.</dd>
1339 <dt id="cfg_MySQLManualBase">$cfg['MySQLManualBase'] string</dt>
1340 <dd>If set to an <abbr title="Uniform Resource Locator">URL</abbr> which
1341 points to the MySQL documentation (type depends
1342 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1343 generated.<br />
1344 See <a href="http://dev.mysql.com/doc/">MySQL Documentation page</a>
1345 for more information about MySQL manuals and their types.</dd>
1347 <dt id="cfg_MySQLManualType">$cfg['MySQLManualType'] string</dt>
1348 <dd>Type of MySQL documentation:
1349 <ul><li>viewable - &quot;viewable online&quot;, current one used on MySQL website</li>
1350 <li>searchable - &quot;Searchable, with user comments&quot;</li>
1351 <li>chapters - &quot;HTML, one page per chapter&quot;</li>
1352 <li>big - &quot;HTML, all on one page&quot;</li>
1353 <li>none - do not show documentation links</li>
1354 </ul>
1355 </dd>
1357 <dt id="cfg_DefaultLang">$cfg['DefaultLang'] string</dt>
1358 <dd>Defines the default language to use, if not browser-defined or
1359 user-defined.<br />
1360 See the <i>select_lang.lib.php</i> script to know the valid values for
1361 this setting.</dd>
1363 <dt id="cfg_DefaultConnectionCollation">$cfg['DefaultConnectionCollation'] string</dt>
1364 <dd>Defines the default connection collation to use, if not
1365 user-defined.<br />
1366 See the <a href="http://dev.mysql.com/doc/mysql/en/charset-charsets.html">MySQL
1367 documentation</a> for list of possible values.</dd>
1369 <dt id="cfg_Lang">$cfg['Lang'] string</dt>
1370 <dd>Force: always use this language (must be defined in the
1371 <i>select_lang.lib.php</i> script).</dd>
1373 <dt id="cfg_FilterLanguages">$cfg['FilterLanguages'] string</dt>
1374 <dd>Limit list of available languages to those matching the given regular
1375 expression. For example if you want only Czech and English, you should
1376 set filter to <code>'^(cs|en)'</code>.</dd>
1378 <dt id="cfg_DefaultCharset">$cfg['DefaultCharset'] string</dt>
1379 <dd>Default character set to use for recoding of MySQL queries. This must be
1380 enabled and it's described by
1381 <a href="#cfg_AllowAnywhereRecoding" class="configrule">$cfg['AllowAnywhereRecoding']</a>
1382 option.<br />
1383 You can give here any character set which is in
1384 <a href="#cfg_AvailableCharsets" class="configrule">$cfg['AvailableCharsets']</a>
1385 array and this is just default choice, user can select any of them.</dd>
1387 <dt id="cfg_AllowAnywhereRecoding">$cfg['AllowAnywhereRecoding'] boolean</dt>
1388 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1389 support (compiled in or module) in PHP to allow MySQL queries recoding
1390 and used language file must have it enabled (by default only these
1391 which are in Unicode, just to avoid losing some characters).<br /><br />
1393 Setting this to <tt>TRUE</tt> also activates a pull-down menu
1394 in the Export page, to choose the character set when exporting a file.
1395 </dd>
1397 <dt id="cfg_RecodingEngine">$cfg['RecodingEngine'] string</dt>
1398 <dd>You can select here which functions will be used for character set
1399 conversion. Possible values are:
1400 <ul><li>auto - automatically use available one (first is tested
1401 iconv, then recode)</li>
1402 <li>iconv - use iconv or libiconv functions</li>
1403 <li>recode - use recode_string function</li>
1404 </ul>
1405 Default is auto.</dd>
1407 <dt id="cfg_IconvExtraParams">$cfg['IconvExtraParams'] string</dt>
1408 <dd>Specify some parameters for iconv used in charset conversion. See
1409 <a href="http://www.gnu.org/software/libiconv/documentation/libiconv/iconv_open.3.html">iconv
1410 documentation</a> for details. By default <code>//TRANSLIT</code> is
1411 used, so that invalid characters will be transliterated.</dd>
1413 <dt id="cfg_AvailableCharsets">$cfg['AvailableCharsets'] array</dt>
1414 <dd>Available character sets for MySQL conversion. You can add your own (any of
1415 supported by recode/iconv) or remove these which you don't use.
1416 Character sets will be shown in same order as here listed, so if you
1417 frequently use some of these move them to the top.</dd>
1419 <dt id="cfg_GD2Available">$cfg['GD2Available'] string</dt>
1420 <dd>Specifies whether GD &gt;= 2 is available. If yes it can be used for
1421 MIME transformations.<br />
1422 Possible values are:
1423 <ul><li>auto - automatically detect, this is a bit expensive
1424 operation for php &lt; 4.3.0 so it is preferred to change this
1425 according to your server real possibilities</li>
1426 <li>yes - GD 2 functions can be used</li>
1427 <li>no - GD 2 function cannot be used</li>
1428 </ul>
1429 Default is auto.
1430 </dd>
1432 <dt id="cfg_NaviWidth">$cfg['NaviWidth'] integer</dt>
1433 <dd>Navi frame width in pixels. See <tt>themes/themename/layout.inc.php</tt>.
1434 </dd>
1436 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1437 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1438 </dt>
1439 <dd>The background styles used for both the frames.
1440 See <tt>themes/themename/layout.inc.php</tt>.</dd>
1442 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1443 <span id="cfg_NaviPointerColor">$cfg['NaviPointerColor']</span> string [valid css color]</dt>
1444 <dd>The style used for the pointer in the navi frame.
1445 See <tt>themes/themename/layout.inc.php</tt>.</dd>
1447 <dt id="cfg_LeftPointerEnable">$cfg['LeftPointerEnable'] boolean</dt>
1448 <dd>A value of <tt>TRUE</tt> activates the navi pointer (when LeftFrameLight
1449 is <tt>FALSE</tt>).</dd>
1451 <dt id="cfg_Border">$cfg['Border'] integer</dt>
1452 <dd>The size of a table's border. See <tt>themes/themename/layout.inc.php</tt>.
1453 </dd>
1455 <dt id="cfg_ThBackground">$cfg['ThBackground'] string [valid css code for background]<br />
1456 <span id="cfg_ThColor">$cfg['ThColor']</span> string [valid css color]</dt>
1457 <dd>The style used for table headers. See
1458 <tt>themes/themename/layout.inc.php</tt>.</dd>
1460 <dt id="cfg_BgcolorOne">$cfg['BgOne'] string [HTML color]</dt>
1461 <dd>The color (HTML) #1 for table rows. See <tt>themes/themename/layout.inc.php</tt>.
1462 </dd>
1464 <dt id="cfg_BgcolorTwo">$cfg['BgTwo'] string [HTML color]</dt>
1465 <dd>The color (HTML) #2 for table rows. See <tt>themes/themename/layout.inc.php</tt>.
1466 </dd>
1468 <dt><span id="cfg_BrowsePointerColor">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1469 <span id="cfg_BrowsePointerColor">$cfg['BrowsePointerColor'] </span>string [HTML color]<br />
1470 <span id="cfg_BrowseMarkerColor">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1471 <span id="cfg_BrowseMarkerColor">$cfg['BrowseMarkerColor'] </span>string [HTML color]
1472 </dt>
1473 <dd>The colors (HTML) uses for the pointer and the marker in browse mode.<br />
1474 The former feature highlights the row over which your mouse is passing
1475 and the latter lets you visually mark/unmark rows by clicking on
1476 them.<br />
1477 See <tt>themes/themename/layout.inc.php</tt>.</dd>
1479 <dt id="cfg_BrowsePointerEnable">$cfg['BrowsePointerEnable'] boolean</dt>
1480 <dd>Whether to activate the browse pointer or not.</dd>
1482 <dt id="cfg_BrowseMarkerEnable">$cfg['BrowseMarkerEnable'] boolean</dt>
1483 <dd>Whether to activate the browse marker or not.</dd>
1485 <dt><span id="cfg_TextareaCols">$cfg['TextareaCols'] </span>integer<br />
1486 <span id="cfg_TextareaRows">$cfg['TextareaRows'] </span>integer<br />
1487 <span id="cfg_CharTextareaCols">$cfg['CharTextareaCols'] </span>integer<br />
1488 <span id="cfg_CharTextareaRows">$cfg['CharTextareaRows'] </span>integer
1489 </dt>
1490 <dd>Number of columns and rows for the textareas.<br />
1491 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1492 <abbr title="structured query language">SQL</abbr> textareas inside the query window.<br />
1493 The Char* values are used for CHAR and VARCHAR editing (if configured
1494 via <a href="#cfg_CharEditing">$cfg['CharEditing']</a>).</dd>
1496 <dt><span id="cfg_LongtextDoubleTextarea">$cfg['LongtextDoubleTextarea'] </span>boolean
1497 </dt>
1498 <dd>Defines whether textarea for LONGTEXT fields should have double size.</dd>
1500 <dt><span id="cfg_TextareaAutoSelect">$cfg['TextareaAutoSelect'] </span>boolean
1501 </dt>
1502 <dd>Defines if the whole textarea of the query box will be selected on
1503 click.</dd>
1504 <dt id="CtrlArrowsMoving">
1505 <span id="cfg_CtrlArrowsMoving">$cfg['CtrlArrowsMoving'] </span>boolean
1506 </dt>
1507 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1508 editing.</dd>
1510 <dt id="cfg_LimitChars">$cfg['LimitChars'] integer</dt>
1511 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1512 Can be turned off by a toggle button on the browse page.</dd>
1514 <dt><span id="cfg_ModifyDeleteAtLeft">$cfg['ModifyDeleteAtLeft'] </span>boolean
1515 <span id="cfg_ModifyDeleteAtRight">$cfg['ModifyDeleteAtRight'] </span>boolean
1516 </dt>
1517 <dd>Defines the place where modify and delete links would be put when
1518 tables contents are displayed (you may have them displayed both at the
1519 left and at the right).
1520 &quot;Left&quot; and &quot;right&quot; are parsed as &quot;top&quot;
1521 and &quot;bottom&quot; with vertical display mode.</dd>
1523 <dt id="cfg_DefaultDisplay">$cfg['DefaultDisplay'] string
1524 <span id="cfg_HeaderFlipType">$cfg['HeaderFlipType'] </span>string
1525 </dt>
1526 <dd>There are 3 display modes: horizontal, horizontalflipped and vertical.
1527 Define which one is displayed by default. The first mode displays each
1528 row on a horizontal line, the second rotates the headers by 90
1529 degrees, so you can use descriptive headers even though fields only
1530 contain small values and still print them out. The vertical mode sorts
1531 each row on a vertical lineup.<br /><br />
1533 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1534 the rotation of the header for horizontalflipped is done via CSS. If
1535 set to 'fake' PHP does the transformation for you, but of course this
1536 does not look as good as CSS.</dd>
1538 <dt id="DefaultPropDisplay">
1539 <span id="cfg_DefaultPropDisplay">$cfg['DefaultPropDisplay']</span> string</dt>
1540 <dd>When editing/creating new columns in a table all fields normally get
1541 lined up one field a line. (default: 'horizontal'). If you set this to
1542 'vertical' you can have each field lined up vertically beneath each
1543 other. You can save up a lot of place on the horizontal direction and
1544 no longer have to scroll.</dd>
1546 <dt id="cfg_ShowBrowseComments">$cfg['ShowBrowseComments'] boolean<br />
1547 <span id="cfg_ShowPropertyComments">$cfg['ShowPropertyComments'] </span>boolean
1548 </dt>
1549 <dd>By setting the corresponding variable to <tt>TRUE</tt> you can enable the
1550 display of column comments in Browse or Property display. In browse
1551 mode, the comments are shown inside the header. In property mode,
1552 comments are displayed using a CSS-formatted dashed-line below the
1553 name of the field. The comment is shown as a tool-tip for that field.
1554 </dd>
1556 <dt id="cfg_UploadDir">$cfg['UploadDir'] string</dt>
1557 <dd>
1558 The name of the directory where
1559 <abbr title="structured query language">SQL</abbr> files have been
1560 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1561 are available under a drop-down box when you click the database name,
1562 then the <abbr title="structured query language">SQL</abbr> tab.
1563 <br /><br />
1565 If you want different directory for each user, %u will be replaced
1566 with username.<br /><br />
1568 Please note that the file names must have the suffix &quot;.sql&quot;
1569 (or &quot;.sql.bz2&quot; or &quot;.sql.gz&quot; if support for
1570 compressed formats is enabled).<br /><br />
1572 This feature is useful when your file is too big to be uploaded via
1573 <abbr title="HyperText Transfer Protocol">HTTP</abbr>, or when file
1574 uploads are disabled in PHP.<br /><br />
1576 Please note that if PHP is running in safe mode, this directory must
1577 be owned by the same user as the owner of the phpMyAdmin scripts.
1578 <br /><br />
1580 See also <a href="#faq1_16">
1581 <abbr title="Frequently Asked Questions">FAQ</abbr> 1.16</a> for
1582 alternatives.
1583 </dd>
1585 <dt id="cfg_docSQLDir">$cfg['docSQLDir'] string</dt>
1586 <dd>
1587 The name of the directory where docSQL files can be uploaded for
1588 import into phpMyAdmin.
1589 <br /><br />
1590 Please note that if PHP is running in safe mode, this directory must
1591 be owned by the same user as the owner of the phpMyAdmin scripts.
1592 </dd>
1594 <dt id="cfg_SaveDir">$cfg['SaveDir'] string</dt>
1595 <dd>
1596 The name of the directory where dumps can be saved.<br /><br />
1598 If you want different directory for each user, %u will be replaced
1599 with username.<br /><br />
1601 Please note that the directory has to be writable for user running
1602 webserver.<br /><br />
1604 Please note that if PHP is running in safe mode, this directory must
1605 be owned by the same user as the owner of the phpMyAdmin scripts.
1606 </dd>
1608 <dt id="cfg_TempDir">$cfg['TempDir'] string</dt>
1609 <dd>
1610 The name of the directory where temporary files can be stored.
1611 <br /><br />
1612 This is needed for native MS Excel export, see
1613 <a href="#faq6_23"><abbr title="Frequently Asked Questions">FAQ</abbr>
1614 6.23</a>
1615 </dd>
1617 <dt id="cfg_Export">$cfg['Export'] array</dt>
1618 <dd>
1619 In this array are defined default parameters for export, names of
1620 items are similar to texts seen on export page, so you can easily
1621 identify what they mean.
1622 </dd>
1624 <dt id="cfg_Import">$cfg['Import'] array</dt>
1625 <dd>
1626 In this array are defined default parameters for import, names of
1627 items are similar to texts seen on import page, so you can easily
1628 identify what they mean.
1629 </dd>
1631 <dt id="cfg_RepeatCells">$cfg['RepeatCells'] integer</dt>
1632 <dd>
1633 Repeat the headers every X cells, or 0 to deactivate.
1634 </dd>
1636 <dt id="cfg_EditInWindow">$cfg['EditInWindow'] boolean<br />
1637 <span id="cfg_QueryWindowWidth">$cfg['QueryWindowWidth'] </span>integer<br />
1638 <span id="cfg_QueryWindowHeight">$cfg['QueryWindowHeight'] </span>integer<br />
1639 <span id="cfg_QueryHistoryDB">$cfg['QueryHistoryDB'] </span>boolean<br />
1640 <span id="cfg_QueryWindowDefTab">$cfg['QueryWindowDefTab'] </span>string<br />
1641 <span id="cfg_QueryHistoryMax">$cfg['QueryHistoryMax'] </span>integer
1642 </dt>
1643 <dd>
1644 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1645 or icon is always displayed on the left panel. If JavaScript is enabled in
1646 your browser, a click on this opens a distinct query window, which is
1647 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1648 changes to display a query box.<br /><br />
1650 The size of this query window can be customized with
1651 <tt>$cfg['QueryWindowWidth']</tt> and <tt>$cfg['QueryWindowWidth']</tt>
1652 - both integers for the size in pixels. Note that normally, those
1653 parameters will be modified in <tt>layout.inc.php</tt> for the
1654 theme you are using.<br /><br />
1656 If <tt>$cfg['EditInWindow']</tt> is set to true, a click on [Edit]
1657 from the results page (in the &quot;Showing Rows&quot; section)
1658 opens the query window and puts the current query
1659 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1660 query in the right panel's query box.
1661 <br /><br />
1662 The usage of the JavaScript query window is recommended if you have a
1663 JavaScript enabled browser. Basic functions are used to exchange quite
1664 a few variables, so most 4th generation browsers should be capable to
1665 use that feature. It currently is only tested with Internet Explorer 6
1666 and Mozilla 1.x.
1667 <br /><br />
1668 If <tt>$cfg['QueryHistoryDB']</tt> is set to <tt>TRUE</tt>, all your Queries are logged
1669 to a table, which has to be created by you (see <a
1670 href="#history" class="configrule">$cfg['Servers'][$i]['history']</a>). If set to FALSE,
1671 all your queries will be appended to the form, but only as long as
1672 your window is opened they remain saved.
1673 <br /><br />
1674 When using the JavaScript based query window, it will always get
1675 updated when you click on a new table/db to browse and will focus if
1676 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1677 the query window by checking the box "Do not overwrite this query from
1678 outside the window" below the query textarea. Then you can browse
1679 tables/databases in the background without losing the contents of the
1680 textarea, so this is especially useful when composing a query with
1681 tables you first have to look in. The checkbox will get automatically
1682 checked whenever you change the contents of the textarea. Please
1683 uncheck the button whenever you definitely want the query window to
1684 get updated even though you have made alterations.
1685 <br /><br />
1686 If <tt>$cfg['QueryHistoryDB']</tt> is set to <tt>TRUE</tt> you can specify the amount of
1687 saved history items using <tt>$cfg['QueryHistoryMax']</tt>.
1688 <br /><br />
1689 The query window also has a custom tabbed look to group the features.
1690 Using the variable <tt>$cfg['QueryWindowDefTab']</tt> you can specify the
1691 default tab to be used when opening the query window. It can be set to
1692 either 'sql', 'files', 'history' or 'full'.</dd>
1694 <dt id="cfg_BrowseMIME">$cfg['BrowseMIME'] boolean</dt>
1695 <dd>Enable <a href="#transformations">MIME-transformations</a>.</dd>
1697 <dt id="cfg_MaxExactCount">$cfg['MaxExactCount'] integer</dt>
1698 <dd><ul><li>For InnoDB tables, determines for how large tables phpMyAdmin
1699 should get the exact row count using <code>SELECT COUNT</code>.
1700 If the approximate row count as returned by
1701 <code>SHOW TABLE STATUS</code> is smaller than this value,
1702 <code>SELECT COUNT</code> will be used, otherwise the approximate
1703 count will be used.</li>
1704 <li>For VIEWs, since obtaining the exact count could have an
1705 impact on performance, this value is the maximum to be displayed.
1706 </li>
1707 </ul>
1708 </dd>
1710 <dt id="wysiwyg">
1711 <span id="cfg_WYSIWYG-PDF">$cfg['WYSIWYG-PDF'] </span>boolean</dt>
1712 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1713 <abbr title="Portable Document Format">PDF</abbr>
1714 page. By clicking on the button 'toggle scratchboard' on the page
1715 where you edit x/y coordinates of those elements you can activate a
1716 scratchboard where all your elements are placed. By clicking on an
1717 element, you can move them around in the pre-defined area and the x/y
1718 coordinates will get updated dynamically. Likewise, when entering a
1719 new position directly into the input field, the new position in the
1720 scratchboard changes after your cursor leaves the input field.<br />
1721 You have to click on the 'OK'-button below the tables to save the new
1722 positions. If you want to place a new element, first add it to the
1723 table of elements and then you can drag the new element around.<br />
1724 By changing the paper size and the orientation you can change the size
1725 of the scratchboard as well. You can do so by just changing the
1726 dropdown field below, and the scratchboard will resize automatically,
1727 without interfering with the current placement of the elements.<br />
1728 If ever an element gets out of range you can either enlarge the paper
1729 size or click on the 'reset' button to place all elements below each
1730 other.<br />
1731 <b>NOTE:</b> You have to use a recent browser like IE6 or Mozilla to
1732 get this control to work. The basic Drag&amp;Drop script functionality
1733 was kindly borrowed from www.youngpup.net and is underlying so
1734 specific license.</dd>
1736 <dt id="cfg_NaturalOrder">$cfg['NaturalOrder'] boolean</dt>
1737 <dd>Sorts database and table names according to natural order (for example,
1738 t1, t2, t10). Currently implemented in the left panel (Light mode)
1739 and in Database view, for the table list.</dd>
1741 <dt id="cfg_TitleTable">$cfg['TitleTable'] string</dt>
1742 <dt id="cfg_TitleDatabase">$cfg['TitleDatabase'] string</dt>
1743 <dt id="cfg_TitleServer">$cfg['TitleServer'] string</dt>
1744 <dt id="cfg_TitleDefault">$cfg['TitleDefault'] string</dt>
1745 <dd>Allows you to specify window's title bar. Following magic string can
1746 be used to get special values:
1747 <dl>
1748 <dt><code>@HTTP_HOST@</code></dt>
1749 <dd>HTTP host that runs phpMyAdmin</dd>
1750 <dt><code>@SERVER@</code></dt>
1751 <dd>MySQL server name</dd>
1752 <dt><code>@VERBOSE@</code></dt>
1753 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
1754 <dt><code>@VSERVER@</code></dt>
1755 <dd>Verbose MySQL server name if set, otherwise normal</dd>
1756 <dt><code>@DATABASE@</code></dt>
1757 <dd>Currently opened database</dd>
1758 <dt><code>@TABLE@</code></dt>
1759 <dd>Currently opened table</dd>
1760 <dt><code>@PHPMYADMIN@</code></dt>
1761 <dd>phpMyAdmin with version</dd>
1762 </dl>
1763 </dd>
1765 <dt id="cfg_ErrorIconic">$cfg['ErrorIconic'] boolean</dt>
1766 <dd>Uses icons for warnings, errors and informations.</dd>
1768 <dt id="cfg_MainPageIconic">$cfg['MainPageIconic'] boolean</dt>
1769 <dd>Uses icons on main page in lists and menu tabs.</dd>
1771 <dt id="cfg_ReplaceHelpImg">$cfg['ReplaceHelpImg'] boolean</dt>
1772 <dd>Shows a help button instead of the &quot;Documentation&quot; message.
1773 </dd>
1775 <dt id="cfg_ThemePath">$cfg['ThemePath'] string</dt>
1776 <dd>If theme manager is active, use this as the path of the subdirectory
1777 containing all the themes.</dd>
1779 <dt id="cfg_ThemeManager">$cfg['ThemeManager'] boolean</dt>
1780 <dd>Enables user-selectable themes. See <a href="#faqthemes">
1781 <abbr title="Frequently Asked Questions">FAQ</abbr> 2.7</a>.</dd>
1783 <dt id="cfg_ThemeDefault">$cfg['ThemeDefault'] string</dt>
1784 <dd>The default theme (a subdirectory under <tt>cfg['ThemePath']</tt>).</dd>
1786 <dt id="cfg_ThemePerServer">$cfg['ThemePerServer'] boolean</dt>
1787 <dd>Whether to allow different theme for each server.</dd>
1789 <dt id="cfg_DefaultQueryTable">$cfg['DefaultQueryTable'] string<br />
1790 <span id="cfg_DefaultQueryDatabase">$cfg['DefaultQueryDatabase']</span> string
1791 </dt>
1792 <dd>Default queries that will be displayed in query boxes when user didn't
1793 specify any. Use %d for database name, %t for table name and %f for a
1794 comma separated list of field names. Note that %t and %f are only
1795 applicable to <tt>$cfg['DefaultQueryTable']</tt>.</dd>
1797 <dt id="cfg_SQP_fmtType">$cfg['SQP']['fmtType'] string [<tt>html</tt>|<tt>none</tt>]</dt>
1798 <dd>
1799 The main use of the new <abbr title="structured query language">SQL</abbr> Parser is to pretty-print <abbr title="structured query language">SQL</abbr> queries. By
1800 default we use HTML to format the query, but you can disable this by
1801 setting this variable to <tt>'none'</tt>.
1802 </dd>
1804 <dt id="cfg_SQP_fmtInd">$cfg['SQP']['fmtInd'] float<br />
1805 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
1806 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
1807 query inside a bracket is indented. By changing
1808 <tt>$cfg['SQP']['fmtInd']</tt> you can change the amount of this indent.
1809 <br />Related in purpose is <tt>$cfg['SQP']['fmtIndUnit']</tt> which
1810 specifies the units of the indent amount that you specified. This is
1811 used via stylesheets.</dd>
1813 <dt id="cfg_SQP_fmtColor">$cfg['SQP']['fmtColor'] array of string tuples</dt>
1814 <dd>This array is used to define the colours for each type of element of
1815 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
1816 <i>class</i> =&gt; [<i>HTML colour code</i> | <i>empty string</i>]<br />
1817 If you specify an empty string for the color of a class, it is ignored
1818 in creating the stylesheet.
1819 You should not alter the class names, only the colour strings.<br />
1820 <b>Class name key:</b>
1821 <ul><li><b>comment</b> Applies to all comment sub-classes</li>
1822 <li><b>comment_mysql</b> Comments as <tt>"#...\n"</tt></li>
1823 <li><b>comment_ansi</b> Comments as <tt>"-- ...\n"</tt></li>
1824 <li><b>comment_c</b> Comments as <tt>"/*...*/"</tt></li>
1825 <li><b>digit</b> Applies to all digit sub-classes</li>
1826 <li><b>digit_hex</b> Hexadecimal numbers</li>
1827 <li><b>digit_integer</b> Integer numbers</li>
1828 <li><b>digit_float</b> Floating point numbers</li>
1829 <li><b>punct</b> Applies to all punctuation sub-classes</li>
1830 <li><b>punct_bracket_open_round</b> Opening brackets<tt>"("</tt></li>
1831 <li><b>punct_bracket_close_round</b> Closing brackets <tt>")"</tt></li>
1832 <li><b>punct_listsep</b> List item Separator <tt>","</tt></li>
1833 <li><b>punct_qualifier</b> Table/Column Qualifier <tt>"."</tt> </li>
1834 <li><b>punct_queryend</b> End of query marker <tt>";"</tt></li>
1835 <li><b>alpha</b> Applies to all alphabetic classes</li>
1836 <li><b>alpha_columnType</b> Identifiers matching a column type</li>
1837 <li><b>alpha_columnAttrib</b> Identifiers matching a database/table/column attribute</li>
1838 <li><b>alpha_functionName</b> Identifiers matching a MySQL function name</li>
1839 <li><b>alpha_reservedWord</b> Identifiers matching any other reserved word</li>
1840 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
1841 <li><b>alpha_identifier</b> All other identifiers</li>
1842 <li><b>quote</b> Applies to all quotation mark classes</li>
1843 <li><b>quote_double</b> Double quotes <tt>"</tt></li>
1844 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
1845 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
1846 </ul>
1847 </dd>
1849 <dt id="cfg_SQLValidator">$cfg['SQLValidator'] boolean</dt>
1850 <dd><dl><dt id="cfg_SQLValidator_use">$cfg['SQLValidator']['use'] boolean</dt>
1851 <dd>phpMyAdmin now supports use of the <a href="http://developer.mimer.com/validator/index.htm">Mimer <abbr title="structured query language">SQL</abbr> Validator</a> service,
1852 as originally published on
1853 <a href="http://developers.slashdot.org/article.pl?sid=02/02/19/1720246">Slashdot</a>.
1854 <br />
1855 For help in setting up your system to use the service, see the
1856 <a href="#faqsqlvalidator"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.14</a>.
1857 </dd>
1859 <dt id="cfg_SQLValidator_username">$cfg['SQLValidator']['username'] string<br />
1860 <span id="cfg_SQLValidator_password">$cfg['SQLValidator']['password']</span> string</dt>
1861 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
1862 and any password, so we use those by default. Instead, if
1863 you have an account with them, you can put your login details
1864 here, and it will be used in place of the anonymous login.</dd>
1865 </dl>
1866 </dd>
1868 <dt id="cfg_DBG">$cfg['DBG']</dt>
1869 <dd><b>DEVELOPERS ONLY!</b></dd>
1871 <dt id="cfg_DBG_enable">$cfg['DBG']['enable'] boolean</dt>
1872 <dd><b>DEVELOPERS ONLY!</b><br />
1873 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
1874 the code.<br />
1875 For help in setting up your system to this, see the
1876 <a href="#developersdbg">Developers</a> section.</dd>
1878 <dt id="cfg_DBG_profile_enable">$cfg['DBG']['profile']['enable'] boolean</dt>
1879 <dd><b>DEVELOPERS ONLY!</b><br />
1880 Enable profiling support for phpMyAdmin. This will append a chunk of data
1881 to the end of every page displayed in the main window with profiling
1882 statistics for that page.<br />
1883 You may need to increase the maximum execution time for this to
1884 complete successfully.</dd>
1886 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
1887 <dd><b>DEVELOPERS ONLY!</b><br />
1888 When profiling data is displayed, this variable controls the threshold of
1889 display for any profiling data, based on the average time each time has
1890 taken. If it is over the threshold it is displayed, otherwise it is not
1891 displayed. This takes a value in milliseconds. In most cases you don't need
1892 to edit this.</dd>
1894 <dt id="cfg_ColumnTypes">$cfg['ColumnTypes'] array</dt>
1895 <dd>All possible types of a MySQL column. In most cases you don't need to
1896 edit this.</dd>
1898 <dt id="cfg_AttributeTypes">$cfg['AttributeTypes'] array</dt>
1899 <dd>Possible attributes for fields. In most cases you don't need to edit
1900 this.</dd>
1902 <dt id="cfg_Functions">$cfg['Functions'] array</dt>
1903 <dd>A list of functions MySQL supports. In most cases you don't need to
1904 edit this.</dd>
1906 <dt id="cfg_RestrictColumnTypes">$cfg['RestrictColumnTypes'] array</dt>
1907 <dd>Mapping of column types to meta types used for preferring displayed
1908 functions. In most cases you don't need to edit this.</dd>
1910 <dt id="cfg_RestrictFunctions">$cfg['RestrictFunctions'] array</dt>
1911 <dd>Functions preferred for column meta types as defined in
1912 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
1913 to edit this.</dd>
1915 <dt id="cfg_DefaultFunctions">$cfg['DefaultFunctions'] array</dt>
1916 <dd>Functions selected by default when inserting/changing row, Functions
1917 are defined for meta types from
1918 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a> and for
1919 <code>first_timestamp</code>, which is used for first timestamp column
1920 in table.</dd>
1922 <dt id="cfg_NumOperators">$cfg['NumOperators'] array</dt>
1923 <dd>Operators available for search operations on numeric and date fields.
1924 </dd>
1926 <dt id="cfg_TextOperators">$cfg['TextOperators'] array</dt>
1927 <dd>Operators available for search operations on character fields.
1928 Note that we put <code>LIKE</code> by default instead of
1929 <code>LIKE %...%</code>, to avoid unintended performance problems
1930 in case of huge tables.</dd>
1932 <dt id="cfg_EnumOperators">$cfg['EnumOperators'] array</dt>
1933 <dd>Operators available for search operations on enum fields.</dd>
1935 <dt id="cfg_NullOperators">$cfg['NullOperators'] array</dt>
1936 <dd>Additional operators available for search operations when the
1937 field can be null.</dd>
1939 </dl>
1941 <!-- TRANSFORMATIONS -->
1942 <h2 id="transformations">Transformations</h2>
1944 <ol><li><a href="#transformationsintro">Introduction</a></li>
1945 <li><a href="#transformationshowto">Usage</a></li>
1946 <li><a href="#transformationsfiles">File structure</a></li>
1947 </ol>
1949 <h3 id="transformationsintro">1. Introduction</h3>
1951 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
1952 and the proper directives. Please see the <a href="#config">Configuration
1953 section</a> on how to do so.</p>
1955 <p> You can apply different transformations to the contents of each field. The
1956 transformation will take the content of each field and transform it with
1957 certain rules defined in the selected transformation.</p>
1959 <p> Say you have a field 'filename' which contains a filename. Normally you would
1960 see in phpMyAdmin only this filename. Using transformations you can transform
1961 that filename into a HTML link, so you can click inside of the phpMyAdmin
1962 structure on the field's link and will see the file displayed in a new browser
1963 window. Using transformation options you can also specify strings to
1964 append/prepend to a string or the format you want the output stored in.</p>
1966 <p> For a general overview of all available transformations and their options,
1967 you can consult your
1968 <i>&lt;www.your-host.com&gt;/&lt;your-install-dir&gt;/transformation_overview.php</i>
1969 installation.</p>
1971 <p> For a tutorial on how to effectively use transformations, see our
1972 <a href="http://www.phpmyadmin.net/home_page/docs.php">Link section</a> on
1973 the official phpMyAdmin homepage.</p>
1975 <h3 id="transformationshowto">2. Usage</h3>
1977 <p> Go to your <i>tbl_properties_structure.php</i> page (i.e. reached through
1978 clicking on the 'Structure' link for a table). There click on
1979 &quot;Change&quot; (or change icon) and there you will see three new fields at
1980 the end of the line. They are called 'MIME-type', 'Browser transformation' and
1981 'Transformation options'.</p>
1983 <ul><li>The field 'MIME-type' is a dropdown field. You have the options to leave that field
1984 empty or to use 'auto' [this feature is not yet available]. Please note that
1985 transformations are inactive as long as no MIME-type is selected.</li>
1987 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
1988 hopefully growing amount of pre-defined transformations. See below for information on
1989 how to build your own transformation.<br />
1991 There are global transformations and mimetype-bound transformations. Global transformations
1992 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
1993 Mimetype-bound transformations usually only operate on a certain mimetype. There are
1994 transformations which operate on the main mimetype (like 'image'), which will most likely
1995 take the subtype into regard, and those who only operate on a
1996 specific subtype (like 'image/jpeg').<br />
1998 You can use transformations on mimetypes for which the function was not defined for. There
1999 is no security check for you selected the right transformation, so take care of what the
2000 output will be like.</li>
2002 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2003 transform-function specific options here. Usually the transforms can operate with default
2004 options, but it is generally a good idea to look up the overview to see which options are
2005 necessary.<br />
2007 Much like the ENUM/SET-Fields, you have to split up several options using the format
2008 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2009 parsed as an array, leaving the first value the first element in the array, and so
2010 forth.<br />
2012 If you want to specify a MIME character set you can define it in the transformation_options.
2013 You have to put that outside of the pre-defined options of the specific mime-transform,
2014 as the last value of the set. Use the format "'; charset=XXX'". If you use a transform,
2015 for which you can specify 2 options and you want to append a character set, enter "'first
2016 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2017 the parameters: "'','','charset=us-ascii'".</li>
2018 </ul>
2020 <h3 id="transformationsfiles">3. File structure</h3>
2022 <p> All mimetypes and their transformations are defined through single files in
2023 the directory 'libraries/transformations/'.</p>
2025 <p> They are stored in files to ease up customization and easy adding of new
2026 transformations.</p>
2028 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2029 always work. It makes no sense to apply a transformation to a mimetype, the
2030 transform-function doesn't know to handle.</p>
2032 <p> One can, however, use empty mime-types and global transformations which should work
2033 for many mimetypes. You can also use transforms on a different mimetype they where built
2034 for, but pay attention to option usage as well as what the transformation does to your
2035 field.</p>
2037 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2038 any other transform function and provides some basic functions.</p>
2040 <p> There are 5 possible file names:</p>
2042 <ol><li>A mimetype+subtype transform:<br /><br />
2044 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2046 Please not that mimetype and subtype are separated via '_', which shall
2047 not be contained in their names. The transform function/filename may
2048 contain only characters which cause no problems in the file system as
2049 well as the PHP function naming convention.<br /><br />
2051 The transform function will the be called
2052 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2054 <b>Example:</b><br /><br />
2056 <tt>text_html__formatted.inc.php</tt><br />
2057 <tt>PMA_transform_text_html__formatted()</tt></li>
2059 <li>A mimetype (w/o subtype) transform:<br /><br />
2061 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2063 Please note that there are no single '_' characters.
2064 The transform function/filename may contain only characters which cause
2065 no problems in the file system as well as the PHP function naming
2066 convention.<br /><br />
2068 The transform function will the be called
2069 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2071 <b>Example:</b><br /><br />
2073 <tt>text__formatted.inc.php</tt><br />
2074 <tt>PMA_transform_text__formatted()</tt></li>
2076 <li>A mimetype+subtype without specific transform function<br /><br />
2078 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2080 Please note that there are no '__' characters in the filename. Do not
2081 use special characters in the filename causing problems with the file
2082 system.<br /><br />
2084 No transformation function is defined in the file itself.<br /><br />
2086 <b>Example:</b><br /><br />
2088 <tt>text_plain.inc.php</tt><br />
2089 (No function)</li>
2091 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2093 <tt>[mimetype].inc.php</tt><br /><br />
2095 Please note that there are no '_' characters in the filename. Do not use
2096 special characters in the filename causing problems with the file system.
2097 <br /><br />
2099 No transformation function is defined in the file itself.<br /><br />
2101 <b>Example:</b><br /><br />
2103 <tt>text.inc.php</tt><br />
2104 (No function)</li>
2106 <li>A global transform function with no specific mimetype<br /><br />
2108 <tt>global__[transform].inc.php</tt><br /><br />
2110 The transform function will the be called
2111 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2113 <b>Example:</b><br /><br />
2115 <tt>global__formatted</tt><br />
2116 <tt>PMA_transform_global__formatted()</tt></li>
2117 </ol>
2119 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2120 transform function.</p>
2122 <p> All filenames containing no '__' in themselves are not shown as valid transform
2123 functions in the dropdown.</p>
2125 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2126 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2127 without a transform function. Also note the introduction of a function description in
2128 the language files. For each function a $strTransformation_[filename without .inc.php]
2129 has to exist.</p>
2131 <p> You can use the template generator to generate new functions and entries in the
2132 language file.</p>
2134 <p> To create a new transform function please see
2135 <tt>libraries/transformations/template_generator.sh</tt>.
2136 To create a new, empty mimetype please see
2137 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2139 <p> A transform function always gets passed three variables:</p>
2141 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2142 you want to transform.</li>
2143 <li><b>$options</b> - Contains any user-passed options to a transform function
2144 as an array.</li>
2145 <li><b>$meta</b> - Contains an object with field information to your column.
2146 The data is drawn from the output of the
2147 <a href="http://www.php.net/mysql_fetch_field">mysql_fetch_field()</a>
2148 function. This means, all object properties described on the
2149 <a href="http://www.php.net/mysql_fetch_field">manual page</a> are
2150 available in this variable and can be used to transform a field accordingly
2151 to unsigned/zerofill/not_null/... properties.<br />
2152 The $meta-&gt;mimetype variable contains the original MIME-type of the
2153 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2154 </ol>
2156 <!-- FAQ -->
2157 <h2 id="faq">FAQ - Frequently Asked Questions</h2>
2159 <ol><li><a href="#faqserver">Server</a></li>
2160 <li><a href="#faqconfig">Configuration</a></li>
2161 <li><a href="#faqlimitations">Known limitations</a></li>
2162 <li><a href="#faqmultiuser">ISPs, multi-user installations</a></li>
2163 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2164 <li><a href="#faqusing">Using phpMyAdmin</a></li>
2165 <li><a href="#faqproject">phpMyAdmin project</a></li>
2166 <li><a href="#faqsecurity">Security</a></li>
2167 </ol>
2169 <p> Please have a look at our
2170 <a href="http://www.phpmyadmin.net/home_page/docs.php">Link section</a> on
2171 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2172 features and or interface.</p>
2174 <h3 id="faqserver">Server</h3>
2176 <h4 id="faq1_1">
2177 <a href="#faq1_1">1.1 I'm running PHP 4+ and my server is crashing each time a specific
2178 action is required or phpMyAdmin sends a blank page or a page full of
2179 cryptic characters to my browser, what can I do?</a></h4>
2181 <p> There are some known PHP bugs with output buffering and compression.<br />
2182 Try to set the <a href="#cfg_OBGzip" class="configrule">$cfg['OBGzip']</a>
2183 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2184 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2185 configuration file.<br />
2186 Furthermore, we know about such problems connected to the release
2187 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2188 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2190 <h4 id="faq1_2">
2191 <a href="#faq1_2">1.2 My Apache server crashes when using phpMyAdmin.</a></h4>
2193 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2194 See also the
2195 <a href="#faq1_1"><abbr title="Frequently Asked Questions">FAQ</abbr> 1.1</a>
2196 entry about PHP bugs with output buffering.<br />
2197 If your server keeps crashing, please ask for help in the various Apache
2198 support groups.</p>
2200 <h4 id="faq1_3">
2201 <a href="#faq1_3">1.3 I'm running phpMyAdmin with "cookie" authentication
2202 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2203 script: I'm always displayed the login screen.</a></h4>
2205 <p> This is a known PHP bug (see this
2206 <a href="http://bugs.php.net/bug.php?id=16626">bug report</a>) from the
2207 official PHP bug database. It means there is and won't be any phpMyAdmin
2208 fix against it because there is no way to code a fix.</p>
2210 <h4 id="faq1_4">
2211 <a href="#faq1_4">1.4 Using phpMyAdmin on
2212 <abbr title="Internet Information Services">IIS</abbr>, I'm displayed the
2213 error message: &quot;The specified <abbr title="Common Gateway Interface">CGI</abbr>
2214 application misbehaved by not returning a complete set of
2215 <abbr title="HyperText Transfer Protocol">HTTP</abbr> headers ...&quot;.</a>
2216 </h4>
2218 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2219 Have a look at the last message in this
2220 <a href="http://bugs.php.net/bug.php?id=12061">bug report</a> from the
2221 official PHP bug database.</p>
2223 <h4 id="faq1_5">
2224 <a href="#faq1_5">1.5 Using phpMyAdmin on
2225 <abbr title="Internet Information Services">IIS</abbr>, I'm facing crashes
2226 and/or many error messages with the
2227 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or advanced authentication
2228 mode.</a></h4>
2230 <p> This is a known problem with the PHP
2231 <abbr title="Internet Server Application Programming Interface">ISAPI</abbr>
2232 filter: it's not so stable. Please use instead the cookie authentication mode.
2233 </p>
2235 <h4 id="faq1_6">
2236 <a href="#faq1_6">1.6 I can't use phpMyAdmin on PWS: nothing is displayed!</a></h4>
2238 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2239 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2240 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2241 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2242 <i>left.php</i> and <i>libraries/common.lib.php</i>.</p>
2244 <h4 id="faq1_7">
2245 <a href="#faq1_7">1.7 How can I GZip or Bzip a dump or a
2246 <abbr title="comma seperated values">CSV</abbr> export? It does not seem to
2247 work.</a></h4>
2249 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2250 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2251 or not, and so on). So, you must have PHP4&nbsp;>=&nbsp;4.0.4 and Zlib/Bzip2
2252 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2253 We faced PHP crashes when trying to download a dump with MS Internet
2254 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2255 this case you should switch to the release version of PHP 4.2.0.</p>
2257 <h4 id="faq1_8">
2258 <a href="#faq1_8">1.8 I cannot insert a text file in a table, and I get
2259 an error about safe mode being in effect.</a></h4>
2261 <p> Your uploaded file is saved by PHP in the &quot;upload dir&quot;, as
2262 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2263 the system default is <i>/tmp</i>).<br />
2264 We recommend the following setup for Apache servers running in safe mode,
2265 to enable uploads of files while being reasonably secure:</p>
2267 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2268 <li>give ownership to the Apache server's user.group:
2269 <tt>chown apache.apache /tmp/php</tt></li>
2270 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2271 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2272 <li>restart Apache</li>
2273 </ul>
2275 <h4 id="faq1_9">
2276 <a href="#faq1_9">1.9 I'm having troubles when uploading files. In
2277 general file uploads don't work on my system and uploaded files have a
2278 <tt>Content-Type:</tt> header in the first line.</a></h4>
2280 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2281 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2282 So the problem is that this package has a serious bug that was corrected
2283 ages ago in PHP (2001-01-28: see
2284 <a href="http://www.php.net/bugs.php?id=8966">PHP's bug tracking system</a>
2285 for more details). The problem is that the bugged package is still
2286 available though it was corrected (see
2287 <a href="http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=24933">RedHat's BugZilla</a>
2288 for more details).<br />
2289 So please download
2290 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2291 and the problem should go away.<br />
2292 And that fixes the \r\n problem with file uploads!</p>
2294 <h4 id="faq1_10">
2295 <a href="#faq1_10">1.10 I'm having troubles when uploading files with
2296 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2297 I'm using the Apache server.</a></h4>
2299 <p> As suggested by &quot;Rob M&quot; in the phpWizard forum, add this line to
2300 your <i>httpd.conf</i>:</p>
2302 <pre>SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown</pre>
2304 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2306 <h4 id="faq1_11">
2307 <a href="#faq1_11">1.11 I get an 'open_basedir restriction' while
2308 uploading a file from the query box.</a></h4>
2310 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2311 restrictions. Assuming that the restriction allows you to open files in the
2312 current directory ('.'), all you have to do is create a 'tmp' directory
2313 under the phpMyAdmin install directory, with permissions 777 and the same
2314 owner as the owner of your phpMyAdmin directory. The uploaded files will
2315 be moved there, and after execution of your
2316 <abbr title="structured query language">SQL</abbr> commands, removed.</p>
2318 <h4 id="faq1_12">
2319 <a href="#faq1_12">1.12 I have lost my MySQL root password, what can I do?</a></h4>
2321 <p> The MySQL manual explains how to
2322 <a href="http://www.mysql.com/doc/R/e/Resetting_permissions.html">
2323 reset the permissions</a>.</p>
2325 <h4 id="faq1_13">
2326 <a href="#faq1_13">1.13 I get an error 'No
2327 <abbr title="structured query language">SQL</abbr> query' when trying to
2328 execute a bookmark.</a></h4>
2330 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2331 cannot access the uploaded query.</p>
2333 <h4 id="faq1_14">
2334 <a href="#faq1_14">1.14 I get an error 'No
2335 <abbr title="structured query language">SQL</abbr> query' when trying to
2336 submit a query from the convenient text area.</a></h4>
2338 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2339 and try to increase it.</p>
2341 <h4 id="faq1_15">
2342 <a href="#faq1_15">1.15 I have problems with <i>mysql.user</i> field names.</a>
2343 </h4>
2345 <p> In older MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2346 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2347 names to align with current standards.</p>
2349 <h4 id="faq1_16">
2350 <a href="#faq1_16">1.16 I cannot upload big dump files (memory,
2351 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or timeout problems).</a>
2352 </h4>
2354 <p> Starting with version 2.7.0, the import engine has been re&#8211;written and these
2355 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2356 to take advantage of the new import features.</p>
2358 <p> The first things to check (or ask your host provider to check) are the
2359 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2360 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2361 All of these three settings limit the maximum size of data that can be
2362 submitted and handled by PHP. One user also said that post_max_size
2363 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2365 There exist several workarounds if your upload is too big or your
2366 hosting provider is unwilling to change the settings:</p>
2368 <ul><li>Look at the <a href="#cfg_UploadDir" class="configrule">$cfg['UploadDir']</a>
2369 feature. This allows one to
2370 upload a file to the server via scp, ftp, or your favorite file transfer
2371 method. PhpMyAdmin is then able to import the files from the temporary
2372 directory. More information is available in the <a href="#config">Configuration
2373 section</a> of this document.</li>
2374 <li>Using a utility (such as <a href="http://www.ozerov.de/bigdump.php">
2375 BigDump</a>) to split the files before uploading. We cannot support this
2376 or any third party applications, but are aware of users having success
2377 with it.</li>
2378 <li>If you have shell (command line) access, use MySQL to import the files
2379 directly. You can do this by issuing the &quot;source&quot; command from
2380 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2381 </ul>
2383 <h4 id="faq1_17">
2384 <a id="faqmysqlversions" href="#faq1_17">1.17 Which MySQL versions does phpMyAdmin
2385 support?</a></h4>
2387 <p> All MySQL versions from 3.23.32 till 5.0 (except for 4.1.0 and 4.1.1) are
2388 fully supported. Please note that the older your MySQL version is, the more
2389 limitations you will have to face.<br />
2390 phpMyAdmin may connect to your MySQL server using php's classic
2391 <a href="http://php.net/mysql">MySQL extension</a> as well as the
2392 <a href="http://php.net/mysqli">improved MySQL extension (MySQLi)</a> that
2393 is available in php 5.0.<br />
2394 Either way, the developers of both extensions recommend to use the classic
2395 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2396 When compiling php, we strongly recommend that you manually link the MySQL
2397 extension of your choice to a MySQL client library of at least the same
2398 minor version since the one that is bundled with some php distributions is
2399 rather old and might cause problems <a href="#faq1_17a">
2400 (see <abbr title="Frequently Asked Questions">FAQ</abbr> 1.17a)</a>.
2401 If your webserver is running on a windows system, you might want to try
2402 MySQL's
2403 <a href="http://dev.mysql.com/downloads/connector/php/">Connector/PHP</a>
2404 instead of the MySQL / MySQLi extensions that are bundled with the official
2405 php Win32 builds.
2406 <br />
2407 MySQL&nbsp;5.1 is not yet supported.</p>
2409 <h5 id="faq1_17a">
2410 <a href="#faq1_17a">1.17a I cannot connect to the MySQL server. It always returns the error
2411 message, &quot;Client does not support authentication protocol requested
2412 by server; consider upgrading MySQL client&quot;</a></h5>
2414 <p> You tried to access MySQL with an old MySQL client library. The version of
2415 your MySQL client library can be checked in your phpinfo() output.
2416 In general, it should have at least the same minor version as your server
2417 - as mentioned in <a href="#faq1_17">
2418 <abbr title="Frequently Asked Questions">FAQ</abbr> 1.17</a>.<br /><br />
2420 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2421 changed the authentication hash and your PHP is trying to use the old method.
2422 The proper solution is to use the <a href="http://www.php.net/mysqli">mysqli extension</a>
2423 with the proper client library to match your MySQL installation. Your
2424 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2425 More information (and several workarounds) are located in the
2426 <a href="http://dev.mysql.com/doc/mysql/en/old-client.html">MySQL Documentation</a>.
2427 </p>
2429 <h4 id="faq1_18">
2430 <a href="#faq1_18">1.18 I'm running MySQL&nbsp;&lt;=&nbsp;4.0.1 having
2431 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2432 capital letter in its name it is changed to lowercase as it should. But
2433 if I try to DROP this table MySQL is unable to find the corresponding
2434 file.</a></h4>
2436 <p> This is a bug of MySQL&nbsp;&lt;=&nbsp;4.0.1. Please upgrade to at least
2437 MySQL&nbsp;4.0.2 or turn off your <tt>lower_case_table_names</tt>
2438 directive.</p>
2440 <h4 id="faq1_19">
2441 <a href="#faq1_19">1.19 I can't run the &quot;display relations&quot; feature because the
2442 script seems not to know the font face I'm using!</a></h4>
2444 <p> The &quot;FPDF&quot; library we're using for this feature requires some
2445 special files to use font faces.<br />
2446 Please refers to the <a href="http://www.fpdf.org/">FPDF manual</a> to build
2447 these files.</p>
2449 <h4 id="faqmysql">
2450 <a href="#faqmysql">1.20 I receive the error &quot;cannot load MySQL extension, please
2451 check PHP Configuration&quot;.</a></h4>
2453 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2454 &quot;MySQL extension&quot;. This extension may be part of the PHP
2455 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2456 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2457 to load the extension but failed.<br /><br />
2459 Usually, the problem is solved by installing a software package called
2460 &quot;PHP-MySQL&quot; or something similar.</p>
2462 <h4 id="faq1_21">
2463 <a href="#faq1_21">1.21 I am running the
2464 <abbr title="Common Gateway Interface">CGI</abbr> version of PHP under Unix,
2465 and I cannot log in using cookie auth.</a></h4>
2467 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2469 <h4 id="faq1_22">
2470 <a href="#faq1_22">1.22 I don't see the &quot;Location of text file&quot; field,
2471 so I cannot upload.</a></h4>
2473 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2474 parameter is not set to &quot;on&quot;.</p>
2476 <h4 id="faq1_23">
2477 <a href="#faq1_23">1.23 I'm running MySQL on a Win32 machine. Each time I create
2478 a new table the table and field names are changed to lowercase!</a></h4>
2480 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2481 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2482 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2483 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2484 directory and add the following line to the group [mysqld]:</p>
2486 <pre>set-variable = lower_case_table_names=0</pre>
2488 <p> Next, save the file and restart the MySQL service. You can always check the
2489 value of this directive using the query</p>
2491 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2493 <h4 id="faq1_24">
2494 <a href="#faq1_24">1.24 Some characters are being truncated in my queries, or I
2495 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2497 <p> This is a <a href="http://bugs.php.net/bug.php?id=19404">PHP 4.2.3 bug</a>.
2498 </p>
2500 <h4 id="faq1_25">
2501 <a href="#faq1_25">1.25 I am running Apache with mod_gzip-1.3.26.1a on Windows XP,
2502 and I get problems, such as undefined variables when I run a
2503 <abbr title="structured query language">SQL</abbr> query.</a></h4>
2505 <p> A tip from Jose Fandos: put a comment on the following two lines
2506 in httpd.conf, like this:</p>
2508 <pre>
2509 # mod_gzip_item_include file \.php$
2510 # mod_gzip_item_include mime "application/x-httpd-php.*"
2511 </pre>
2513 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2514 PHP scripts. Of course you have to restart Apache.</p>
2516 <h4 id="faq1_26">
2517 <a href="#faq1_26">1.26 I just installed phpMyAdmin in my document root of
2518 <abbr title="Internet Information Services">IIS</abbr> but
2519 I get the error &quot;No input file specified&quot; when trying to
2520 run phpMyAdmin.</a></h4>
2522 <p> This is a permission problem. Right-click on the phpmyadmin folder
2523 and choose properties. Under the tab Security, click on &quot;Add&quot;
2524 and select the user &quot;IUSR_machine&quot; from the list. Now set his
2525 permissions and it should work.</p>
2527 <h4 id="faq1_27">
2528 <a href="#faq1_27">1.27 I get empty page when I want to view huge page (eg.
2529 db_details_structure.php with plenty of tables).</a></h4>
2531 <p> This is a <a href="http://bugs.php.net/21079">PHP bug</a> that occur when
2532 GZIP output buffering is enabled. If you turn off it (by
2533 <a href="#cfg_OBGzip" class="configrule">$cfg['OBGzip'] = false</a>
2534 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2535 PHP&nbsp;5.0.0.</p>
2537 <h4 id="faq1_28">
2538 <a href="#faq1_28">1.28 My MySQL server sometimes refuses queries and returns the
2539 message 'Errorcode: 13'. What does this mean?</a></h4>
2541 <p> This can happen due to a MySQL bug when having database / table names with
2542 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2543 To fix this, turn off this directive, convert all database and table names
2544 to lower case and turn it on again. Alternatively, there's a bug-fix
2545 available starting with MySQL&nbsp;3.23.56 / 4.0.11-gamma.</p>
2547 <h4 id="faq1_29">
2548 <a href="#faq1_29">1.29 When I create a table or modify a field, I get an error
2549 and the fields are duplicated.</a></h4>
2551 <p> It is possible to configure Apache in such a way that PHP has problems
2552 interpreting .php files.</p>
2554 <p> The problems occur when two different (and conflicting) set of directives
2555 are used:</p>
2557 <pre>
2558 SetOutputFilter PHP
2559 SetInputFilter PHP
2560 </pre>
2562 <p> and</p>
2564 <pre>AddType application/x-httpd-php .php</pre>
2566 <p> In the case we saw, one set of directives was in
2567 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2568 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2569 The recommended way is with <tt>AddType</tt>, so just comment out
2570 the first set of lines and restart Apache:</p>
2572 <pre>
2573 #SetOutputFilter PHP
2574 #SetInputFilter PHP
2575 </pre>
2577 <h4 id="faq1_30">
2578 <a href="#faq1_30">1.30 I get the error &quot;left.php: Missing hash&quot;.</a></h4>
2580 <p> This problem is known to happen when the server is running Turck MMCache
2581 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2583 <h4 id="faq1_31">
2584 <a href="#faq1_31">1.31 Does phpMyAdmin support php5?</a></h4>
2586 <p> Yes.<br />
2587 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2588 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2589 <tt>error_reporting</tt> settings.
2590 </p>
2592 <h4 id="faq1_32">
2593 <a href="#faq1_32">1.32 Can I use <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication with <abbr title="Internet Information Services">IIS</abbr>?</a></h4>
2595 <p> Yes. This procedure was tested with phpMyAdmin 2.6.1, PHP 4.3.9 in <abbr title="Internet Server Application Programming Interface">ISAPI</abbr>
2596 mode under <abbr title="Internet Information Services">IIS</abbr> 5.1.</p>
2598 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2599 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2600 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2601 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2602 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2603 enabled.) Click <tt>OK</tt>.</li>
2604 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2605 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2606 </ol>
2608 <h4 id="faq1_33">
2609 <a href="#faq1_33">1.33 Is there a problem with the mysqli extension when running
2610 PHP 5.0.4 on 64-bit systems?</a></h4>
2612 <p> Yes. This problem affects phpMyAdmin (&quot;Call to undefined function
2613 pma_reloadnavigation&quot;), so upgrade your PHP to the next version.</p>
2615 <h4 id="faq1_34">
2616 <a href="#faq1_34">1.34 Can I access directly to database or table pages?</a></h4>
2618 <p> Yes. Out of the box, you can use <abbr title="Uniform Resource Locator">URL</abbr>s like
2619 http://server/phpMyAdmin/index.php?db=database&amp;table=table&amp;target=script.
2620 Table and script parts are optional. If you want
2621 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2622 some configuration. Following lines apply only for <a
2623 href="http://httpd.apache.org">Apache</a> web server. First make sure,
2624 that you have enabled some features within global configuration. You need
2625 <code>Options FollowSymLinks</code> and <code>AllowOverride
2626 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2627 you need mod_rewrite to be enabled. Then you just need to create following
2628 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2629 (don't forget to change directory name inside of it):</p>
2631 <pre>
2632 RewriteEngine On
2633 RewriteBase /path_to_phpMyAdmin
2634 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&amp;table=$2&amp;target=$3 [R]
2635 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&amp;target=$2 [R]
2636 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&amp;table=$2 [R]
2637 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2638 </pre>
2640 <h4 id="faq1_35">
2641 <a href="#faq1_35">1.35 Can I use <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication with Apache <abbr title="Common Gateway Interface">CGI</abbr>?</a></h4>
2643 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2644 following rewrite rule:</p>
2646 <pre>
2647 RewriteEngine On
2648 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2649 </pre>
2651 <h4 id="faq1_36">
2652 <a href="#faq1_36">1.36 I get an error &quot;500 Internal Server Error&quot;.</a>
2653 </h4>
2655 There can be many explanations to this and a look at your server's
2656 error log file might give a clue.
2657 </p>
2659 <h4 id="faq1_37">
2660 <a href="#faq1_37">1.37 I run phpMyAdmin on cluster of different machines and
2661 password encryption in cookie auth doesn't work.</a></h4>
2663 <p> If your cluster consist of different architectures, PHP code used for
2664 encryption/decryption won't work correct. This is caused by use of
2665 pack/unpack functions in code. Only solution is to use mcrypt extension
2666 which works fine in this case.</p>
2668 <h3 id="faqconfig">Configuration</h3>
2670 <h4 id="faq2_1">
2671 <a href="#faq2_1">2.1 The error message &quot;Warning: Cannot add header information -
2672 headers already sent by ...&quot; is displayed, what's the problem?</a></h4>
2674 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
2675 (I.E. no blank lines, no spaces, no characters...) neither before the
2676 <tt>&lt;?php</tt> tag at the beginning, neither after the <tt>?&gt;</tt>
2677 tag at the end.</p>
2679 <h4 id="faq2_2">
2680 <a href="#faq2_2">2.2 phpMyAdmin can't connect to MySQL. What's wrong?</a></h4>
2682 <p> Either there is an error with your PHP setup or your username/password is
2683 wrong. Try to make a small script which uses mysql_connect and see if it
2684 works. If it doesn't, it may be you haven't even compiled MySQL support
2685 into PHP.</p>
2687 <h4 id="faq2_3">
2688 <a href="#faq2_3">2.3 The error message &quot;Warning: MySQL Connection Failed: Can't
2689 connect to local MySQL server through socket '/tmp/mysql.sock'
2690 (111) ...&quot; is displayed. What can I do?</a></h4>
2692 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
2694 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
2695 In your <i>php.ini</i> you will find a line</p>
2697 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
2699 <p> change it to</p>
2701 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
2703 <p> Then restart apache and it will work.</p>
2705 <p> Here is a fix suggested by Brad Ummer:</p>
2707 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
2708 To do this, telnet to your server and go to the MySQL bin directory. In
2709 this directory there should be a file named <i>mysqladmin</i>. Type
2710 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
2711 info about your MySQL server, including the socket
2712 (<i>/tmp/mysql.sock</i>, for example).</li>
2713 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
2714 phpMyAdmin, you need to complete the socket information in the
2715 <i>config.inc.php</i>.<br />
2716 For example:
2717 <a href="#cfg_Servers_socket" class="configrule">
2718 $cfg['Servers'][$i]['socket']&nbsp;=&nbsp;'/tmp/mysql.sock';</a>
2719 <br /><br />
2721 Please also make sure that the permissions of this file allow to be readable
2722 by your webserver (i.e. '0755').</li>
2723 </ul>
2725 <p> Have also a look at the
2726 <a href="http://www.mysql.com/doc/C/a/Can_not_connect_to_server.html">
2727 corresponding section of the MySQL documentation</a>.</p>
2729 <h4 id="faq2_4">
2730 <a href="#faq2_4">2.4 Nothing is displayed by my browser when I try to run phpMyAdmin,
2731 what can I do?</a></h4>
2733 <p> Try to set the <a href="#cfg_OBGzip" class="configrule">$cfg['OBGZip']</a>
2734 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
2735 sometime.<br />
2736 Also have a look at your PHP version number: if it contains &quot;4.0b...&quot;
2737 it means you're running a beta version of PHP. That's not a so good idea,
2738 please upgrade to a plain revision.</p>
2740 <h4 id="faq2_5">
2741 <a href="#faq2_5">2.5 Each time I want to insert or change a record or drop a database
2742 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
2743 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
2745 <p> Check the value you set for the
2746 <a href="#cfg_PmaAbsoluteUri" class="configrule">$cfg['PmaAbsoluteUri']</a>
2747 directive in the phpMyAdmin configuration file.</p>
2749 <h4 id="faq2_6">
2750 <a href="#faq2_6">2.6 I get an &quot;Access denied for user: 'root@localhost' (Using
2751 password: YES)&quot;-error when trying to access a MySQL-Server on a
2752 host which is port-forwarded for my localhost.</a></h4>
2754 <p> When you are using a port on your localhost, which you redirect via
2755 port-forwarding to another host, MySQL is not resolving the localhost
2756 as expected.<br />
2757 Erik Wasser explains: The solution is: if your host is &quot;localhost&quot;
2758 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
2759 connection for speeding up things. And that doesn't work in this configuration
2760 with port forwarding.<br />
2761 If you enter "127.0.0.1" as hostname, everything is right and MySQL uses the
2762 <abbr title="Transmission Control Protocol">TCP</abbr> connection.</p>
2764 <h4 id="faqthemes"><a href="#faqthemes">2.7 Using and creating themes</a></h4>
2766 <p> Themes are configured with
2767 <a href="#cfg_ThemePath" class="configrule">$cfg['ThemePath']</a>,
2768 <a href="#cfg_ThemeManager" class="configrule">$cfg['ThemeManager']</a> and
2769 <a href="#cfg_ThemeDefault" class="configrule">$cfg['ThemeDefault']</a>.<br />
2770 <br />
2771 Under <a href="#cfg_ThemePath" class="configrule">$cfg['ThemePath']</a>, you
2772 should not delete the directory &quot;original&quot; or its underlying
2773 structure, because this is the system theme used by phpMyAdmin.
2774 &quot;original&quot; contains all images and styles, for backwards
2775 compatibility and for all themes that would not include images or css-files.
2776 <br /><br />
2778 If <a href="#cfg_ThemeManager" class="configrule">$cfg['ThemeManager']</a>
2779 is enabled, you can select your favorite theme on the main page. Your
2780 selected theme will be stored in a cookie.<br /><br /></p>
2782 <p> To create a theme:</p>
2784 <ul><li>make a new subdirectory (for example &quot;your_theme_name&quot;) under
2785 <a href="#cfg_ThemePath" class="configrule">$cfg['ThemePath']</a>
2786 (by default <tt>themes</tt>)</li>
2787 <li>copy the files and directories from &quot;original&quot; to
2788 &quot;your_theme_name&quot;</li>
2789 <li>edit the css-files in &quot;your_theme_name/css&quot;</li>
2790 <li>put your new images in &quot;your_theme_name/img&quot;</li>
2791 <li>edit <tt>layout.inc.php</tt> in &quot;your_theme_name&quot;</li>
2792 <li>edit <tt>info.inc.php</tt> in &quot;your_theme_name&quot; to
2793 contain your chosen theme name, that will be visible in user interface</li>
2794 <li>make a new screenshot of your theme and save it under
2795 &quot;your_theme_name/screen.png&quot;</li>
2796 </ul>
2798 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
2799 theme verbose name, theme generation and theme version. These versions and
2800 generations are enumerated from 1 and do not have any direct dependence on
2801 phpMyAdmin version. Themes within same generation should be backwards
2802 compatible - theme with version 2 should work in phpMyAdmin requiring
2803 version 1. Themes with different generation are incompatible.</p>
2805 <p> If you do not want to use your own symbols and buttons, remove the
2806 directory &quot;img&quot; in &quot;your_theme_name&quot;. phpMyAdmin will
2807 use the default icons and buttons (from the system-theme &quot;original&quot;).
2808 </p>
2810 <h4 id="faqmissingparameters">
2811 <a href="#faqmissingparameters">2.8 I get &quot;Missing parameters&quot; errors,
2812 what can I do?</a></h4>
2814 <p> Here are a few points to check:</p>
2816 <ul><li>In <tt>config.inc.php</tt>, try to leave the
2817 <a href="#cfg_PmaAbsoluteUri" class="configrule">$cfg['PmaAbsoluteUri']</a>
2818 directive empty. See also
2819 <a href="#faq4_7"><abbr title="Frequently Asked Questions">FAQ</abbr> 4.7</a>.
2820 </li>
2821 <li>Maybe you have a broken PHP installation or you need to upgrade
2822 your Zend Optimizer. See
2823 <a href="http://bugs.php.net/bug.php?id=31134">
2824 http://bugs.php.net/bug.php?id=31134</a>.
2825 </li>
2826 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
2827 set to the default (200) or another low value, you could get this
2828 error if your table has a high number of columns. Adjust this setting
2829 accordingly. (Thanks to Klaus Dorninger for the hint).
2830 </li>
2831 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
2832 of &quot;;&quot; will cause this error. Replace it with &quot;&amp;;&quot;.
2833 </li>
2834 </ul>
2836 <h3 id="faqlimitations">Known limitations</h3>
2838 <h4 id="login_bug">
2839 <a href="#login_bug">3.1 When using
2840 <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication, an user
2841 who logged out can not log in again in with the same nick.</a></h4>
2843 <p> This is related to the authentication mechanism (protocol) used by
2844 phpMyAdmin. To bypass this problem: just close all the opened
2845 browser windows and then go back to phpMyAdmin. You should be able to
2846 log in again.</p>
2848 <h4 id="faq3_2">
2849 <a href="#faq3_2">3.2 When dumping a large table in compressed mode, I get a memory
2850 limit error or a time limit error.</a></h4>
2852 <p> Compressed dumps are built in memory and because of this are limited to
2853 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
2854 using
2855 <a href="#cfg_CompressOnFly" class="configrule">$cfg['CompressOnFly']</a>
2856 (enabled by default). Zip exports can not be handled this way, so if you need
2857 Zip files for larger dump, you have to use another way.</p>
2859 <h4 id="faq3_3">
2860 <a href="#faq3_3">3.3 With InnoDB tables, I lose foreign key relationships when I rename
2861 or alter a table.</a></h4>
2863 <p> This seems to be a InnoDB bug (fixed in MySQL 3.23.50?).</p>
2865 <h4 id="faq3_4">
2866 <a href="#faq3_4">3.4 I am unable to import dumps I created with the mysqldump tool
2867 bundled with the MySQL server distribution.</a></h4>
2869 <p> The problem is that mysqldump creates invalid comments like this:</p>
2871 <pre>
2872 -- MySQL dump 8.22
2874 -- Host: localhost Database: database
2875 ---------------------------------------------------------
2876 -- Server version 3.23.54
2877 </pre>
2879 <p> The invalid part of the code is the horizontal line made of dashes that
2880 appears once in every dump created with mysqldump. If you want to run your
2881 dump you have to turn it into valid MySQL. This means, you have to add a
2882 whitespace after the first two dashes of the line or add a # before it:
2883 <br />
2884 <code>
2885 -- -------------------------------------------------------<br />
2886 </code>
2887 or<br />
2888 <code>
2889 #---------------------------------------------------------
2890 </code>
2891 </p>
2893 <h4 id="faq3_5">
2894 <a href="#faq3_5">3.5 When using nested folders there are some multiple hierarchies
2895 displayed in a wrong manner?!</a> (<a href="#cfg_LeftFrameTableSeparator"
2896 class="configrule">$cfg['LeftFrameTableSeparator']</a>)</h4>
2898 <p> Please note that you should not use the separating string multiple times
2899 without any characters between them, or at the beginning/end of your table
2900 name. If you have to, think about using another TableSeparator or disabling
2901 that feature</p>
2903 <h4 id="faq3_6">
2904 <a href="#faq3_6">3.6 What is currently not supported in phpMyAdmin about InnoDB?</a></h4>
2906 <p> In Relation view, being able to choose a table in another database,
2907 or having more than one index field in the foreign key.<br /><br/>
2908 In Query-by-example (Query), automatic generation of the query
2909 LEFT JOIN from the foreign table.<br /><br/>
2910 </p>
2912 <h4 id="faq3_7">
2913 <a href="#faq3_7">3.7 I have table with many (100+) fields and when I try to browse table
2914 I get series of errors like &quot;Warning: unable to parse url&quot;. How
2915 can this be fixed?</a></h4>
2917 Your table neither have a primary key nor an unique one, so we must use a
2918 long expression to identify this row. This causes problems to parse_url
2919 function. The workaround is to create a primary or unique key.
2920 <br />
2921 </p>
2923 <h4 id="faq3_8">
2924 <a href="#faq3_8">3.8 I cannot use (clickable) HTML-forms in fields where I put
2925 a MIME-Transformation onto!</a></h4>
2927 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
2928 nested forms can be put inside the table where phpMyAdmin displays the results.
2929 You can, however, use any form inside of a table if keep the parent
2930 form-container with the target to tbl_row_delete.php and just put your own
2931 input-elements inside. If you use a custom submit input field, the form will
2932 submit itself to the displaying page again, where you can validate the
2933 $HTTP_POST_VARS in a transformation.
2935 For a tutorial on how to effectively use transformations, see our
2936 <a href="http://www.phpmyadmin.net/home_page/docs.php">Link section</a>
2937 on the official phpMyAdmin-homepage.</p>
2939 <h4 id="faq3_9">
2940 <a href="#faq3_9">3.9 I get error messages when using "--sql_mode=ANSI" for the
2941 MySQL server</a></h4>
2943 <p> When MySQL is running in ANSI-compatibility mode, there are some major
2944 differences in how <abbr title="structured query language">SQL</abbr> is
2945 structured (see <a href="http://dev.mysql.com/doc/mysql/en/ANSI_mode.html">
2946 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
2947 the quote-character (") is interpreted as an identifier quote character and
2948 not as a string quote character, which makes many internal phpMyAdmin
2949 operations into invalid <abbr title="structured query language">SQL</abbr>
2950 statements. There is no workaround to this behaviour. News to this item will
2951 be posted in Bug report
2952 <a href="https://sf.net/tracker/index.php?func=detail&amp;aid=816858&amp;group_id=23067&amp;atid=377408">#816858</a>
2953 </p>
2955 <h4 id="faq3_10">
2956 <a href="#faq3_10">3.10 Homonyms and no primary key: When the results of a SELECT display
2957 more that one column with the same value
2958 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two &quot;Smith&quot; values are displayed),
2959 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
2961 <p> Please make sure that your table has a primary key, so that phpMyAdmin
2962 can use it for the Edit and Delete links.</p>
2964 <h4 id="faq3_11">
2965 <a href="#faq3_11">3.11 The number of records for InnoDB tables is not correct.</a></h4>
2967 <p> phpMyAdmin uses a quick method to get the row count, and this method
2968 only returns an approximate count in the case of InnoDB tables. See
2969 <a href="#cfg_MaxExactCount" class="configrule">$cfg['MaxExactCount']</a> for
2970 a way to modify those results, but
2971 this could have a serious impact on performance.</p>
2973 <h4 id="faq3_12">
2974 <a href="#faq3_12">3.12 What are the phpMyAdmin limitations for MySQL 3?</a></h4>
2976 <p> The number of records in queries containing COUNT and GROUP BY is
2977 not correctly calculated. Also, sorting results of a query like
2978 &quot;SELECT * from table GROUP BY&quot; ... is problematic.</p>
2980 <h4 id="faq3_13">
2981 <a href="#faq3_13">3.13 I get an error when entering <tt>USE</tt> followed by a db name
2982 containing an hyphen.
2983 </a></h4>
2985 The tests I have made with current MySQL 4.1.11 API shows that the
2986 API does not accept this syntax for the USE command. Enclosing the
2987 db name with backquotes works. For further confusion, no backquotes
2988 are needed with command-line mysql.
2989 </p>
2991 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
2993 <h4 id="faq4_1">
2994 <a href="#faq4_1">4.1 I'm an <abbr title="Internet service provider">ISP</abbr>. Can I setup one central copy of phpMyAdmin or do I
2995 need to install it for each customer.
2996 </a></h4>
2998 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
2999 your users. The development of this feature was kindly sponsored by
3000 NetCologne GmbH.
3001 This requires a properly setup MySQL user management and phpMyAdmin
3002 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3003 &quot;Using <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication&quot;.
3004 </p>
3006 <h4 id="faq4_2">
3007 <a href="#faq4_2">4.2 What's the preferred way of making phpMyAdmin secure against evil
3008 access.
3009 </a></h4>
3011 This depends on your system.<br />
3012 If you're running a server which cannot be accessed by other people, it's
3013 sufficient to use the directory protection bundled with your webserver
3014 (with Apache you can use <i>.htaccess</i> files, for example).<br />
3015 If other people have telnet access to your server, you should use
3016 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3017 <br /><br />
3018 Suggestions:
3019 </p>
3020 <ul>
3021 <li>
3022 Your <i>config.inc.php</i> file should be <tt>chmod 660</tt>.
3023 </li>
3024 <li>
3025 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3026 is a user whose password is only known to you, and apache is the
3027 group under which Apache runs.
3028 </li>
3029 <li>
3030 You should use PHP safe mode, to protect from other users that try
3031 to include your <i>config.inc.php</i> in their scripts.
3032 </li>
3033 </ul>
3035 <h4 id="faq4_3">
3036 <a href="#faq4_3">4.3 I get errors about not being able to include a file in
3037 <i>/lang</i> or in <i>/libraries</i>.
3038 </a></h4>
3040 Check <i>php.ini</i>, or ask your sysadmin to check it. The
3041 <tt>include_path</tt> must contain &quot;.&quot; somewhere in it, and
3042 <tt>open_basedir</tt>, if used, must contain &quot;.&quot; and
3043 &quot;./lang&quot; to allow normal operation of phpMyAdmin.
3044 </p>
3046 <h4 id="faq4_4">
3047 <a href="#faq4_4">4.4 phpMyAdmin always gives &quot;Access denied&quot; when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3048 authentication.
3049 </a></h4>
3051 <p> This could happen for several reasons:</p>
3053 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3054 and/or
3055 <a href="#cfg_Servers_controlpass" class="configrule">$cfg['Servers'][$i]['controlpass']</a>
3056 are wrong.</li>
3057 <li>The username/password you specify in the login dialog are invalid.</li>
3058 <li>You have already setup a security mechanism for the
3059 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3060 phpMyAdmin's authentication, so remove it.</li>
3061 </ul>
3063 <h4 id="faq4_5">
3064 <a href="#faq4_5">4.5 Is it possible to let users create their own databases?</a></h4>
3066 <p> Starting with 2.2.5, in the user management page, you can enter a wildcard
3067 database name for a user (for example &quot;joe%&quot;),
3068 and put the privileges you want. For example,
3069 adding <tt>SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX, ALTER</tt>
3070 would let a user create/manage his/her database(s).</p>
3072 <h4 id="faq4_6">
3073 <a href="#faq4_6">4.6 How can I use the Host-based authentication additions?</a></h4>
3075 <p> If you have existing rules from an old .htaccess file, you can take them
3076 and add a username between the <tt>'deny'</tt>/<tt>'allow'</tt> and
3077 <tt>'from'</tt> strings. Using the username wildcard of <tt>'%'</tt> would
3078 be a major benefit here if your installation is suited to using it. Then
3079 you can just add those updated lines into the
3080 <a href="#cfg_Servers_AllowDeny_rules" class="configrule">
3081 $cfg['Servers'][$i]['AllowDeny']['rules']</a> array.</p>
3083 <p> If you want a pre-made sample, you can try this fragment. It stops the
3084 'root' user from logging in from any networks other than the private
3085 network <abbr title="Internet Protocol">IP</abbr> blocks.</p>
3087 <pre>
3088 //block root from logging in except from the private networks
3089 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3090 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3091 'deny root from all',
3092 'allow root from localhost',
3093 'allow root from 10.0.0.0/8',
3094 'allow root from 192.168.0.0/16',
3095 'allow root from 172.16.0.0/12',
3097 </pre>
3099 <h4 id="faq4_7">
3100 <a href="#faq4_7">4.7 Authentication window is displayed more than once, why?</a></h4>
3102 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3103 different than the one set in your
3104 <a href="#cfg_PmaAbsoluteUri" class="configrule">$cfg['PmaAbsoluteUri']</a>.
3105 For example, a missing &quot;www&quot;, or entering with an <abbr title="Internet Protocol">IP</abbr> address
3106 while a domain name is defined in the config file.</p>
3108 <h3 id="faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></h3>
3110 <h4 id="faq5_1">
3111 <a href="#faq5_1">5.1 I get an out of memory error, and my controls are non-functional,
3112 when trying to create a table with more than 14 fields.
3113 </a></h4>
3115 We could reproduce this problem only under Win98/98SE. Testing under
3116 WinNT4 or Win2K, we could easily create more than 60 fields.
3117 <br />
3118 A workaround is to create a smaller number of fields, then come back to
3119 your table properties and add the other fields.
3120 </p>
3122 <h4 id="faq5_2">
3123 <a href="#faq5_2">5.2 With Xitami 2.5b4, phpMyAdmin won't process form fields.</a></h4>
3125 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3126 with each script/website that use forms.<br />
3127 Upgrade or downgrade your Xitami server.
3128 </p>
3130 <h4 id="faq5_3">
3131 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3133 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3134 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3135 don't seem to work.<br />
3137 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3138 the user's temporary directory, so they must be moved before closing
3139 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3141 Testing needs to be done for Konqueror 2.2.2.<br />
3142 </p>
3144 <h4 id="faq5_4">
3145 <a href="#faq5_4">5.4 I can't use the cookie authentication mode because Internet
3146 Explorer never stores the cookies.
3147 </a></h4>
3149 MS Internet Explorer seems to be really buggy about cookies, at least till
3150 version 6. And thanks to Andrew Zivolup we've traced also a PHP 4.1.1 bug
3151 in this area!
3152 <br />
3153 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3154 work!
3155 </p>
3157 <h4 id="faq5_5">
3158 <a href="#faq5_5">5.5 In Internet Explorer 5.0, I get JavaScript errors when browsing my
3159 rows.
3160 </a></h4>
3162 Upgrade to at least Internet Explorer 5.5 SP2.<br />
3163 </p>
3165 <h4 id="faq5_6">
3166 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3167 when trying to modify a row in a table with many fields, or with a text field
3168 </a></h4>
3170 Your table neither have a primary key nor an unique one, so we must use a
3171 long <abbr title="Uniform Resource Locator">URL</abbr> to identify this row. There is a limit on the length of the <abbr title="Uniform Resource Locator">URL</abbr> in
3172 those browsers, and this not happen in Netscape, for example. The
3173 workaround is to create a primary or unique key, or use another browser.
3174 <br />
3175 </p>
3177 <h4 id="faq5_7">
3178 <a href="#faq5_7">5.7 I refresh (reload) my browser, and come back to the welcome
3179 page.
3180 </a></h4>
3182 Some browsers support right-clicking into the frame you want to refresh,
3183 just do this in the right frame.<br />
3184 </p>
3186 <h4 id="faq5_8">
3187 <a href="#faq5_8">5.8 With Mozilla 0.9.7 I have problems sending a query modified in the
3188 query box.
3189 </a></h4>
3191 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3192 Mozilla versions.<br />
3193 </p>
3195 <h4 id="faq5_9">
3196 <a href="#faq5_9">5.9 With Mozilla 0.9.? to 1.0 and Netscape 7.0-PR1 I can't type a
3197 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3198 </a></h4>
3200 This is a Mozilla bug (see bug #26882 at
3201 <a href="http://bugzilla.mozilla.org/">BugZilla</a>).<br />
3202 </p>
3204 <h4 id="faq5_10">
3205 <a href="#faq5_10">5.10 With Netscape 4.75 I get empty rows between each row of data in a
3206 <abbr title="comma seperated values">CSV</abbr> exported file.
3207 </a></h4>
3209 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3210 data in octet-stream mode. Since we can't detect the specific Netscape
3211 version, we cannot workaround this bug.
3212 </p>
3214 <h4 id="faq5_11">
3215 <a href="#faq5_11">5.11 Extended-ASCII characters like German umlauts are displayed
3216 wrong.</a></h4>
3218 <p> Please ensure that you have set your browser's character set to the one of the
3219 language file you have selected on phpMyAdmin's start page.
3220 Alternatively, you can try the auto detection mode that is supported by the
3221 recent versions of the most browsers.</p>
3223 <h4 id="faq5_12">
3224 <a href="#faq5_12">5.12 <acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X: Safari browser changes special characters to
3225 &quot;?&quot;.</a></h4>
3227 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3228 Netscape and Mozilla do not have this problem.</p>
3230 <h4 id="faq5_13">
3231 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3232 I cannot manage two servers: I log in to the first one, then the other one,
3233 but if I switch back to the first, I have to log in on each operation.</a></h4>
3235 <p> This is a bug in Internet Explorer, other browsers do not behave this way.</p>
3237 <h4 id="faq5_14">
3238 <a href="#faq5_14">5.14 Using Opera6, I can manage to get to the authentication,
3239 but nothing happens after that, only a blank screen.</a></h4>
3241 <p> Having <tt>$cfg['QueryFrameJS']</tt> set o <tt>TRUE</tt>, this leads to a
3242 bug in Opera6, because it is not able to interpret frameset definitions
3243 written by JavaScript. Please upgrade your phpMyAdmin installtion or to
3244 Opera7 at least.</p>
3246 <h4 id="faq5_15">
3247 <a href="#faq5_15">5.15 I have display problems with Safari.</a></h4>
3249 <p> Please upgrade to at least version 1.2.3.</p>
3251 <h4 id="faq5_16">
3252 <a href="#faq5_16">5.16 With Internet Explorer, I get &quot;Access is denied&quot;
3253 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3255 <p> Please check the following points:</p>
3256 <ul><li>Maybe you have defined your <tt>PmaAbsoluteUri</tt> setting
3257 in <tt>config.inc.php</tt> to an <abbr title="Internet Protocol">IP</abbr>
3258 address and you are starting
3259 phpMyAdmin with a <abbr title="Uniform Resource Locator">URL</abbr>
3260 containing a domain name, or the reverse situation.</li>
3261 <li>Security settings in IE and/or Microsoft Security Center are
3262 too high, thus blocking scripts execution.</li>
3263 <li>The Windows Firewall is blocking Apache and MySQL. You must
3264 allow <abbr title="HyperText Transfer Protocol">HTTP</abbr> ports
3265 (80 or 443) and MySQL port (usually 3306)
3266 in the &quot;in&quot; and &quot;out&quot; directions.</li>
3267 </ul>
3269 <h4 id="faq5_17">
3270 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3271 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3272 installed in their Firefox is causing the problem.</p>
3274 <h3 id="faqusing">Using phpMyAdmin</h3>
3276 <h4 id="faq6_1">
3277 <a href="#faq6_1">6.1 I can't insert new rows into a table / I can't create a table
3278 - MySQL brings up a <abbr title="structured query language">SQL</abbr>-error.
3279 </a></h4>
3281 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3282 specifying a wrong field-type.<br />
3283 Common errors include:
3284 </p>
3285 <ul>
3286 <li>Using <tt>VARCHAR</tt> without a size argument</li>
3287 <li>Using <tt>TEXT</tt> or <tt>BLOB</tt> with a size argument</li>
3288 </ul>
3290 Also, look at the syntax chapter in the MySQL manual to confirm that your
3291 syntax is correct.
3292 </p>
3294 <h4 id="faq6_2">
3295 <a href="#faq6_2">6.2 When I create a table, I click the Index checkbox for 2 fields and
3296 phpMyAdmin generates only one index with those 2 fields.
3297 </a></h4>
3299 In phpMyAdmin 2.2.0 and 2.2.1, this is the way to create a multi-fields
3300 index. If you want two indexes, create the first one when creating the
3301 table, save, then display the table properties and click the Index link to
3302 create the other index.
3303 </p>
3305 <h4 id="faq6_3">
3306 <a href="#faq6_3">6.3 How can I insert a null value into my table?</a></h4>
3308 Since version 2.2.3, you have a checkbox for each field that can be null.
3309 Before 2.2.3, you had to enter &quot;null&quot;, without the quotes, as the
3310 field's value. Since version 2.5.5, you have to use the checkbox to get
3311 a real NULL value, so if you enter &quot;NULL&quot; this means you want
3312 a literal NULL in the field, and not a NULL value (this works in PHP4).
3313 </p>
3315 <h4 id="faq6_4">
3316 <a href="#faq6_4">6.4 How can I backup my database or table?</a></h4>
3318 <p> Click on a database or table name in the left frame, the properties will be
3319 displayed. Then on the menu, click &quot;Export&quot;, you can dump
3320 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3321 statements that can be used to recreate your database/table.
3322 <br /><br />
3323 You will need to choose &quot;Save as file&quot;, so that phpMyAdmin can
3324 transmit the resulting dump to your station. Depending on your PHP
3325 configuration, you will see options to compress the dump. See also the
3326 <a href="#cfg_ExecTimeLimit" class="configrule">$cfg['ExecTimeLimit']</a>
3327 configuration variable.<br /><br />
3329 For additional help on this subject, look for the word &quot;dump&quot; in
3330 this document.</p>
3332 <h4 id="faq6_5">
3333 <a href="#faq6_5">6.5 How can I restore (upload) my database or table using a dump?
3334 How can I run a &quot;.sql&quot; file?
3335 </a></h4>
3337 <p> Click on a database name in the left frame, the properties will be
3338 displayed. Select &quot;Import&quot; from the list
3339 of tabs in the right&#8211;hand frame (or &quot;<abbr title="structured query language">SQL</abbr>&quot; if your phpMyAdmin
3340 version is older than 2.7.0). In the &quot;Location of the text file&quot; section, type in
3341 the path to your dump filename, or use the Browse button. Then click Go.
3342 <br /><br />
3343 With version 2.7.0, the import engine has been re&#8211;written, if possible it is suggested
3344 that you upgrade to take advantage of the new features.
3345 <br /><br />
3346 For additional help on this subject, look for the word &quot;upload&quot;
3347 in this document.
3348 </p>
3350 <h4 id="faq6_6">
3351 <a href="#faq6_6">6.6 How can I use the relation table in Query-by-example?</a></h4>
3353 <p> Here is an example with the tables persons, towns and countries, all
3354 located in the database mydb. If you don't have a <tt>pma_relation</tt>
3355 table, create it as explained in the configuration section. Then create the
3356 example tables:</p>
3358 <pre>
3359 CREATE TABLE REL_countries (
3360 country_code char(1) NOT NULL default '',
3361 description varchar(10) NOT NULL default '',
3362 PRIMARY KEY (country_code)
3363 ) TYPE=MyISAM;
3365 INSERT INTO REL_countries VALUES ('C', 'Canada');
3367 CREATE TABLE REL_persons (
3368 id tinyint(4) NOT NULL auto_increment,
3369 person_name varchar(32) NOT NULL default '',
3370 town_code varchar(5) default '0',
3371 country_code char(1) NOT NULL default '',
3372 PRIMARY KEY (id)
3373 ) TYPE=MyISAM;
3375 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3376 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3378 CREATE TABLE REL_towns (
3379 town_code varchar(5) NOT NULL default '0',
3380 description varchar(30) NOT NULL default '',
3381 PRIMARY KEY (town_code)
3382 ) TYPE=MyISAM;
3384 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3385 INSERT INTO REL_towns VALUES ('M', 'Montr&eacute;al');
3386 </pre>
3388 <p> To setup appropriate links and display information:</p>
3390 <ul><li>on table &quot;REL_persons&quot; click Structure, then Relation view</li>
3391 <li>in Links, for &quot;town_code&quot; choose &quot;REL_towns-&gt;code&quot;</li>
3392 <li>in Links, for &quot;country_code&quot; choose &quot;REL_countries-&gt;country_code&quot;</li>
3393 <li>on table &quot;REL_towns&quot; click Structure, then Relation view</li>
3394 <li>in &quot;Choose field to display&quot;, choose &quot;description&quot;</li>
3395 <li>repeat the two previous steps for table &quot;REL_countries&quot;</li>
3396 </ul>
3398 <p> Then test like this:</p>
3400 <ul><li>Click on your db name in the left frame</li>
3401 <li>Choose &quot;Query&quot;</li>
3402 <li>Use tables: persons, towns, countries</li>
3403 <li>Click &quot;Update query&quot;</li>
3404 <li>In the fields row, choose persons.person_name and click the
3405 &quot;Show&quot; tickbox </li>
3406 <li>Do the same for towns.description and countries.descriptions in the
3407 other 2 columns</li>
3408 <li>Click &quot;Update query&quot; and you will see in the query box that
3409 the correct joins have been generated</li>
3410 <li>Click &quot;Submit query&quot;</li>
3411 </ul>
3413 <h4 id="faqdisplay">
3414 <a href="#faqdisplay">6.7 How can I use the &quot;display field&quot; feature?</a></h4>
3416 Starting from the previous example, create the pma_table_info as explained
3417 in the configuration section, then browse your persons table,
3418 and move the mouse over a town code or country code.
3419 <br /><br />
3420 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that &quot;display field&quot;
3421 enables: drop-down list of possible values.
3422 </p>
3424 <h4 id="faqpdf">
3425 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3427 First the configuration variables &quot;relation&quot;,
3428 &quot;table_coords&quot; and &quot;pdf_pages&quot; have to be filled in.
3429 <br /><br />
3430 Then you need to think about your schema layout. Which tables will go on
3431 which pages?
3432 </p>
3433 <ul>
3434 <li>Select your database in the left frame.</li>
3435 <li>Choose &quot;Operations&quot; in the navigation bar at the top.</li>
3436 <li>Choose &quot;Edit <abbr title="Portable Document Format">PDF</abbr>
3437 Pages&quot; near the bottom of the page.</li>
3438 <li>Enter a name for the first <abbr title="Portable Document Format">PDF</abbr>
3439 page and click Go. If you like, you
3440 can use the &quot;automatic layout,&quot; which will put all your
3441 linked tables onto the new page.</li>
3442 <li>Select the name of the new page (making sure the Edit radio button
3443 is selected) and click Go.</li>
3444 <li>Select a table from the list, enter its coordinates and click Save.<br />
3445 Coordinates are relative; your diagram will
3446 be automatically scaled to fit the page. When initially placing tables
3447 on the page, just pick any coordinates -- say, 50x50. After clicking
3448 Save, you can then use the <a href="#wysiwyg">graphical editor</a> to
3449 position the element correctly.</li>
3450 <li>When you'd like to look at your <abbr title="Portable Document Format">PDF</abbr>,
3451 first be sure to click the Save
3452 button beneath the list of tables and coordinates, to save any changes
3453 you made there. Then scroll all the way down, select the
3454 <abbr title="Portable Document Format">PDF</abbr> options
3455 you want, and click Go.</li>
3456 <li>Internet Explorer for Windows may suggest an incorrect filename when
3457 you try to save a generated <abbr title="Portable Document Format">PDF</abbr>.
3458 When saving a generated <abbr title="Portable Document Format">PDF</abbr>, be
3459 sure that the filename ends in &quot;.pdf&quot;, for example
3460 &quot;schema.pdf&quot;. Browsers on other operating systems, and other
3461 browsers on Windows, do not have this problem.</li>
3462 </ul>
3464 <h4 id="faq6_9">
3465 <a href="#faq6_9">6.9 phpMyAdmin is changing the type of one of my
3466 columns!</a></h4>
3468 <p> No, it's MySQL that is doing
3469 <a href="http://www.mysql.com/doc/S/i/Silent_column_changes.html">silent
3470 column type changing</a>.</p>
3472 <h4 id="underscore">
3473 <a href="#underscore">6.10 When creating a privilege, what happens with
3474 underscores in the database name?</a></h4>
3476 <p> If you do not put a backslash before the underscore, this is a wildcard
3477 grant, and the underscore means &quot;any character&quot;. So, if the
3478 database name is &quot;john_db&quot;, the user would get rights to john1db,
3479 john2db ...<br /><br />
3481 If you put a backslash before the underscore, it means that the database
3482 name will have a real underscore.</p>
3484 <h4 id="faq6_11">
3485 <a href="#faq6_11">6.11 What is the curious symbol &oslash; in the
3486 statistics pages?</a></h4>
3488 <p> It means &quot;average&quot;.</p>
3490 <h4 id="faqexport">
3491 <a href="#faqexport">6.12 I want to understand some Export options.</a></h4>
3493 <p><b>Structure:</b></p>
3495 <ul><li>&quot;Add DROP TABLE&quot; will add a line telling MySQL to
3496 <a href="http://dev.mysql.com/doc/mysql/en/drop-table.html">drop the table</a>,
3497 if it already exists during the import. It does NOT drop the table after
3498 your export, it only affects the import file.</li>
3499 <li>&quot;If Not Exists&quot; will only create the table if it doesn't exist.
3500 Otherwise, you may get an error if the table name exists but has a
3501 different structure.</li>
3502 <li>&quot;Add AUTO_INCREMENT value&quot; ensures that AUTO_INCREMENT value
3503 (if any) will be included in backup.</li>
3504 <li>&quot;Enclose table and field names with backquotes&quot; ensures that
3505 field and table names formed with special characters are protected.</li>
3506 <li>&quot;Add into comments&quot; includes column comments, relations, and MIME
3507 types set in the pmadb in the dump as
3508 <abbr title="structured query language">SQL</abbr> comments (<i>/* xxx */</i>).
3509 </li>
3510 </ul>
3512 <p><b>Data:</b></p>
3514 <ul><li>&quot;Complete inserts&quot; adds the column names on every INSERT
3515 command, for better documentation (but resulting file is bigger).</li>
3516 <li>&quot;Extended inserts&quot; provides a shorter dump file by using only
3517 once the INSERT verb and the table name.</li>
3518 <li>&quot;Delayed inserts&quot; are best explained in the
3519 <a href="http://dev.mysql.com/doc/mysql/en/insert-delayed.html">MySQL manual</a>.
3520 </li>
3521 <li>&quot;Ignore inserts&quot; treats errors as a warning instead. Again,
3522 more info is provided in the
3523 <a href="http://dev.mysql.com/doc/mysql/en/insert.html">MySQL manual</a>,
3524 but basically with this selected, invalid values are adjusted and
3525 inserted rather than causing the entire statement to fail.</li>
3526 </ul>
3528 <h4 id="faq6_13">
3529 <a href="#faq6_13">6.13 I would like to create a database with a dot
3530 in its name.</a></h4>
3532 <p> This is a bad idea, because in MySQL the syntax &quot;database.table&quot;
3533 is the normal way to reference a database and table name. Worse, MySQL
3534 will usually let you create a database with a dot, but then you cannot
3535 work with it, nor delete it.</p>
3537 <h4 id="faqsqlvalidator">
3538 <a href="#faqsqlvalidator">6.14 How do I set up the
3539 <abbr title="structured query language">SQL</abbr> Validator?</a></h4>
3541 <p> To use it, you need a very recent version of PHP, 4.3.0 recommended, with
3542 <abbr title="Extensible Markup Language">XML</abbr>,
3543 <abbr title="Perl Compatible Regular Expressions">PCRE</abbr> and
3544 <abbr title="PHP Extension and Application Repository">PEAR</abbr> support.
3545 On your system command line, run <tt>"pear install Net_Socket Net_URL
3546 HTTP_Request Mail_Mime Net_DIME SOAP"</tt> to get the necessary
3547 <abbr title="PHP Extension and Application Repository">PEAR</abbr> modules
3548 for usage.<br />
3549 On a more recent pear version, I had problems with the state of Net_DIME
3550 being beta, so this single command
3551 <tt>"pear -d preferred_state=beta install -a SOAP"</tt> installed all the
3552 needed modules.<br />
3553 If you use the Validator, you should be aware that any
3554 <abbr title="structured query language">SQL</abbr> statement you
3555 submit will be stored anonymously (database/table/column names,
3556 strings, numbers replaced with generic values). The Mimer
3557 <abbr title="structured query language">SQL</abbr>
3558 Validator itself, is &copy; 2001 Upright Database Technology.
3559 We utilize it as free SOAP service.</p>
3561 <h4 id="faq6_15">
3562 <a href="#faq6_15">6.15 I want to add a BLOB field and put an index on
3563 it, but MySQL says &quot;BLOB column '...' used in key specification without
3564 a key length&quot;.</a></h4>
3566 <p> The right way to do this, is to create the field without any indexes,
3567 then display the table structure and use the &quot;Create an index&quot;
3568 dialog. On this page, you will be able to choose your BLOB field, and
3569 set a size to the index, which is the condition to create an index on
3570 a BLOB field.</p>
3572 <h4 id="faq6_16">
3573 <a href="#faq6_16">6.16 How can I simply move in page with plenty
3574 editing fields?</a></h4>
3576 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3577 with many editing fields (table structure changes, row editing, etc.)
3578 (must be enabled in configuration - see.
3579 <a href="#CtrlArrowsMoving" class="configrule">$cfg['CtrlArrowsMoving']</a>).
3580 You can also have a look at the directive
3581 <a href="#DefaultPropDisplay" class="configrule">$cfg['DefaultPropDisplay']</a>
3582 ('vertical') and see if this eases up editing for you.</p>
3584 <h4 id="faq6_17">
3585 <a href="#faq6_17">6.17 Transformations: I can't enter my own mimetype!
3586 WTF is this feature then useful for?</a></h4>
3588 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3589 on them. Otherwise you could just put a comment on the field. Because entering
3590 your own mimetype will cause serious syntax checking issues and validation,
3591 this introduces a high-risk false-user-input situation. Instead you have to
3592 initialize mimetypes using functions or empty mimetype definitions.<br />
3593 Plus, you have a whole overview of available mimetypes. Who knows all those
3594 mimetypes by heart so he/she can enter it at will?</p>
3596 <h4 id="faqbookmark">
3597 <a href="#faqbookmark">6.18 Bookmarks: Where can I store bookmarks? Why
3598 can't I see any bookmarks below the query box? What is this variable for?
3599 </a></h4>
3601 <p> Any query you have executed can be stored as a bookmark on the page where the
3602 results are displayed. You will find a button labeled 'Bookmark this query'
3603 just at the end of the page.<br />
3604 As soon as you have stored a bookmark, it is related to the database you run
3605 the query on. You can now access a bookmark dropdown on each page, the query
3606 box appears on for that database.<br /><br />
3608 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3609 Just use the string <b>/*[VARIABLE]*/</b> anywhere in your query. Everything
3610 which is put into the <i>value</i> input box on the query box page will
3611 replace the string &quot;/*[VARIABLE]*/&quot; in your stored query. Just be
3612 aware of that you HAVE to create a valid query, otherwise your query won't be
3613 even able to be stored in the database.<br />
3614 Also remember, that everything else inside the <b>/*[VARIABLE]*/</b> string
3615 for your query will remain the way it is, but will be stripped of the /**/
3616 chars. So you can use:<br /><br />
3618 <code>/*, [VARIABLE] AS myname */</code><br /><br />
3620 which will be expanded to<br /><br />
3622 <code>, VARIABLE as myname</code><br /><br />
3624 in your query, where VARIABLE is the string you entered in the input box. If
3625 an empty string is provided, no replacements are made.<br /><br />
3627 A more complex example. Say you have stored this query:<br /><br />
3628 <code>SELECT Name, Address FROM addresses WHERE 1 /* AND Name LIKE '%[VARIABLE]%' */</code>
3629 <br /><br />
3631 Say, you now enter &quot;phpMyAdmin&quot; as the variable for the stored query,
3632 the full query will be:<br /><br />
3634 <code>SELECT Name, Address FROM addresses WHERE 1 AND Name LIKE '%phpMyAdmin%'</code>
3635 <br /><br />
3637 You can use multiple occurrences of <b>/*[VARIABLE]*/</b> in a single query.<br />
3638 <b>NOTE THE ABSENCE OF SPACES</b> inside the &quot;/**/&quot; construct. Any
3639 spaces inserted there
3640 will be later also inserted as spaces in your query and may lead to unexpected
3641 results especially when
3642 using the variable expansion inside of a &quot;LIKE ''&quot; expression.<br />
3643 Your initial query which is going to be stored as a bookmark has to yield at
3644 least one result row so
3645 you can store the bookmark. You may have that to work around using well
3646 positioned &quot;/**/&quot; comments.</p>
3648 <h4 id="faq6_19">
3649 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
3650 include exported table?</a></h4>
3652 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
3653 document should look like following one (assuming you have table
3654 exported in file <code>table.tex</code>):</p>
3656 <pre>
3657 \documentclass{article} % or any class you want
3658 \usepackage{longtable} % for displaying table
3659 \begin{document} % start of document
3660 \include{table} % including exported table
3661 \end{document} % end of document
3662 </pre>
3664 <h4 id="faq6_20">
3665 <a href="#faq6_20">6.20 In MySQL 4, I see a lot of databases which are not mine, and cannot
3666 access them.
3667 </a></h4>
3669 <p> Upgrading to MySQL 4 usually gives users those global privileges: CREATE
3670 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
3671 enable users to see all the database names.
3672 See this <a href="http://bugs.mysql.com/179">bug report</a>.<br /><br />
3674 So if your users do not need those privileges, you can remove them and their
3675 databases list will shorten.</p>
3677 <h4 id="faq6_21">
3678 <a href="#faq6_21">6.21 In edit/insert mode, how can I see a list of
3679 possible values for a field, based on some foreign table?</a></h4>
3681 <p> You have to setup appropriate links between the tables, and also
3682 setup the &quot;display field&quot; in the foreign table. See
3683 <a href="#faq6_6"><abbr title="Frequently Asked Questions">FAQ</abbr>
3684 6.6</a> for an example. Then, if there are 200 values or less in the
3685 foreign table, a drop-down list of values will be available.
3686 You will see two lists of values, the first list containing the key
3687 and the display field, the second list containing the display field
3688 and the key. The reason for this is to be able to type the first
3689 letter of either the key or the display field.<br /><br />
3691 For 200 values or more, a distinct window will appear, to browse foreign
3692 key values and choose one.</p>
3694 <h4 id="faq6_22">
3695 <a href="#faq6_22">6.22 Bookmarks: Can I execute a default bookmark
3696 automatically when entering Browse mode for a table?</a></h4>
3698 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
3699 </p>
3701 <h4 id="faq6_23">
3702 <a href="#faq6_23">6.23 Export: I heard phpMyAdmin can export Microsoft
3703 Excel files, how can I enable that?</a></h4>
3705 <p> Current version does support direct export to Microsoft Excel and Word
3706 versions 2000 and newer. If you need export older versions, you can use
3707 <abbr title="comma seperated values">CSV</abbr> suitable for Microsoft Excel,
3708 which works out of the box or you can
3709 try native <b>experimental</b> MS Excel exporter. <b>This export has
3710 several problems, most important are limitation of cell content to 255
3711 chars and no support for charsets, so think carefully whether you want to
3712 enable this.</b>. For enabling this you need to set
3713 <a href="#cfg_TempDir" class="configrule">$cfg['TempDir']</a> to
3714 place where web server user can write (for example <tt>'./tmp'</tt>) and
3715 install <abbr title="PHP Extension and Application Repository">PEAR</abbr>
3716 module Spreadsheet_Excel_Writer into php include path. The
3717 installation can be done by following command:</p>
3719 <pre>
3720 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
3721 </pre>
3723 <p> First part of switches set we want to install beta version of that module
3724 (no stable version available yet) and then we tell pear we want to satisfy
3725 dependencies.</p>
3727 <p> If you are running in PHP safe mode, you will have to set
3728 in <tt>php.ini</tt> the <tt>safe_mode_include_dir</tt> to the directory
3729 where your <abbr title="PHP Extension and Application Repository">PEAR</abbr>
3730 modules are located, for example:</p>
3732 <pre>
3733 safe_mode_include_dir = /usr/local/lib/php
3734 </pre>
3736 <p> To create the temporary directory on a UNIX-based system, you can do:</p>
3738 <pre>
3739 cd phpMyAdmin
3740 mkdir tmp
3741 chmod o+rwx tmp
3742 </pre>
3744 <h4 id="faq6_24">
3745 <a href="#faq6_24">6.24 Now that phpMyAdmin supports native MySQL 4.1.x column comments,
3746 what happens to my column comments stored in pmadb?</a></h4>
3748 <p> Automatic migration of a table's pmadb-style column comments to the native
3749 ones is done whenever you enter Structure page for this table.</p>
3751 <h3 id="faqproject">phpMyAdmin project</h3>
3753 <h4 id="faq7_1">
3754 <a href="#faq7_1">7.1 I have found a bug. How do I inform developers?</a></h4>
3756 <p> Our Bug Tracker is located at
3757 <a href="http://sf.net/projects/phpmyadmin/">http://sf.net/projects/phpmyadmin/</a>
3758 under the Bugs section.<br /><br />
3760 But please first discuss your bug with other users:<br />
3761 <a href="http://sf.net/projects/phpmyadmin/">
3762 http://sf.net/projects/phpmyadmin/</a> (and choose Forums)</p>
3764 <h4 id="faq7_2">
3765 <a href="#faq7_2">7.2 I want to translate the messages to a new language or upgrade an
3766 existing language, where do I start?</a></h4>
3768 <p> Always use the current CVS version of your language file.
3769 For a new language, start from <i>english-iso-8859-1.inc.php</i>. If you
3770 don't know how to get the CVS version, please ask one of the developers.
3771 <br />
3772 Please note that we try not to use HTML entities like &amp;eacute; in
3773 the translations, since we define the right character set in the file.
3774 With HTML entities, the text on JavaScript messages would not
3775 display correctly.
3776 However there are some entities that need to be there, for quotes
3777 ,non-breakable spaces, ampersands, less than, greater than.<br />
3778 You can then put your translations, as a zip file to avoid losing special
3779 characters, on the sourceforge.net translation tracker.<br />
3780 It would be a good idea to subscribe to the phpmyadmin-translators mailing
3781 list, because this is where we ask for translations of new messages.</p>
3783 <h4 id="faq7_3">
3784 <a href="#faq7_3">7.3 I would like to help out with the development of
3785 phpMyAdmin. How should I proceed?</a></h4>
3787 <p> The following method is preferred for new developers:</p>
3789 <ol><li>fetch the current CVS tree over anonymous CVS:<br />
3790 <tt>cvs -d:pserver:anonymous@phpmyadmin.cvs.sourceforge.net:/cvsroot/phpmyadmin login</tt><br />
3791 [Password: simply press the Enter key]<br />
3792 <tt>cvs -z3 -d:pserver:anonymous@phpmyadmin.cvs.sourceforge.net:/cvsroot/phpmyadmin checkout phpMyAdmin</tt><br />
3793 [This will create a new sub-directory named phpMyAdmin]</li>
3794 <li>add your stuff</li>
3795 <li>put the modified files (tar'ed and gzip'ed) inside the patch tracker of
3797 <a href="http://sf.net/projects/phpmyadmin/">phpMyAdmin SourceForge account</a>.
3798 </li>
3799 </ol>
3801 <p> Write access to the CVS tree is granted only to experienced developers who
3802 have already contributed something useful to phpMyAdmin.<br />
3803 Also, have a look at the <a href="#developers">Developers section</a>.</p>
3805 <h3 id="faqsecurity">Security</h3>
3807 <h4 id="faq8_1">
3808 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
3810 <p> Please refer to
3811 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
3812 </p>
3814 <!-- DEVELOPERS -->
3815 <h2 id="developers">Developers Information</h2>
3817 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
3818 great features have been written by other people and you too can help to
3819 make phpMyAdmin a useful tool.</p>
3821 <p> If you're planning to contribute source, please read the following
3822 information:</p>
3824 <ul><li>All files include <i>libraries/header.inc.php</i> (layout),.
3825 <i>libraries/common.lib.php</i> (common functions) and
3826 <i>config.inc.php</i>.<br />
3827 Only configuration data should go in <i>config.inc.php</i>. Please keep
3828 it free from other code.<br />
3829 Commonly used functions should be added to
3830 <i>libraries/common.lib.php</i> and more specific ones may be added
3831 within a library stored into the <i>libraries</i> sub-directory.</li>
3832 <li>Obviously, you're free to use whatever coding style you want. But
3833 please try to keep your code as simple as possible: beginners are
3834 using phpMyAdmin as an example application.<br />
3835 As far as possible, we want the scripts to be XHTML1.0 and CSS2
3836 compliant on one hand, they fit the
3837 <a href="http://pear.php.net/">
3838 <abbr title="PHP Extension and Application Repository">PEAR</abbr>
3839 coding standards</a>
3840 on the other hand. Please pay attention to this.</li>
3841 <li>Please try to keep up the file-naming conventions. Table-related stuff
3842 goes to <i>tbl_*.php</i>, db-related code to <i>db_*.php</i>,
3843 server-related tools to <i>server_*.php</i> and so on.</li>
3844 <li>Please don't use verbose strings in your code, instead add the string
3845 (at least) to <i>english-iso-8859-1.inc.php</i> and print() it out.</li>
3846 <li>If you want to be really helpful, write an entry for the ChangeLog.</li>
3847 <li id="developersdbg">
3848 The DBG extension (<a href="http://dd.cron.ru/dbg/">PHP
3849 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
3850 better debug and profile their code.<br />
3851 Please see the
3852 <a href="#cfg_DBG" class="configrule">$cfg['DBG']*</a> configuration
3853 options for more information.<br />
3854 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
3855 lost during its re-entry into Earth's atmosphere and in memory of the
3856 brave men and women who gave their lives for the people of Earth.</li>
3857 </ul>
3859 <!-- CREDITS -->
3860 <h2 id="credits">Credits</h2>
3862 <pre>
3863 phpMyAdmin - Credits
3864 ====================
3866 CREDITS, in chronological order
3867 -------------------------------
3869 - Tobias Ratschiller &lt;tobias_at_ratschiller.com&gt;
3870 * creator of the phpmyadmin project
3871 * maintainer from 1998 to summer 2000
3873 - Marc Delisle &lt;Marc.Delisle_at_cegepsherbrooke.qc.ca&gt;
3874 * multi-language version
3875 * various fixes and improvements
3876 * <abbr title="structured query language">SQL</abbr> analyser (most of it)
3877 * current project maintainer
3879 - Olivier M&uuml;ller &lt;om_at_omnis.ch&gt;
3880 * started SourceForge phpMyAdmin project in March 2001
3881 * sync'ed different existing CVS trees with new features and bugfixes
3882 * multi-language improvements, dynamic language selection
3883 * current project maintainer
3884 * many bugfixes and improvements
3886 - Lo&iuml;c Chapeaux &lt;lolo_at_phpheaven.net&gt;
3887 * rewrote and optimized javascript, DHTML and DOM stuff
3888 * rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
3889 generate XHTML1.0 and CSS2 compliant codes
3890 * improved the language detection system
3891 * many bugfixes and improvements
3893 - Robin Johnson &lt;robbat2_at_users.sourceforge.net&gt;
3894 * database maintenance controls
3895 * table type code
3896 * Host authentication <abbr title="Internet Protocol">IP</abbr> Allow/Deny
3897 * DB-based configuration (Not completed)
3898 * <abbr title="structured query language">SQL</abbr> parser and pretty-printer
3899 * <abbr title="structured query language">SQL</abbr> validator
3900 * many bugfixes and improvements
3902 - Armel Fauveau &lt;armel.fauveau_at_globalis-ms.com&gt;
3903 * bookmarks feature
3904 * multiple dump feature
3905 * gzip dump feature
3906 * zip dump feature
3908 - Geert Lund &lt;glund_at_silversoft.dk&gt;
3909 * various fixes
3910 * moderator of the phpMyAdmin former users forum at phpwizard.net
3912 - Korakot Chaovavanich &lt;korakot_at_iname.com&gt;
3913 * &quot;insert as new row&quot; feature
3915 - Pete Kelly &lt;webmaster_at_trafficg.com&gt;
3916 * rewrote and fix dump code
3917 * bugfixes
3919 - Steve Alberty &lt;alberty_at_neptunlabs.de&gt;
3920 * rewrote dump code for PHP4
3921 * mySQL table statistics
3922 * bugfixes
3924 - Benjamin Gandon &lt;gandon_at_isia.cma.fr&gt;
3925 * main author of the version 2.1.0.1
3926 * bugfixes
3928 - Alexander M. Turek &lt;me_at_derrabus.de&gt;
3929 * MySQL 4.0 / 4.1 / 5.0 compatibility
3930 * abstract database interface (PMA_DBI) with MySQLi support
3931 * privileges administration
3932 * <abbr title="Extensible Markup Language">XML</abbr> exports
3933 * various features and fixes
3934 * German language file updates
3936 - Mike Beck &lt;mike.beck_at_web.de&gt;
3937 * automatic joins in QBE
3938 * links column in printview
3939 * Relation view
3941 - Michal &#268;iha&#345; &lt;michal_at_cihar.com&gt;
3942 * enhanced index creation/display feature
3943 * feature to use a different charset for HTML than for MySQL
3944 * improvements of export feature
3945 * various features and fixes
3946 * Czech language file updates
3948 - Christophe Gesch&eacute; from the &quot;MySQL Form Generator for PHPMyAdmin&quot;
3949 (http://sf.net/projects/phpmysqlformgen/)
3950 * suggested the patch for multiple table printviews
3952 - Garvin Hicking &lt;me_at_supergarv.de&gt;
3953 * built the patch for vertical display of table rows
3954 * built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history
3955 * Improvement of column/db comments
3956 * (MIME)-Transformations for columns
3957 * Use custom alias names for Databases in left frame
3958 * hierarchical/nested table display
3959 * <abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations
3960 * new icon sets
3961 * vertical display of column properties page
3962 * some bugfixes, features, support, German language additions
3964 - Yukihiro Kawada &lt;kawada_at_den.fujifilm.co.jp&gt;
3965 * japanese kanji encoding conversion feature
3967 - Piotr Roszatycki &lt;d3xter_at_users.sourceforge.net&gt; and Dan Wilson
3968 * the Cookie authentication mode
3970 - Axel Sander &lt;n8falke_at_users.sourceforge.net&gt;
3971 * table relation-links feature
3973 - Maxime Delorme &lt;delorme.maxime_at_free.fr&gt;
3974 * <abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
3975 &quot;FPDF&quot; library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
3976 for the &quot;UFPDF&quot; library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).
3978 - Olof Edlund &lt;olof.edlund_at_upright.se&gt;
3979 * <abbr title="structured query language">SQL</abbr> validator server
3981 - Ivan R. Lanin &lt;ivanlanin_at_users.sourceforge.net&gt;
3982 * phpMyAdmin logo (until June 2004)
3984 - Mike Cochrane &lt;mike_at_graftonhall.co.nz&gt;
3985 * blowfish library from the Horde project
3987 - Marcel Tschopp &lt;ne0x_at_users.sourceforge.net&gt;
3988 * mysqli support
3989 * many bugfixes and improvements
3991 - Michael Keck &lt;mkkeck_at_users.sourceforge.net&gt;
3992 * redesign for 2.6.0
3993 * phpMyAdmin sailboat logo (June 2004)
3995 - Mathias Landh&auml;u&szlig;er
3996 * Representation at conferences
3998 - Sebastian Mendel &lt;cybot_tm_at_users.sourceforge.net&gt;
3999 * interface improvements
4000 * various bugfixes
4002 And also to the following people who have contributed minor changes,
4003 enhancements, bugfixes or support for a new language since version 2.1.0:
4005 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4006 P&eacute;ter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4007 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kl&auml;ger,
4008 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4009 Bernard M. Piller, Laurent Haas, &quot;Sakamoto&quot;, Yuval Sarna,
4010 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4011 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4012 Lu&iacute;s V., Martijn W. van der Lee,
4013 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4014 Jakub Wilk, Thomas Michael Winningham, Vilius Zigmantas, &quot;Manuzhai&quot;.
4017 Original Credits of Version 2.1.0
4018 ---------------------------------
4020 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4021 to create a web-based interface to MySQL using PHP3. Although I have not
4022 used any of his source-code, there are some concepts I've borrowed from
4023 him. phpMyAdmin was created because Peter told me he wasn't going to
4024 further develop his (great) tool.
4025 Thanks go to
4026 - Amalesh Kempf &lt;ak-lsml_at_living-source.com&gt; who contributed the
4027 code for the check when dropping a table or database. He also suggested
4028 that you should be able to specify the primary key on tbl_create.php3. To
4029 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4030 well as a bug-report. Plus many smaller improvements.
4031 - Jan Legenhausen &lt;jan_at_nrw.net&gt;: He made many of the changes that
4032 were introduced in 1.3.0 (including quite significant ones like the
4033 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4034 bug-fixes and help.
4035 - Marc Delisle &lt;DelislMa_at_CollegeSherbrooke.qc.ca&gt; made phpMyAdmin
4036 language-independent by outsourcing the strings to a separate file. He
4037 also contributed the French translation.
4038 - Alexandr Bravo &lt;abravo_at_hq.admiral.ru&gt; who contributed
4039 tbl_select.php3, a feature to display only some fields from a table.
4040 - Chris Jackson &lt;chrisj_at_ctel.net&gt; added support for MySQL
4041 functions in tbl_change.php3. He also added the
4042 &quot;Query by Example&quot; feature in 2.0.
4043 - Dave Walton &lt;walton_at_nordicdms.com&gt; added support for multiple
4044 servers and is a regular contributor for bug-fixes.
4045 - Gabriel Ash &lt;ga244_at_is8.nyu.edu&gt; contributed the random access
4046 features for 2.0.6.
4047 The following people have contributed minor changes, enhancements, bugfixes
4048 or support for a new language:
4049 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4050 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4051 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4052 G. Wieggers.
4054 And thanks to everyone else who sent me email with suggestions, bug-reports
4055 and or just some feedback.
4056 </pre>
4058 <h2 id="glossary">Glossary</h2>
4060 <p> From Wikipedia, the free encyclopedia</p>
4062 <ul>
4063 <li><a href="http://www.wikipedia.org/wiki/.htaccess">.htaccess</a>
4064 - the default name of Apache's directory-level configuration file.</li>
4065 <li><a href="http://www.wikipedia.org/wiki/Blowfish_%28cipher%29">Blowfish</a>
4066 - a keyed, symmetric block cipher, designed in 1993 by Bruce Schneier.</li>
4067 <li><a href="http://www.wikipedia.org/wiki/Browser">Browser (Web Browser)</a>
4068 - a software application that enables a user to display and interact with
4069 text, images, and other information typically located on a web page at a
4070 website on the World Wide Web.</li>
4071 <li><a href="http://www.wikipedia.org/wiki/Bzip2">bzip2</a>
4072 - a free software/open source data compression algorithm and program
4073 developed by Julian Seward.</li>
4074 <li><a href="http://www.wikipedia.org/wiki/CGI">CGI (Common Gateway Interface)</a>
4075 - an important World Wide Web technology that enables a client web browser
4076 to request data from a program executed on the Web server.</li>
4077 <li><a href="http://www.wikipedia.org/wiki/Changelog">Changelog</a>
4078 - a log or record of changes made to a project.</li>
4079 <li><a href="http://www.wikipedia.org/wiki/Client_%28computing%29">Client</a>
4080 - a computer system that accesses a (remote) service on another computer
4081 by some kind of network.</li>
4082 <li><a href="http://www.wikipedia.org/wiki/Column (database)">column</a>
4083 - a set of data values of a particular simple type, one for each row of
4084 the table.</li>
4085 <li><a href="http://www.wikipedia.org/wiki/HTTP cookie">Cookie</a>
4086 - a packet of information sent by a server to a World Wide Web browser
4087 and then sent back by the browser each time it accesses that server.</li>
4088 <li><a href="http://www.wikipedia.org/wiki/Comma-separated_values">CSV</a>
4089 - Comma-seperated values</li>
4090 <li>DB - look at <a href="#database">Database</a>.</li>
4091 <li><a id="database" href="http://www.wikipedia.org/wiki/Database">database</a>
4092 - an organized collection of data.</li>
4093 <li>Engine - look at <a href="#glossar_storage_engine">Storage Engines</a>.</li>
4094 <li><a href="http://www.wikipedia.org/wiki/extension">extension</a>
4095 - a PHP module that extends PHP with additional functionality.</li>
4096 <li><a href="http://www.wikipedia.org/wiki/FAQ">FAQ (Frequently Asked Questions)</a>
4097 - a list of commonly asked question and there answers.</li>
4098 <li><a href="http://www.wikipedia.org/wiki/Field (computer science)">Field</a>
4099 - one part of divided data/columns.</li>
4100 <li><a href="http://www.wikipedia.org/wiki/Foreign key">foreign key</a>
4101 - a field or group of fields in a database record that point to a key
4102 field or group of fields forming a key of another database record in some
4103 (usually different) table.</li>
4104 <li><a href="http://www.fpdf.org/">FPDF (FreePDF)</a>
4105 - the free PDF library</li>
4106 <li><a id="gd" href="http://www.wikipedia.org/wiki/GD_Graphics_Library">
4107 GD Graphics Library</a> - a library by Thomas Boutell and others for
4108 dynamically manipulating images.</li>
4109 <li>GD2 - look at <a href="#gd">GD Graphics Library</a>.</li>
4110 <li><a href="http://www.wikipedia.org/wiki/Gzip">gzip</a>
4111 - gzip is short for GNU zip, a GNU free software file compression
4112 program.</li>
4113 <li><a href="http://www.wikipedia.org/wiki/Host">host</a>
4114 - any machine connected to a computer network, a node that has a hostname.</li>
4115 <li><a href="http://www.wikipedia.org/wiki/Hostname">hostname</a>
4116 - the unique name by which a network attached device is known on a network.</li>
4117 <li><a href="http://www.wikipedia.org/wiki/HyperText Transfer Protocol">HTTP
4118 (HyperText Transfer Protocol)</a>
4119 - the primary method used to transfer or convey information on the World
4120 Wide Web.</li>
4121 <li><a href="http://www.wikipedia.org/wiki/Https: URI scheme">https</a>
4122 - a <abbr title="HyperText Transfer Protocol">HTTP</abbr>-connection with
4123 additional security measures.</li>
4124 <li><a href="http://www.wikipedia.org/wiki/Internet Information Services">IIS (Internet Information Services)</a>
4125 - a set of Internet-based services for servers using Microsoft Windows.</li>
4126 <li><a id="glossar_index" href="http://www.wikipedia.org/wiki/Index (database)">Index</a>
4127 - a feature that allows quick access to the rows in a table.</li>
4128 <li><a href="http://www.wikipedia.org/wiki/Internet Protocol">IP (Internet Protocol)</a>
4129 - a data-oriented protocol used by source and destination hosts for
4130 communicating data across a packet-switched internetwork.</li>
4131 <li><a href="http://www.wikipedia.org/wiki/IP Address">IP Address</a>
4132 - a unique number that devices use in order to identify and communicate
4133 with each other on a network utilizing the Internet Protocol standard.</li>
4134 <li><a href="http://www.wikipedia.org/wiki/ISAPI">ISAPI
4135 (Internet Server Application Programming Interface)</a>
4136 - the API of Internet Information Services (IIS).</li>
4137 <li><a href="http://www.wikipedia.org/wiki/ISP">ISP (Internet service provider)</a>
4138 - a business or organization that offers users access to the Internet and related services.</li>
4139 <li><a id="jpeg" href="http://www.wikipedia.org/wiki/JPEG">JPEG</a>
4140 - a most commonly used standard method of lossy compression for
4141 photographic images.</li>
4142 <li>JPG - look at <a href="#jpeg">JPEG</a>.</li>
4143 <li>Key - look at <a href="#glossar_index">index</a>.</li>
4144 <li><a href="http://www.wikipedia.org/wiki/LaTeX">L<sup>A</sup>T<sub><big>E</big></sub>X</a>
4145 - a document preparation system for the T<sub>E</sub>X typesetting program.</li>
4146 <li><a href="http://www.wikipedia.org/wiki/Mac">Mac (Apple Macintosh)</a>
4147 - line of personal computers is designed, developed, manufactured, and
4148 marketed by Apple Computer.</li>
4149 <li><a id="glossar_mac_os_x" href="http://www.wikipedia.org/wiki/Mac OS X"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>
4150 - the operating system which is included with all currently shipping Apple
4151 Macintosh computers in the consumer and professional markets.</li>
4152 <li><a href="http://www.wikipedia.org/wiki/MCrypt">MCrypt</a>
4153 - a cryptographic library.</li>
4154 <li><a href="http://php.net/mcrypt">mcrypt</a>
4155 - the MCrypt PHP extension.</li>
4156 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4157 - an Internet Standard for the format of e-mail.</li>
4158 <li><a href="http://www.wikipedia.org/wiki/module">module</a>
4159 - some sort of extension for the Apache Webserver.</li>
4160 <li><a href="http://www.wikipedia.org/wiki/MySQL">MySQL</a>
4161 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4162 Management System (DBMS).</li>
4163 <li><a href="http://php.net/mysqli">mysqli</a>
4164 - the improved MySQL client PHP extension.</li>
4165 <li><a href="http://php.net/mysql">mysql</a>
4166 - the MySQL client PHP extension.</li>
4167 <li><a href="http://en.wikipedia.org/wiki/OpenDocument">OpenDocument</a>
4168 - open standard for office documents.</li>
4169 <li><a href="http://www.wikipedia.org/wiki/OS X"><abbr title="operating system">OS</abbr> X</a>
4170 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4171 <li><a href="http://www.wikipedia.org/wiki/Portable Document Format">PDF
4172 (Portable Document Format)</a>
4173 - a file format developed by Adobe Systems for representing two
4174 dimensional documents in a device independent and resolution independent
4175 format.</li>
4176 <li><a href="http://pear.php.net/">PEAR</a>
4177 - the PHP Extension and Application Repository.</li>
4178 <li><a href="http://php.net/pcre">PCRE (Perl Compatible Regular Expressions)</a>
4179 - the perl-compatible regular expression functions for PHP</li>
4180 <li><a href="http://www.wikipedia.org/wiki/PHP">PHP</a>
4181 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4182 programming language used mainly for developing server-side applications
4183 and dynamic web content, and more recently, a broader range of software
4184 applications.</li>
4185 <li><a href="http://www.wikipedia.org/wiki/Port (computing)">port</a>
4186 - a connection through which data is sent and received.</li>
4187 <li><a href="http://www.wikipedia.org/wiki/Gzip">RFC</a>
4188 - Request for Comments (RFC) documents are a series of memoranda
4189 encompassing new research, innovations, and methodologies applicable to
4190 Internet technologies.</li>
4191 <li><a href="http://www.ietf.org/rfc/rfc1952.txt">RFC 1952</a>
4192 - GZIP file format specification version 4.3</li>
4193 <li><a href="http://www.wikipedia.org/wiki/Row (database)">Row (record, tulpel)</a>
4194 - represents a single, implicitly structured data item in a table.</li>
4195 <li><a href="http://www.wikipedia.org/wiki/Server_%28computing%29">Server</a>
4196 - a computer system that provides services to other computing
4197 systems over a network.</li>
4198 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4199 - handlers for different table types</li>
4200 <li><a href="http://www.wikipedia.org/wiki/Socket#Computer_sockets">socket</a>
4201 - a form of inter-process communication.</li>
4202 <li><a href="http://www.wikipedia.org/wiki/Secure_Sockets_Layer">SSL (Secure
4203 Sockets Layer)</a>
4204 - a cryptographic protocol which provides secure communication on the Internet.</li>
4205 <li><a href="http://www.wikipedia.org/wiki/SQL">SQL</a>
4206 - Structured Query Language</li>
4207 <li><a href="http://www.wikipedia.org/wiki/Table (database)">table</a>
4208 - a set of data elements (cells) that is organized, defined and stored as
4209 horizontal rows and vertical columns where each item can be uniquely
4210 identified by a label or key or by it?s position in relation to other items.</li>
4211 <li>Table type</li>
4212 <li><a href="http://www.wikipedia.org/wiki/Tar_%28file_format%29">tar</a>
4213 - a type of archive file format: the Tape ARchive format.</li>
4214 <li><a href="http://www.wikipedia.org/wiki/TCP">TCP (Transmission Control Protocol)</a>
4215 - one of the core protocols of the Internet protocol suite.</li>
4216 <li><a href="http://www.acko.net/node/56">UFPDF</a>
4217 - Unicode/UTF-8 extension for FPDF</li>
4218 <li><a href="http://www.wikipedia.org/wiki/URL">URL (Uniform Resource Locator)</a>
4219 - a sequence of characters, conforming to a standardized format, that is
4220 used for referring to resources, such as documents and images on the
4221 Internet, by their location.</li>
4222 <li><a href="http://www.wikipedia.org/wiki/Webserver">Webserver</a>
4223 - A computer (program) that is responsible for accepting HTTP requests
4224 from clients and serving them Web pages.</li>
4225 <li><a href="http://www.wikipedia.org/wiki/XML">XML (Extensible Markup Language)</a>
4226 - a W3C-recommended general-purpose markup language for creating
4227 special-purpose markup languages, capable of describing many different
4228 kinds of data.</li>
4229 <li><a href="http://www.wikipedia.org/wiki/ZIP_%28file_format%29">ZIP</a>
4230 - a popular data compression and archival format.</li>
4231 <li><a href="http://www.wikipedia.org/wiki/Zlib">zlib</a>
4232 - an open-source, cross-platform data compression library by Jean-loup
4233 Gailly and Mark Adler.</li>
4234 </ul>
4236 <p id="bottom">
4237 <a href="http://validator.w3.org/check?uri=referer">
4238 <img src="http://www.w3.org/Icons/valid-xhtml11" alt="Valid XHTML 1.1"
4239 height="31" width="88" /></a>
4240 <a href="http://jigsaw.w3.org/css-validator/">
4241 <img src="http://www.w3.org/Icons/valid-css" alt="Valid CSS!" width="88"
4242 height="31" /></a></p>
4244 </body>
4245 </html>