| blob | 12f0fb19604d4110163160eab9af036eca6686e5 |
3 <!--
4 vim: expandtab ts=4 sw=4 sts=4 tw=78
5 -->
8 <!-- $Id$ -->
9 <head>
15 </head>
19 <h1>
21 3.3.0-dev
22 Documentation
23 </h1>
24 </div>
26 <!-- TOP MENU -->
35 <li><a href="Documentation.html#faq"><abbr title="Frequently Asked Questions"> FAQ</abbr></a></li>
41 </ul>
46 phpMyAdmin homepage</a></li>
48 SourceForge phpMyAdmin project page</a></li>
50 Official phpMyAdmin wiki</a></li>
51 <li>Local documents:
54 </ul>
55 </li>
56 <li>Documentation version:
58 </li>
59 </ul>
61 <!-- REQUIREMENTS -->
68 and the Standard PHP Library (SPL) extension.
69 </li>
72 currently default), you should install mbstring and ctype
73 extensions.
74 </li>
75 <li>You need GD2 support in PHP to display inline
77 original aspect ratio</li>
83 load pages significantly slower.
84 </li>
85 </ul>
86 </li>
89 </ul>
91 <!-- INTRODUCTION -->
94 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
95 a single database. To accomplish the latter you'll need a properly set up
96 MySQL user who can read/write only the desired database. It's up to you to
97 look up the appropriate part in the MySQL manual.
98 </p>
103 <li>create, copy, drop, rename and alter databases, tables, fields and
104 indexes</li>
105 <li>maintenance server, databases and tables, with proposals on server
106 configuration</li>
107 <li>execute, edit and bookmark any
109 batch-queries</li>
112 </li>
119 OpenDocument Text and Spreadsheet,
121 <abbr title="Microsoft Excel 2000">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
122 </li>
126 <li>using Query-by-example (QBE), create complex queries automatically
127 connecting required tables</li>
129 your Database layout</li>
131 <li>transform stored data into any format using a set of predefined
132 functions, like displaying BLOB-data as image or download-link
133 </li>
139 </li>
140 </ul>
143 <p> Many people have difficulty
144 understanding the concept of user management with regards to phpMyAdmin. When
145 a user logs in to phpMyAdmin, that username and password are passed directly
146 to MySQL. phpMyAdmin does no account management on its own (other than
147 allowing one to manipulate the MySQL user account information); all users
148 must be valid MySQL users.</p>
157 <!-- INSTALLATION -->
165 </ol>
168 phpMyAdmin does not apply any special security methods to the MySQL database
169 server. It is still the system administrator's job to grant permissions on
171 be used for this.
172 </p>
180 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
181 before uploading them to your server, as PHP seems not to like
186 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
187 Downloads page. Some kits contain only the English messages,
188 others contain all languages in UTF-8 format (this should be fine
189 in most situations), others contain all
190 languages and all character sets. We'll assume you chose a kit whose
192 </li>
193 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
195 document root. If you don't have direct access to your document root,
196 put the files in a directory on your local machine, and, after step 4,
197 transfer the directory on your web server using, for example, ftp.</li>
198 <li>Ensure that all the scripts have the appropriate owner (if PHP is
199 running in safe mode, having some scripts with an owner different
200 from the owner of other scripts will be a
205 <li>Now you must configure your installation. There are two methods that
206 can be used. Traditionally, users have hand-edited a copy of
208 provided for those who prefer a graphical installation. Creating a
209 <tt>config.inc.php</tt> is still a quick way to get started and needed for some advanced features.
210 <ul><li>To manually create the file, simply use your text editor to
213 file) in the main (top-level) phpMyAdmin directory (the one
217 default value is okay for a particular setting, there is no
219 few directives to get going, a simple configuration may look
220 like this:
221 <pre>
222 <?php
223 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
225 $i=0;
226 $i++;
227 $cfg['Servers'][$i]['auth_type'] = 'cookie';
228 ?>
229 </pre>
230 Or, if you prefer to not be prompted every time you log in:
231 <pre>
232 <?php
234 $i=0;
235 $i++;
236 $cfg['Servers'][$i]['user'] = 'root';
237 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
238 ?>
239 </pre>
240 For a full explanation of possible configuration values, see the
246 directory. This is a security measure. On a Linux/Unix system you
247 can use the following commands:
248 <pre>
249 cd phpMyAdmin
250 mkdir config # create directory for saving
251 chmod o+rw config # give it world writable permissions
252 </pre>
253 And to edit an existing configuration, copy it over first:
254 <pre>
255 cp config.inc.php config/ # copy current configuration for editing
256 chmod o+w config/config.inc.php # give it world writable permissions
257 </pre>
258 On other platforms, simply create the folder and ensure that your
267 the webserver does not have the proper permissions you may see the
269 config/</tt> directory exists and has the proper permissions -
271 and upload (via FTP or some similar means) to the proper location.<br /><br />
273 Once the file has been saved, it must be moved out of the <tt>
274 config/</tt> directory and the permissions must be reset, again
275 as a security measure:
276 <pre>
277 mv config/config.inc.php . # move file to current directory
278 chmod o-rw config.inc.php # remove world read and write permissions
279 rm -rf config # remove not needed directory
280 </pre>
281 Now the file is ready to be used. You can choose to review or edit
282 the file with your favorite editor, if you prefer to set some
283 advanced options which the setup script does not provide.</li></ul></li>
284 <li>If you are using the
286 protect the phpMyAdmin installation directory because using
287 config does not require a user to
288 enter a password to access the phpMyAdmin installation. Use of an alternate
289 authentication method is recommended, for example with
297 in your browser. phpMyAdmin should now display a welcome screen
298 and your databases, or a login dialog if using
300 authentication mode.</li>
303 Apache you can use supplied .htaccess file in that folder, for other
304 webservers, you should configure this yourself. Such configuration
305 prevents from possible path exposure and cross side scripting
306 vulnerabilities that might happen to be found in that code.</li>
307 <li>
308 It is generally good idea to protect public phpMyAdmin installation
309 against access by robots as they usually can not do anything good
311 your webserver or limit access by web server configuration. You can
314 </li>
315 </ol>
319 <p> For a whole set of new features (bookmarks, comments,
322 transformation, etc.) you need to create a set of special tables. Those
323 tables can be located in your own database, or in a central database for a
324 multi-user installation (this database would then be accessed by the
325 controluser, so no other user should have rights to it).</p>
335 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
336 that you may need special (administrator) privileges to create the database
337 and tables, and that the script may need some tuning, depending on the
338 database name.</p>
343 section</a>. You will also need to have a controluser with the proper rights
350 unpacked one. Configuration files from old versions may
351 require some tweaking as some options have been changed or removed; in
353 so you better remove it from your file and just use the default one.
355 statement that you might find near the end of your configuration file.</p>
359 is version-specific.</p>
362 version 4.1.2 or newer and if you use the pmadb/linked table infrastructure,
363 you should run the SQL script found in
370 where you want to give users access to their own database and don't want
371 them to play around with others.<br />
372 Nevertheless be aware that MS Internet Explorer seems to be really buggy
374 in this area!<br />
377 that your user/password pair are not in clear in the configuration file.
378 </li>
381 authentication modes are more secure: the MySQL login information does
382 not need to be set in the phpMyAdmin configuration file (except possibly
384 However, keep in mind that the password travels in plain text, unless
385 you are using the HTTPS protocol.<br />
386 In cookie mode, the password is stored, encrypted with the blowfish
387 algorithm, in a temporary cookie.</li>
399 file under the
401 $cfg['Servers'][$i]['controluser']</a></tt> and
406 only an example: use something else in your file!</b> Input these
407 statements from the phpMyAdmin SQL Query window or mysql command–line
408 client.<br />
410 if it's not the same as the MySQL server's one.
412 <pre>
413 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
414 GRANT SELECT (
415 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
416 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
417 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
418 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
419 Execute_priv, Repl_slave_priv, Repl_client_priv
420 ) ON mysql.user TO 'pma'@'localhost';
421 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
422 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
423 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
424 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
426 If you want to use the many new relation and bookmark features:
428 <pre>
430 </pre>
436 on a set of particular databases. Normally you shouldn't give global
437 privileges to an ordinary user, unless you understand the impact of those
438 privileges (for example, you are creating a superuser).<br />
442 <pre>
443 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
444 </pre>
446 What the user may now do is controlled entirely by the MySQL user
447 management system.<br />
449 authentication mode, you don't need to fill the user/password fields
451 array.</li>
452 </ul>
457 method and allows you to log in as any valid MySQL user.</li>
458 <li>Is supported with most PHP configurations. For
471 mode.</li>
472 </ul>
476 <ul><li>You can use this method as a replacement for the
478 (for example, if you're running
480 <li>Obviously, the user must enable cookies in the browser, but this is
481 now a requirement for all authentication modes.</li>
482 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
483 with the same username.</li>
484 <li>If you want to log in to arbitrary server see
489 not required.</li>
490 </ul>
494 <ul><li>This mode is a convenient way of using credentials from another
495 application to authenticate to phpMyAdmin.</li>
496 <li>The other application has to store login information into
497 session data.</li>
499 section.</li>
500 </ul>
503 <ul><li>This mode is the less secure one because it requires you to fill the
505 $cfg['Servers'][$i]['user']</a> and
507 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
508 can read your config.inc.php can discover your username and password).
509 <br />
516 is an entry explaining how to protect your configuration file.</li>
517 <li>For additional security in this mode, you may wish to consider the Host
518 authentication
520 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
522 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
523 directives.</li>
524 <li>Unlike cookie and http, does not require a user to log in when first
525 loading the phpMyAdmin site. This is by design but could allow any
526 user to access your installation. Use of some restriction method is
528 HTTP-AUTH directive or disallowing incoming HTTP requests at
529 one’s router or firewall will suffice (both of which
530 are beyond the scope of this manual but easily searchable with Google).</li>
531 </ul>
533 <p>
534 The Swekey is a low cost authentication USB key that can be used in
535 web applications.<br /><br />
536 When Swekey authentication is activated, phpMyAdmin requires the
537 users's Swekey to be plugged before entering the login page (currently
538 supported for cookie authentication mode only). Swekey Authentication is
539 disabled by default.<br /><br />
541 </p>
542 <pre>
543 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
544 </pre>
545 <p>
547 each user with their Swekey Id. It is important to place this file outside
548 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
550 users' information.<br /><br />
551 If you want to purchase a Swekey please visit
553 since this link provides funding for phpMyAdmin.
554 </p>
555 <!-- CONFIGURATION -->
559 users:</span> PHP does not seem to like
563 before saving a script you have modified.</p>
568 section to create one. This file only needs to contain the parameters you want to
569 change from their corresponding default value in
572 <p> The parameters which relate to design (like colors) are placed in
575 your site specific code to be included on start and end of each page.</p>
579 (with full path) to your phpMyAdmin installation's directory.
582 some web servers are case–sensitive.
585 Starting with version 2.3.0, it is advisable to try leaving this
586 blank. In most cases phpMyAdmin automatically detects the proper
587 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
588 href="https://sourceforge.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
589 A good test is to browse a table, edit a row and save it. There should
590 be an error message if phpMyAdmin is having trouble auto–detecting
591 the correct value. If you get an error that this must be set or if
592 the autodetect code fails to detect your path, please post a bug
593 report on our bug tracker so we can improve the code.</dd>
597 with master / foreign – tables (see
599 <br />
600 If you tried to set this up and it does not work for you, have a look on
602 use it. You will find a link that will analyze why those features have
603 been disabled.<br />
604 If you do not want to use those features set this variable to
608 <dd>A warning is displayed on the main page if Suhosin is detected.
610 from appearing.</dd>
613 <dd>Disable the default warning that is displayed if mcrypt is missing for
614 cookie authentication.
616 from appearing.</dd>
620 domain to call phpMyAdmin inside a frame, and is a potential security
621 hole allowing cross-frame scripting attacks.</dd>
625 algorithm to encrypt the password.<br />
627 passphrase of your choice. It will be used internally by the blowfish
628 algorithm: you won’t be prompted for this passphrase. The maximum
631 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
632 makes a bit weaker security as this generated secret is stored in
633 session and furthermore it makes impossible to recall user name from
634 cookie.</dd>
638 MySQL servers. Therefore, a
640 been added which contains the login information for the different servers.
641 The first
643 contains the hostname of the first server, the second
645 the hostname of the second server, etc. In
647 server definition, however you can put as many as you need in
649 have to define all settings, just those you need to change).</dd>
653 $i-th MySQL-server. E.g. localhost.</dd>
658 ignores this port number and connects with the socket, so if you want
659 to connect to a port different from the default port, use
662 </dd>
666 To determine the correct socket, check your MySQL configuration or, using the
668 Among the resulting information displayed will be the socket used.</dd>
671 <dd>Whether to enable SSL for connection to MySQL server.
672 </dd>
675 <dd>What type connection to use with the MySQL server. Your options are
677 is nearly guaranteed to be available on all MySQL servers, while
678 sockets are not supported on some platforms.<br /><br />
680 To use the socket mode, your MySQL server must be on the same machine
681 as the Web server.</dd>
684 <dd>What php MySQL extension to use for the connection. Valid options are:
685 <br /><br />
688 The classic MySQL extension. This is the recommended and default
689 method at this time.<br /><br />
692 The improved MySQL extension. This extension became available
693 with php 5.0.0 and is the recommended way to connect to a server
697 <dd>Whether to use a compressed protocol for the MySQL server connection
698 or not (experimental).<br />
704 </dt>
706 all relational features (see
708 and, for a MySQL server previous to 4.1.2 or running with
711 authentication mode).<br /><br />
714 cookie authentication modes (or 'config'
715 authentication mode since phpMyAdmin 2.2.1), you need to supply the
720 This account is used to check what databases the user will see at
721 login.<br />
725 In phpMyAdmin versions before 2.2.5, those were called
729 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
730 <dd>Whether config or cookie or
732 should be used for this server.
734 is the plain old way: username and password are stored in
736 <li>'cookie' authentication mode
738 2.2.3 allows you to log in as any valid MySQL user with the
739 help of cookies. Username and password are stored in
740 cookies during the session and password is deleted when it
741 ends. This can also allow you to log in in arbitrary server if
742 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
743 </li>
744 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
745 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
746 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
747 <li>'signon' authentication mode
749 as introduced in 2.10.0 allows you to log in from prepared PHP
750 session data. This is useful for implementing single signon
751 from another application. Sample way how to seed session is in
757 </ul>
760 for more information.
761 </dd>
763 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
764 </dt>
765 <dd>
767 names for hardware authentication. Leave empty to deactivate this feature.
768 </dd>
772 </dt>
773 <dd>
774 When using auth_type = 'config', this is the user/password-pair
775 which phpMyAdmin will use to connect to the
776 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
777 cookie authentication is used and should be empty.</dd>
779 <span
781 </dt>
782 <dd>
783 Allow attempt to log in without password when a login with password
784 fails. This can be used together with http authentication, when
785 authentication is done some other way and phpMyAdmin gets user name
786 from auth and uses empty password for connecting to MySQL. Password
787 login is still tried first, but as fallback, no password method is
788 tried.</dd>
791 </dt>
792 <dd>
793 If set to a (an array of) database name(s), only this (these) database(s)
794 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
795 database(s) name(s) may contain MySQL wildcards characters
799 This setting is an efficient way to lower the server load since the
800 latter does not need to send MySQL requests to build the available
802 privileges rules of the MySQL database server</span>. If set, it just
803 means only these databases will be displayed but
805 <br /><br />
807 An example of using more that one database:
809 <br /><br />
811 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
812 databases in the left frame, so that you can individually arrange your databases.<br />
813 If you want to have certain databases at the top, but don't care about the others, you do not
814 need to specify all other databases. Use:
816 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
817 order.</dd>
820 </dt>
821 <dd>Regular expression for hiding some databases. This only hides them
822 from listing, but a user is still able to access them (using, for example,
823 the SQL query area). To limit access, use the MySQL privilege system.
824 <br /><br />
829 More information on regular expressions can be found in the
831 PCRE pattern syntax</a> portion of the PHP reference manual.
832 </dd>
835 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
836 this string will be displayed instead of the hostname in the pull-down
837 menu on the main page. This can be useful if you want to show only
838 certain databases on your system, for example. For HTTP auth, all
839 non-US-ASCII characters will be stripped.</dd>
843 </dt>
844 <dd>The name of the database containing the linked-tables infrastructure.
845 <br /><br />
848 section in this document to see the benefits of this infrastructure,
849 and for a quick way of creating this database and the needed tables.
850 <br /><br />
852 If you are the only user of this phpMyAdmin installation, you can
853 use your current database to store those special tables; in this
854 case, just put your current database name in
856 set this parameter to the name of your central database containing
857 the linked-tables infrastructure.</dd>
861 </dt>
863 useful for queries you often run.<br /><br />
865 To allow the usage of this functionality:
867 <li>enter the table name in
869 </ul>
870 </dd>
874 </dt>
876 which field is a key in another table (a foreign key). phpMyAdmin
877 currently uses this to
878 <ul><li>make clickable, when you browse the master table, the data values
879 that point to the foreign table;</li>
881 when browsing the master table, if you move the mouse to a column
882 containing a foreign key (use also the 'table_info' table);<br />
885 <li>in edit/insert mode, display a drop-down list of possible foreign
889 <li>display links on the table properties page, to check referential
890 integrity (display missing foreign keys) for each described key;
891 </li>
895 schema of your database (also uses the table_coords table).</li>
896 </ul>
898 The keys can be numeric or character.<br /><br />
900 To allow the usage of this functionality:
903 infrastructure</li>
904 <li>put the relation table name in
906 <li>now as normal user open phpMyAdmin and for each one of your
907 tables where you want to use this feature, click
909 </li>
910 </ul>
914 future development of the cross-db relations.
915 </dd>
919 </dt>
920 <dd>
921 Since release 2.3.0 you can describe, in a special 'table_info'
922 table, which field is to be displayed as a tool-tip when moving the
923 cursor over the corresponding key.<br />
924 This configuration variable will hold the name of this special
925 table. To allow the usage of this functionality:
927 <li>put the table name in
929 <li>then for each table where you want to use this feature,
931 to choose the field.</li>
932 </ul>
934 </dd>
938 </dt>
941 the relations between your tables. To do this it needs two tables
946 schema output).<br /><br />
950 To allow the usage of this functionality:
953 infrastructure</li>
954 <li>put the correct table names in
957 </ul>
960 </dd>
964 </dt>
966 Since release 2.3.0 you can store comments to describe each column for
968 <br /><br />
970 Starting with release 2.5.0, comments are consequently used on the table
971 property pages and table browse view, showing up as tool-tips above the
972 column name (properties page) or embedded within the header of table in
973 browse view. They can also be shown in a table dump. Please see the
974 relevant configuration directives later on.<br /><br />
976 Also new in release 2.5.0 is a MIME-transformation system which is also
978 Transformations</a> for further information. To use the
979 MIME-transformation system, your column_info table has to have the three
980 new fields 'mimetype', 'transformation', 'transformation_options'.
981 <br /><br />
983 To allow the usage of this functionality:
985 infrastructure</li>
986 <li>put the table name in
990 <pre>
991 ALTER TABLE `pma_column_comments`
992 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
993 ADD `transformation` VARCHAR( 255 ) NOT NULL,
994 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
995 </pre>
998 renamed from<br />
1001 </ul>
1002 </dd>
1006 </dt>
1009 all queries you entered manually into the phpMyAdmin interface. If you
1010 don't want to use a table-based history, you can use the JavaScript-based
1011 history. Using that, all your history items are deleted when closing the
1012 window.<br /><br />
1014 Using
1016 you can specify an amount of history items you want to have on hold. On
1017 every login, this list gets cut to the maximum amount.<br /><br />
1019 The query history is only available if JavaScript is enabled in your
1020 browser.<br /><br />
1022 To allow the usage of this functionality:
1025 infrastructure</li>
1027 </li>
1028 </ul>
1029 </dd>
1033 </dt>
1035 to visually manage the relations.
1036 <br /><br />
1038 To allow the usage of this functionality:
1041 infrastructure</li>
1043 </li>
1044 </ul>
1045 </dd>
1048 </dt>
1050 column_info table got enhanced with three new fields. If the above variable
1052 latest table structure available. If not, it will emit a warning to the
1053 superuser.<br /><br />
1055 You can disable this checking behavior by setting the variable to false,
1056 which should offer a performance increase.<br /><br />
1058 Recommended to set to FALSE, when you are sure, your table structure is
1059 up to date.</dd>
1061 boolean</dt>
1062 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1063 </dd>
1065 boolean</dt>
1066 <dd>Whether to allow logins without a password. The default
1068 to a MySQL server with was left with an empty password for root or
1069 on which an anonymous (blank) user is defined.
1070 </dd>
1073 </dt>
1075 authentication is disabled.<br /><br />
1078 all deny rules followed by allow rules. Access is allowed by default. Any
1079 client which does not match a Deny command or does match an Allow command
1080 will be allowed access to the server. <br /><br />
1083 applies all allow rules followed by deny rules. Access is denied by
1084 default. Any client which does not match an Allow directive or does
1085 match a Deny directive will be denied access to the server.<br /><br />
1087 If your rule order is set to 'explicit', the authentication is
1088 performed in a similar fashion to rule order 'deny,allow', with the
1092 and was available in Apache by specifying allow and deny rules without
1093 setting any order.<br /><br />
1095 Please also see <a
1097 address behind proxies.
1098 </dd>
1100 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1101 </dt>
1102 <dd>The general format for the rules is as such:
1104 <pre>
1106 </pre>
1111 well (please note that those containing SERVER_ADDRESS might not be
1112 available on all webservers):
1113 <pre>
1119 </pre>
1121 Having an empty rule list is equivalent to either using
1127 following work:<br />
1129 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1130 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1131 But the following does not work:<br />
1134 Also IPv6 addresses are not supported.
1135 </dd>
1136 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1137 <dd>Name of session which will be used for signon authentication method.
1138 </dd>
1140 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1141 </dd>
1143 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1144 </dd>
1147 <dd>If you have more than one server configured, you can set
1149 that server when phpMyAdmin is started, or set it to 0 to be given a
1150 list of servers without logging in.<br />
1152 MUST be set to that server.</dd>
1155 <dd>The maximum number of database names to be displayed in the
1156 navigation frame and the database list.</dd>
1159 <dd>The maximum number of table names to be displayed in the
1160 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1161 when in Light mode.</dd>
1164 <dd>The maximum number of characters when a SQL query is displayed. The
1165 default limit of 1000 should be correct to avoid the display of tons
1166 of hexadecimal codes that represent BLOBs, but some users have real
1167 SQL queries that are longer than 1000 characters. Also, if a query's
1168 length exceeds this limit, this query is not saved in the history.</dd>
1171 <dd>Defines whether to use GZip output buffering for increased
1173 Set to true/false for enabling/disabling. When set to 'auto' (string),
1174 phpMyAdmin tries to enable output buffering and will automatically disable
1175 it if your browser has some problems with buffering. IE6 with a certain patch
1176 is known to cause data corruption when having enabled buffering.</dd>
1179 <dd>Whether persistent connections should be used or not (mysql_connect or
1180 mysql_pconnect).</dd>
1186 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1187 to zero, no time limit is imposed.<br />
1188 This setting is used while importing/exporting dump files but has no
1189 effect when PHP is running in safe mode.</dd>
1192 <dd>Set the number of bytes a script is allowed to allocate. If number set
1193 to zero, no limit is imposed.<br />
1194 This setting is used while importing/exporting dump files but has no
1195 effect when PHP is running in safe mode.<br />
1199 <dd>Mark used tables and make it possible to show databases with locked
1204 generated by phpMyAdmin should be displayed or not.</dd>
1207 <dd>Defines whether normal users (non-administrator) are allowed to
1208 delete their own database or not. If set as FALSE, the link "Drop
1210 mydatabase" will be rejected. Quite practical for
1212 customers.<br />
1213 Please note that this limitation of SQL queries is not as strict as
1214 when using MySQL privileges. This is due to nature of SQL queries
1215 which might be quite complicated. So this choice should be viewed as
1216 help to avoid accidental dropping rather than strict privilege
1217 limitation.</dd>
1221 displayed when you're about to lose data.</dd>
1224 <dd>Define whether the previous login should be recalled or not in cookie
1225 authentication mode.<br /><br />
1227 This is automatically disabled if you do not have configured
1229 </dd>
1232 <dd>Define how long is login cookie valid. Please note that php
1233 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1234 might limit session validity and if session is lost, login cookie is
1236 at least as high is $cfg['LoginCookieValidity'] is set.</dd>
1240 means that it will be kept for existing session. This is recommended
1241 for not trusted environments.</dd>
1244 <dd>If enabled (default), logout deletes cookies for all servers,
1245 otherwise only for current one. Setting this to false makes it easy to
1246 forget to log out from other server, when you are using more of
1247 them.</dd>
1253 <dd>Define whether phpMyAdmin will continue executing a multi-query
1254 statement if one of the queries fails. Default is to abort execution.</dd>
1257 <dd>Define whether phpMyAdmin will output the results of each query of a
1258 multi-query statement embedded into the
1263 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1264 <br /><br />
1267 MySQL servers behind the firewall where your
1269 </dd>
1272 <dd>Defines whether to use a select-based menu and display only the current
1273 tables in the left frame (smaller page). Only in Non-Lightmode you can
1274 use the feature to display nested folders using
1276 </dd>
1279 <dd>In light mode, defines whether to display the names of databases (in the
1280 selector) using a tree, see also
1282 </dd>
1285 string or array</dt>
1286 <dd>The string used to separate the parts of the database name when showing
1287 them in a tree. Alternatively you can specify more strings in an array
1288 and all of them will be used as a separator.</dd>
1291 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1292 This means if you have tables like 'first__second__third' this will be
1294 If set to FALSE or empty, the feature is disabled. NOTE: You should
1295 not use this separator at the beginning or end of a
1296 table name or multiple times after another without any other
1297 characters in between.</dd>
1300 <dd>Defines how many sublevels should be displayed when splitting
1301 up tables by the above separator.</dd>
1304 <dd>Defines whether to display table comment as tool-tip in left frame or
1305 not.</dd>
1308 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1309 comment and the real name. That means that if you have a table called
1310 'user0001' and add the comment 'MyName' on it, you will see the name
1311 'MyName' used consequently in the left frame and the tool-tip shows
1312 the real name of the DB.</dd>
1315 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1317 When setting this to 'nested', the Alias of the Tablename is only used
1318 to split/nest the tables according to the
1320 directive. So only the folder is called like the Alias, the tablename itself
1321 stays the real tablename.</dd>
1324 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1327 <dd>Enter URL where logo in the navigation frame will point to.
1328 For use especially with self made theme which changes this.
1337 <dd>Defines whether or not to display a server choice at the top of the left frame.
1338 Defaults to FALSE.</dd>
1340 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1341 Defaults to FALSE (drop-down).</dd>
1343 <dd>Defines whether to display database choice in light navigation frame as links
1344 instead of in a drop-down. Defaults to 'auto' - on main page list is
1345 shown, when database is selected, only drop down is displayed.</dd>
1348 <dd>Defines the tab displayed by default when clicking the small
1349 icon next to each table name in the navigation panel. Possible
1355 <dd>Defines whether or not to display space usage and statistics about databases
1356 and tables.<br />
1357 Note that statistics requires at least MySQL 3.23.3 and that, at this
1358 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1361 <dd>Defines whether to display detailed server information on main page.
1362 You can additionally hide more information by using
1364 </dd>
1369 </dt>
1372 not at the starting main (right) frame. This setting
1373 does not check MySQL commands entered directly.<br /><br />
1375 Please note that to block the usage of phpinfo() in scripts, you
1382 hard coded password value in the configuration file, end users can't
1383 be allowed to change their passwords.</dd>
1386 <dd>Defines whether to suggest a database name on the
1390 <dd>Defines whether navigation bar buttons and the right panel top menu
1391 contain text or symbols only. A value of TRUE displays icons, FALSE
1392 displays text and 'both' displays both icons and text.</dd>
1395 <dd>Defines whether a user should be displayed a
1399 <dd>Number of rows displayed when browsing a result set. If the result set
1406 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1410 from editing when browsing a table's content. Valid values are:
1415 </ul>
1416 </dd>
1419 <dd>Defines whether or not MySQL functions fields should be initially
1420 displayed in edit/insert mode. Since version 2.10, the user can
1421 toggle this setting from the interface.
1422 </dd>
1425 <dd>Defines which type of editing controls should be used for CHAR and
1426 VARCHAR fields. Possible values are:
1427 <ul><li>input - this allows to limit size of text to size of field in
1428 MySQL, but has problems with newlines in fields</li>
1429 <li>textarea - no problems with newlines in fields, but also no
1430 length limitations</li>
1431 </ul>
1432 Default is old behavior so input.</dd>
1438 <dd>If there are fewer items than this in the set of foreign keys, then a
1439 drop-down box of foreign keys is presented, in the style described by the
1441 setting.</dd>
1444 <dd>For the foreign key drop-down fields, there are several methods of
1445 display, offering both the key and value data. The contents of the
1446 array should be one or both of the following strings:
1452 </dt>
1453 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1454 creating a dump file</dd>
1457 </dt>
1458 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1459 compressed exports. This doesn't affect smaller dumps and allows users to
1460 create larger dumps that won't otherwise fit in memory due to php
1461 memory limit. Produced files contain more GZip/BZip2 headers, but all
1462 normal programs handle this correctly.</dd>
1466 mainframe.</dd>
1470 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1475 <dd>How many columns will be utilized to display the tables on the
1476 database property view? Default is 1 column. When setting this to a
1477 value larger than 1, the type of the database will be omitted for more
1478 display space.</dd>
1482 <dd>Defines the tab displayed by default on server view. Possible
1489 <dd>Defines the tab displayed by default on database view. Possible
1494 <dd>Defines the tab displayed by default on table view. Possible
1501 points to the MySQL documentation (type depends
1502 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1503 generated.<br />
1505 for more information about MySQL manuals and their types.</dd>
1508 <dd>Type of MySQL documentation:
1514 </ul>
1515 </dd>
1518 <dd>Defines the default language to use, if not browser-defined or
1519 user-defined.<br />
1521 this setting.</dd>
1524 <dd>Defines the default connection collation to use, if not
1525 user-defined.<br />
1530 <dd>Force: always use this language (must be defined in the
1534 <dd>Limit list of available languages to those matching the given regular
1535 expression. For example if you want only Czech and English, you should
1539 <dd>Default character set to use for recoding of MySQL queries. This must be
1540 enabled and it's described by
1542 option.<br />
1543 You can give here any character set which is in
1545 array and this is just default choice, user can select any of them.</dd>
1548 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1549 support (compiled in or module) in PHP to allow MySQL queries recoding
1550 and used language file must have it enabled (by default only these
1551 which are in Unicode, just to avoid losing some characters).<br /><br />
1554 in the Export and Import pages, to choose the character set when
1555 exporting a file. The default value in this menu comes from
1557 </dd>
1560 <dd>You can select here which functions will be used for character set
1561 conversion. Possible values are:
1562 <ul><li>auto - automatically use available one (first is tested
1563 iconv, then recode)</li>
1566 </ul>
1567 Default is auto.</dd>
1570 <dd>Specify some parameters for iconv used in charset conversion. See
1573 used, so that invalid characters will be transliterated.</dd>
1576 <dd>Available character sets for MySQL conversion. You can add your own (any of
1577 supported by recode/iconv) or remove these which you don't use.
1578 Character sets will be shown in same order as here listed, so if you
1579 frequently use some of these move them to the top.</dd>
1584 default empty, you need to fill in some trusted proxy servers if you
1585 want to use rules for IP addresses behind proxy.<br /><br />
1587 The following example specifies that phpMyAdmin should trust a
1589 <pre>
1590 $cfg['TrustedProxies'] =
1592 </pre>
1593 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1594 client's IP address as usual.
1595 </dd>
1599 MIME transformations.<br />
1600 Possible values are:
1601 <ul><li>auto - automatically detect, this is a bit expensive
1603 according to your server real possibilities</li>
1606 </ul>
1607 Default is auto.
1608 </dd>
1611 <dd>
1612 We normally check the permissions on the configuration file to ensure
1613 it's not world writable. However, phpMyAdmin could be installed on
1614 a NTFS filesystem mounted on a non-Windows server, in which case the
1615 permissions seems wrong but in fact cannot be detected. In this case
1617 </dd>
1620 <dd>
1621 Limit for length of URL in links. When length would be above this limit, it
1622 is replaced by form with button.
1623 This is required as some web servers (IIS) have problems with long URLs.
1625 </dd>
1629 </dd>
1631 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1632 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1633 </dt>
1634 <dd>The background styles used for both the frames.
1637 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1639 <dd>The style used for the pointer in the navi frame.
1643 </dt>
1644 <dd>The color used for the database name in the navi frame.
1653 </dd>
1657 <dd>The style used for table headers. See
1662 </dd>
1666 </dd>
1668 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1670 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1672 </dt>
1674 The former feature highlights the row over which your mouse is passing
1675 and the latter lets you visually mark/unmark rows by clicking on
1676 them.<br />
1681 <dd>You put here a valid CSS font family value, for example
1686 <dd>You put here a valid CSS font family value, for example
1700 </dt>
1702 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1704 The Char* values are used for CHAR and VARCHAR editing (if configured
1708 </dt>
1712 </dt>
1713 <dd>Defines if the whole textarea of the query box will be selected on
1714 click.</dd>
1717 </dt>
1718 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1719 editing.</dd>
1722 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1723 Can be turned off by a toggle button on the browse page.</dd>
1727 </dt>
1728 <dd>Defines the place where modify and delete links would be put when
1729 tables contents are displayed (you may have them displayed both at the
1730 left and at the right).
1736 </dt>
1738 Define which one is displayed by default. The first mode displays each
1739 row on a horizontal line, the second rotates the headers by 90
1740 degrees, so you can use descriptive headers even though fields only
1741 contain small values and still print them out. The vertical mode sorts
1742 each row on a vertical lineup.<br /><br />
1744 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1745 the rotation of the header for horizontalflipped is done via CSS. If
1746 set to 'fake' PHP does the transformation for you, but of course this
1747 does not look as good as CSS.</dd>
1751 string or integer</dt>
1752 <dd>When editing/creating new columns in a table all fields normally get
1753 lined up one field a line. (default: 'horizontal'). If you set this to
1754 'vertical' you can have each field lined up vertically beneath each
1755 other. You can save up a lot of place on the horizontal direction and
1756 no longer have to scroll. If you set this to integer, editing of fewer
1757 columns will appear in 'vertical' mode, while editing of more fields
1758 still in 'horizontal' mode. This way you can still effectively edit
1759 large number of fields, while having full view on few of them.</dd>
1763 </dt>
1765 display of column comments in Browse or Property display. In browse
1766 mode, the comments are shown inside the header. In property mode,
1767 comments are displayed using a CSS-formatted dashed-line below the
1768 name of the field. The comment is shown as a tool-tip for that field.
1769 </dd>
1781 <dd>Whether to display a link to validate a query in any SQL Query box.
1788 <dd>
1789 The name of the directory where
1791 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1792 are available under a drop-down box when you click the database or
1793 table name, then the Import tab.
1794 <br /><br />
1796 If you want different directory for each user, %u will be replaced
1797 with username.<br /><br />
1801 compressed formats is enabled).<br /><br />
1803 This feature is useful when your file is too big to be uploaded via
1805 uploads are disabled in PHP.<br /><br />
1807 Please note that if PHP is running in safe mode, this directory must
1808 be owned by the same user as the owner of the phpMyAdmin scripts.
1809 <br /><br />
1813 alternatives.
1814 </dd>
1817 <dd>
1818 The name of the directory where dumps can be saved.<br /><br />
1820 If you want different directory for each user, %u will be replaced
1821 with username.<br /><br />
1823 Please note that the directory must exist and has to be writable for
1824 the user running webserver.<br /><br />
1826 Please note that if PHP is running in safe mode, this directory must
1827 be owned by the same user as the owner of the phpMyAdmin scripts.
1828 </dd>
1831 <dd>
1832 The name of the directory where temporary files can be stored.
1833 <br /><br />
1835 This is needed for native MS Excel export, see
1841 <br /><br />
1843 If the directory where phpMyAdmin is installed is subject to an
1845 temporary directory in some directory accessible by the web
1846 server. However for security reasons, this directory should be outside
1847 the tree published by webserver. If you cannot avoid having this
1848 directory published by webserver, place at least an empty
1850 possible.
1851 <br /><br />
1853 This directory should have as strict permissions as possible as the only
1854 user required to access this directory is the one who runs the
1855 webserver. If you have root privileges, simply make this user owner of
1856 this directory and make it accessible only by it:
1857 <br /><br />
1859 <pre>
1860 chown www-data:www-data tmp
1861 chmod 700 tmp
1862 </pre>
1864 If you cannot change owner of the directory, you can achieve a similar
1867 <pre>
1868 chmod 700 tmp
1869 setfacl -m "g:www-data:rwx" tmp
1870 setfacl -d -m "g:www-data:rwx" tmp
1871 </pre>
1873 If neither of above works for you, you can still make the directory
1875 system reading and writing data in this directory.
1876 </dd>
1879 <dd>
1880 In this array are defined default parameters for export, names of
1881 items are similar to texts seen on export page, so you can easily
1882 identify what they mean.
1883 </dd>
1886 <dd>
1887 In this array are defined default parameters for import, names of
1888 items are similar to texts seen on import page, so you can easily
1889 identify what they mean.
1890 </dd>
1893 <dd>
1894 Repeat the headers every X cells, or 0 to deactivate.
1895 </dd>
1903 </dt>
1904 <dd>
1905 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
1906 or icon is always displayed on the left panel. If JavaScript is enabled in
1907 your browser, a click on this opens a distinct query window, which is
1908 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
1909 changes to display a query box.<br /><br />
1911 The size of this query window can be customized with
1913 - both integers for the size in pixels. Note that normally, those
1915 theme you are using.<br /><br />
1919 opens the query window and puts the current query
1920 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
1921 query in the right panel's query box.
1922 <br /><br />
1923 The usage of the JavaScript query window is recommended if you have a
1924 JavaScript enabled browser. Basic functions are used to exchange quite
1925 a few variables, so most 4th generation browsers should be capable to
1926 use that feature. It currently is only tested with Internet Explorer 6
1927 and Mozilla 1.x.
1928 <br /><br />
1930 to a table, which has to be created by you (see <a
1932 all your queries will be appended to the form, but only as long as
1933 your window is opened they remain saved.
1934 <br /><br />
1935 When using the JavaScript based query window, it will always get
1936 updated when you click on a new table/db to browse and will focus if
1937 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
1938 the query window by checking the box "Do not overwrite this query from
1939 outside the window" below the query textarea. Then you can browse
1940 tables/databases in the background without losing the contents of the
1941 textarea, so this is especially useful when composing a query with
1942 tables you first have to look in. The checkbox will get automatically
1943 checked whenever you change the contents of the textarea. Please
1944 uncheck the button whenever you definitely want the query window to
1945 get updated even though you have made alterations.
1946 <br /><br />
1949 <br /><br />
1950 The query window also has a custom tabbed look to group the features.
1952 default tab to be used when opening the query window. It can be set to
1953 either 'sql', 'files', 'history' or 'full'.</dd>
1959 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
1961 If the approximate row count as returned by
1964 count will be used.
1965 </dd>
1967 <dd>For VIEWs, since obtaining the exact count could have an
1968 impact on performance, this value is the maximum to be displayed, using
1970 any row counting.
1971 </dd>
1975 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
1977 page. By clicking on the button 'toggle scratchboard' on the page
1978 where you edit x/y coordinates of those elements you can activate a
1979 scratchboard where all your elements are placed. By clicking on an
1980 element, you can move them around in the pre-defined area and the x/y
1981 coordinates will get updated dynamically. Likewise, when entering a
1982 new position directly into the input field, the new position in the
1983 scratchboard changes after your cursor leaves the input field.<br />
1984 You have to click on the 'OK'-button below the tables to save the new
1985 positions. If you want to place a new element, first add it to the
1986 table of elements and then you can drag the new element around.<br />
1987 By changing the paper size and the orientation you can change the size
1988 of the scratchboard as well. You can do so by just changing the
1989 dropdown field below, and the scratchboard will resize automatically,
1990 without interfering with the current placement of the elements.<br />
1991 If ever an element gets out of range you can either enlarge the paper
1992 size or click on the 'reset' button to place all elements below each
1993 other.<br />
1995 get this control to work. The basic Drag&Drop script functionality
1996 was kindly borrowed from www.youngpup.net and is underlying so
1997 specific license.</dd>
2000 <dd>Sorts database and table names according to natural order (for example,
2001 t1, t2, t10). Currently implemented in the left panel (Light mode)
2002 and in Database view, for the table list.</dd>
2013 <dd>Allows you to specify window's title bar. Following magic string can
2014 be used to get special values:
2015 <dl>
2021 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
2030 </dl>
2031 </dd>
2041 </dd>
2044 <dd>If theme manager is active, use this as the path of the subdirectory
2045 containing all the themes.</dd>
2059 </dt>
2060 <dd>Default queries that will be displayed in query boxes when user didn't
2061 specify any. Use %d for database name, %t for table name and %f for a
2062 comma separated list of field names. Note that %t and %f are only
2066 <dd>
2067 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
2068 default we use HTML to format the query, but you can disable this by
2070 </dd>
2073 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2074 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2075 query inside a bracket is indented. By changing
2078 specifies the units of the indent amount that you specified. This is
2079 used via stylesheets.</dd>
2082 <dd>This array is used to define the colours for each type of element of
2083 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2085 If you specify an empty string for the color of a class, it is ignored
2086 in creating the stylesheet.
2087 You should not alter the class names, only the colour strings.<br />
2108 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2112 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2113 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2114 </ul>
2115 </dd>
2119 <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,
2120 as originally published on
2122 <br />
2123 For help in setting up your system to use the service, see the
2125 </dd>
2129 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2130 and any password, so we use those by default. Instead, if
2131 you have an account with them, you can put your login details
2132 here, and it will be used in place of the anonymous login.</dd>
2133 </dl>
2134 </dd>
2137 <dd><b>DEVELOPERS ONLY!</b></dd>
2140 <dd><b>DEVELOPERS ONLY!</b><br />
2141 Enable logging queries and execution times to be displayed in the bottom
2142 of main page (right frame).</dd>
2145 <dd><b>DEVELOPERS ONLY!</b><br />
2146 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2147 the code.<br />
2148 For help in setting up your system to this, see the
2152 <dd><b>DEVELOPERS ONLY!</b><br />
2153 Enable profiling support for phpMyAdmin. This will append a chunk of data
2154 to the end of every page displayed in the main window with profiling
2155 statistics for that page.<br />
2156 You may need to increase the maximum execution time for this to
2157 complete successfully.<i>Profiling was removed from the code for
2158 version 2.9.0 due to licensing issues.</i></dd>
2160 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2161 <dd><b>DEVELOPERS ONLY!</b><br />
2162 When profiling data is displayed, this variable controls the threshold of
2163 display for any profiling data, based on the average time each time has
2164 taken. If it is over the threshold it is displayed, otherwise it is not
2165 displayed. This takes a value in milliseconds. In most cases you don't need
2166 to edit this.</dd>
2169 <dd>All possible types of a MySQL column. In most cases you don't need to
2170 edit this.</dd>
2173 <dd>Possible attributes for fields. In most cases you don't need to edit
2174 this.</dd>
2177 <dd>A list of functions MySQL supports. In most cases you don't need to
2178 edit this.</dd>
2181 <dd>Mapping of column types to meta types used for preferring displayed
2182 functions. In most cases you don't need to edit this.</dd>
2185 <dd>Functions preferred for column meta types as defined in
2186 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2187 to edit this.</dd>
2190 <dd>Functions selected by default when inserting/changing row, Functions
2191 are defined for meta types from
2193 <code>first_timestamp</code>, which is used for first timestamp column
2194 in table.</dd>
2197 <dd>Operators available for search operations on numeric and date fields.
2198 </dd>
2201 <dd>Operators available for search operations on character fields.
2202 Note that we put <code>LIKE</code> by default instead of
2203 <code>LIKE %...%</code>, to avoid unintended performance problems
2204 in case of huge tables.</dd>
2207 <dd>Operators available for search operations on enum fields.</dd>
2210 <dd>Additional operators available for search operations when the
2211 field can be null.</dd>
2213 </dl>
2215 <!-- TRANSFORMATIONS -->
2221 </ol>
2225 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2227 section</a> on how to do so.</p>
2229 <p> You can apply different transformations to the contents of each field. The
2230 transformation will take the content of each field and transform it with
2231 certain rules defined in the selected transformation.</p>
2233 <p> Say you have a field 'filename' which contains a filename. Normally you would
2234 see in phpMyAdmin only this filename. Using transformations you can transform
2235 that filename into a HTML link, so you can click inside of the phpMyAdmin
2236 structure on the field's link and will see the file displayed in a new browser
2237 window. Using transformation options you can also specify strings to
2238 append/prepend to a string or the format you want the output stored in.</p>
2240 <p> For a general overview of all available transformations and their options,
2241 you can consult your
2242 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2243 installation.</p>
2245 <p> For a tutorial on how to effectively use transformations, see our
2247 the official phpMyAdmin homepage.</p>
2251 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2252 clicking on the 'Structure' link for a table). There click on
2253 "Change" (or change icon) and there you will see three new fields at
2254 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2255 'Transformation options'.</p>
2257 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2258 that corresponds to the column's contents. Please note that
2259 transformations are inactive as long as no MIME-type is selected.</li>
2261 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2262 hopefully growing amount of pre-defined transformations. See below for information on
2263 how to build your own transformation.<br />
2265 There are global transformations and mimetype-bound transformations. Global transformations
2266 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2267 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2268 transformations which operate on the main mimetype (like 'image'), which will most likely
2269 take the subtype into regard, and those who only operate on a
2270 specific subtype (like 'image/jpeg').<br />
2272 You can use transformations on mimetypes for which the function was not defined for. There
2273 is no security check for you selected the right transformation, so take care of what the
2274 output will be like.</li>
2276 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2277 transform-function specific options here. Usually the transforms can operate with default
2278 options, but it is generally a good idea to look up the overview to see which options are
2279 necessary.<br />
2281 Much like the ENUM/SET-Fields, you have to split up several options using the format
2282 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2283 parsed as an array, leaving the first value the first element in the array, and so
2284 forth.<br />
2286 If you want to specify a MIME character set you can define it in the transformation_options.
2287 You have to put that outside of the pre-defined options of the specific mime-transform,
2289 for which you can specify 2 options and you want to append a character set, enter "'first
2290 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2292 </ul>
2296 <p> All mimetypes and their transformations are defined through single files in
2297 the directory 'libraries/transformations/'.</p>
2299 <p> They are stored in files to ease up customization and easy adding of new
2300 transformations.</p>
2302 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2303 always work. It makes no sense to apply a transformation to a mimetype, the
2304 transform-function doesn't know to handle.</p>
2306 <p> One can, however, use empty mime-types and global transformations which should work
2307 for many mimetypes. You can also use transforms on a different mimetype they where built
2308 for, but pay attention to option usage as well as what the transformation does to your
2309 field.</p>
2311 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2312 any other transform function and provides some basic functions.</p>
2314 <p> There are 5 possible file names:</p>
2316 <ol><li>A mimetype+subtype transform:<br /><br />
2318 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2320 Please not that mimetype and subtype are separated via '_', which shall
2321 not be contained in their names. The transform function/filename may
2322 contain only characters which cause no problems in the file system as
2323 well as the PHP function naming convention.<br /><br />
2325 The transform function will the be called
2326 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2328 <b>Example:</b><br /><br />
2330 <tt>text_html__formatted.inc.php</tt><br />
2331 <tt>PMA_transform_text_html__formatted()</tt></li>
2333 <li>A mimetype (w/o subtype) transform:<br /><br />
2335 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2337 Please note that there are no single '_' characters.
2338 The transform function/filename may contain only characters which cause
2339 no problems in the file system as well as the PHP function naming
2340 convention.<br /><br />
2342 The transform function will the be called
2343 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2345 <b>Example:</b><br /><br />
2347 <tt>text__formatted.inc.php</tt><br />
2348 <tt>PMA_transform_text__formatted()</tt></li>
2350 <li>A mimetype+subtype without specific transform function<br /><br />
2352 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2354 Please note that there are no '__' characters in the filename. Do not
2355 use special characters in the filename causing problems with the file
2356 system.<br /><br />
2358 No transformation function is defined in the file itself.<br /><br />
2360 <b>Example:</b><br /><br />
2362 <tt>text_plain.inc.php</tt><br />
2363 (No function)</li>
2365 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2367 <tt>[mimetype].inc.php</tt><br /><br />
2369 Please note that there are no '_' characters in the filename. Do not use
2370 special characters in the filename causing problems with the file system.
2371 <br /><br />
2373 No transformation function is defined in the file itself.<br /><br />
2375 <b>Example:</b><br /><br />
2377 <tt>text.inc.php</tt><br />
2378 (No function)</li>
2380 <li>A global transform function with no specific mimetype<br /><br />
2382 <tt>global__[transform].inc.php</tt><br /><br />
2384 The transform function will the be called
2385 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2387 <b>Example:</b><br /><br />
2389 <tt>global__formatted</tt><br />
2390 <tt>PMA_transform_global__formatted()</tt></li>
2391 </ol>
2393 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2394 transform function.</p>
2396 <p> All filenames containing no '__' in themselves are not shown as valid transform
2397 functions in the dropdown.</p>
2399 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2400 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2401 without a transform function. Also note the introduction of a function description in
2402 the language files. For each function a $strTransformation_[filename without .inc.php]
2403 has to exist.</p>
2405 <p> You can use the template generator to generate new functions and entries in the
2406 language file.</p>
2408 <p> To create a new transform function please see
2409 <tt>libraries/transformations/template_generator.sh</tt>.
2410 To create a new, empty mimetype please see
2411 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2413 <p> A transform function always gets passed three variables:</p>
2415 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2416 you want to transform.</li>
2417 <li><b>$options</b> - Contains any user-passed options to a transform function
2418 as an array.</li>
2419 <li><b>$meta</b> - Contains an object with field information to your column.
2420 The data is drawn from the output of the
2422 function. This means, all object properties described on the
2424 available in this variable and can be used to transform a field accordingly
2425 to unsigned/zerofill/not_null/... properties.<br />
2426 The $meta->mimetype variable contains the original MIME-type of the
2427 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2428 </ol>
2430 <!-- FAQ -->
2437 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2441 </ol>
2443 <p> Please have a look at our
2445 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2446 features and or interface.</p>
2452 action is required or phpMyAdmin sends a blank page or a page full of
2453 cryptic characters to my browser, what can I do?</a></h4>
2455 <p> There are some known PHP bugs with output buffering and compression.<br />
2457 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2458 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2459 configuration file.<br />
2460 Furthermore, we know about such problems connected to the release
2461 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2462 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2467 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2468 See also the
2470 entry about PHP bugs with output buffering.<br />
2471 If your server keeps crashing, please ask for help in the various Apache
2472 support groups.</p>
2476 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2477 script: I'm always displayed the login screen.</a></h4>
2479 <p> This is a known PHP bug (see this
2481 official PHP bug database. It means there is and won't be any phpMyAdmin
2482 fix against it because there is no way to code a fix.</p>
2488 application misbehaved by not returning a complete set of
2490 </h4>
2492 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2493 Have a look at the last message in this
2495 official PHP bug database.</p>
2500 and/or many error messages with the
2502 mode.</a></h4>
2504 <p> This is a known problem with the PHP
2506 filter: it's not so stable. Please use instead the cookie authentication mode.
2507 </p>
2512 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2513 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2514 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2515 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2516 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2521 work.</a></h4>
2523 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2524 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2525 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2526 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2527 We faced PHP crashes when trying to download a dump with MS Internet
2528 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2529 this case you should switch to the release version of PHP 4.2.0.</p>
2533 an error about safe mode being in effect.</a></h4>
2535 <p> Your uploaded file is saved by PHP in the "upload dir", as
2536 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2537 the system default is <i>/tmp</i>).<br />
2538 We recommend the following setup for Apache servers running in safe mode,
2539 to enable uploads of files while being reasonably secure:</p>
2541 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2542 <li>give ownership to the Apache server's user.group:
2543 <tt>chown apache.apache /tmp/php</tt></li>
2544 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2545 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2546 <li>restart Apache</li>
2547 </ul>
2551 general file uploads don't work on my system and uploaded files have a
2552 <tt>Content-Type:</tt> header in the first line.</a></h4>
2554 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2555 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2556 So the problem is that this package has a serious bug that was corrected
2557 ages ago in PHP (2001-01-28: see
2559 for more details). The problem is that the bugged package is still
2560 available though it was corrected (see
2562 for more details).<br />
2563 So please download
2564 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2565 and the problem should go away.<br />
2566 And that fixes the \r\n problem with file uploads!</p>
2570 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2571 I'm using the Apache server.</a></h4>
2573 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2574 your <i>httpd.conf</i>:</p>
2578 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2582 uploading a file from the query box.</a></h4>
2584 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2585 restrictions. However you need to create temporary directory and
2587 The uploaded files will be moved there, and after execution of your
2593 <p> The MySQL manual explains how to
2595 reset the permissions</a>.</p>
2600 execute a bookmark.</a></h4>
2602 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2603 cannot access the uploaded query.</p>
2608 submit a query from the convenient text area.</a></h4>
2610 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2611 and try to increase it.</p>
2615 </h4>
2617 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2618 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2619 names to align with current standards.</p>
2624 </h4>
2626 <p> Starting with version 2.7.0, the import engine has been re–written and these
2627 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2628 to take advantage of the new import features.</p>
2630 <p> The first things to check (or ask your host provider to check) are the
2631 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2632 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2633 All of these three settings limit the maximum size of data that can be
2634 submitted and handled by PHP. One user also said that post_max_size
2635 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2637 There exist several workarounds if your upload is too big or your
2638 hosting provider is unwilling to change the settings:</p>
2641 feature. This allows one to
2642 upload a file to the server via scp, ftp, or your favorite file transfer
2643 method. PhpMyAdmin is then able to import the files from the temporary
2645 section</a> of this document.</li>
2647 BigDump</a>) to split the files before uploading. We cannot support this
2648 or any third party applications, but are aware of users having success
2649 with it.</li>
2650 <li>If you have shell (command line) access, use MySQL to import the files
2651 directly. You can do this by issuing the "source" command from
2652 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2653 </ul>
2657 support?</a></h4>
2659 <p> In phpMyAdmin 3.0.x, versions starting with MySQL 5.0.1 are
2660 fully supported. phpMyAdmin may connect to your MySQL server
2661 using PHP's classic
2664 is available in php 5.0.<br />
2665 Either way, the developers of both extensions recommend to use the classic
2666 extension for MySQL 4.0 and below and MySQLi for MySQL 4.1 and newer.<br />
2667 When compiling php, we strongly recommend that you manually link the MySQL
2668 extension of your choice to a MySQL client library of at least the same
2669 minor version since the one that is bundled with some PHP distributions is
2672 If your webserver is running on a windows system, you might want to try
2673 MySQL's
2675 instead of the MySQL / MySQLi extensions that are bundled with the official
2676 php Win32 builds.</p>
2680 message, "Client does not support authentication protocol requested
2681 by server; consider upgrading MySQL client"</a></h5>
2683 <p> You tried to access MySQL with an old MySQL client library. The version of
2684 your MySQL client library can be checked in your phpinfo() output.
2685 In general, it should have at least the same minor version as your server
2689 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2690 changed the authentication hash and your PHP is trying to use the old method.
2692 with the proper client library to match your MySQL installation. Your
2693 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2694 More information (and several workarounds) are located in the
2696 </p>
2700 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2701 capital letter in its name it is changed to lowercase as it should. But
2702 if I try to DROP this table MySQL is unable to find the corresponding
2703 file.</a></h4>
2705 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2706 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2707 directive.</p>
2711 script seems not to know the font face I'm using!</a></h4>
2713 <p> The "FPDF" library we're using for this feature requires some
2714 special files to use font faces.<br />
2716 these files.</p>
2720 check PHP Configuration".</a></h4>
2722 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2723 "MySQL extension". This extension may be part of the PHP
2724 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2725 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2726 to load the extension but failed.<br /><br />
2728 Usually, the problem is solved by installing a software package called
2729 "PHP-MySQL" or something similar.</p>
2734 and I cannot log in using cookie auth.</a></h4>
2736 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2740 so I cannot upload.</a></h4>
2742 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2743 parameter is not set to "on".</p>
2747 a new table the table and field names are changed to lowercase!</a></h4>
2749 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2750 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2751 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2752 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2753 directory and add the following line to the group [mysqld]:</p>
2755 <pre>set-variable = lower_case_table_names=0</pre>
2757 <p> Next, save the file and restart the MySQL service. You can always check the
2758 value of this directive using the query</p>
2760 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2764 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2767 </p>
2771 and I get problems, such as undefined variables when I run a
2774 <p> A tip from Jose Fandos: put a comment on the following two lines
2775 in httpd.conf, like this:</p>
2777 <pre>
2778 # mod_gzip_item_include file \.php$
2780 </pre>
2782 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2783 PHP scripts. Of course you have to restart Apache.</p>
2788 I get the error "No input file specified" when trying to
2789 run phpMyAdmin.</a></h4>
2791 <p> This is a permission problem. Right-click on the phpmyadmin folder
2792 and choose properties. Under the tab Security, click on "Add"
2793 and select the user "IUSR_machine" from the list. Now set his
2794 permissions and it should work.</p>
2798 db_structure.php with plenty of tables).</a></h4>
2801 GZIP output buffering is enabled. If you turn off it (by
2803 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2804 PHP 5.0.0.</p>
2808 message 'Errorcode: 13'. What does this mean?</a></h4>
2810 <p> This can happen due to a MySQL bug when having database / table names with
2811 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2812 To fix this, turn off this directive, convert all database and table names
2813 to lower case and turn it on again. Alternatively, there's a bug-fix
2814 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2818 and the fields are duplicated.</a></h4>
2820 <p> It is possible to configure Apache in such a way that PHP has problems
2821 interpreting .php files.</p>
2823 <p> The problems occur when two different (and conflicting) set of directives
2824 are used:</p>
2826 <pre>
2827 SetOutputFilter PHP
2828 SetInputFilter PHP
2829 </pre>
2831 <p> and</p>
2833 <pre>AddType application/x-httpd-php .php</pre>
2835 <p> In the case we saw, one set of directives was in
2836 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2837 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2838 The recommended way is with <tt>AddType</tt>, so just comment out
2839 the first set of lines and restart Apache:</p>
2841 <pre>
2842 #SetOutputFilter PHP
2843 #SetInputFilter PHP
2844 </pre>
2849 <p> This problem is known to happen when the server is running Turck MMCache
2850 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2855 <p> Yes.<br />
2856 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2857 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2858 <tt>error_reporting</tt> settings.
2859 </p>
2862 <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>
2864 <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>
2867 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2868 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2869 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2870 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2871 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2872 enabled.) Click <tt>OK</tt>.</li>
2873 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2874 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2875 </ol>
2879 PHP 5.0.4 on 64-bit systems?</a></h4>
2881 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2882 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2888 http://server/phpMyAdmin/index.php?server=X&db=database&table=table&target=script. For <tt>server</tt> you use the server number which refers to
2889 the order of the server paragraph in <tt>config.inc.php</tt>.
2890 Table and script parts are optional. If you want
2891 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2892 some configuration. Following lines apply only for <a
2894 that you have enabled some features within global configuration. You need
2895 <code>Options FollowSymLinks</code> and <code>AllowOverride
2896 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2897 you need mod_rewrite to be enabled. Then you just need to create following
2898 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2899 (don't forget to change directory name inside of it):</p>
2901 <pre>
2902 RewriteEngine On
2903 RewriteBase /path_to_phpMyAdmin
2904 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2905 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2906 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2907 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2908 </pre>
2911 <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>
2913 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
2914 following rewrite rule:</p>
2916 <pre>
2917 RewriteEngine On
2918 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
2919 </pre>
2923 </h4>
2924 <p>
2925 There can be many explanations to this and a look at your server's
2926 error log file might give a clue.
2927 </p>
2931 password encryption in cookie auth doesn't work.</a></h4>
2933 <p> If your cluster consist of different architectures, PHP code used for
2934 encryption/decryption won't work correct. This is caused by use of
2935 pack/unpack functions in code. Only solution is to use mcrypt extension
2936 which works fine in this case.</p>
2941 <p> Yes but the default configuration values of Suhosin are known to cause
2942 problems with some operations, for example editing a table with many
2943 columns and no primary key. Tuning information is available at
2945 http://www.hardened-php.net/hphp/troubleshooting.html</a>,
2946 although the parameter names have changed (<tt>suhosin</tt> instead
2948 <tt>SuhosinDisableWarning</tt> directive</a>.
2949 </p>
2953 but then my connection is redirected back to http. What can cause this
2954 behavior?</a></h4>
2956 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
2957 in your Apache configuration. See <a href="http://httpd.apache.org/docs/2.0/mod/mod_ssl.html#ssloptions">http://httpd.apache.org/docs/2.0/mod/mod_ssl.html#ssloptions</a>.</p>
2960 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work,</a></h4>
2962 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
2963 Example from the Apache 2.2 documentation:</p>
2964 <pre>
2965 ProxyPass /mirror/foo/ http://backend.example.com/
2966 ProxyPassReverse /mirror/foo/ http://backend.example.com/
2967 ProxyPassReverseCookieDomain backend.example.com public.example.com
2968 ProxyPassReverseCookiePath / /mirror/foo/
2969 </pre>
2971 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
2972 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
2973 This is not specific to phpmyadmin, it's just the behavior of Apache.
2974 </p>
2976 <pre>
2977 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
2978 ProxyPassReverse /mirror/foo/
2979 http://backend.example.com/%7Euser/phpmyadmin
2980 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
2981 </pre>
2983 <p>See <a href="http://httpd.apache.org/docs/2.2/mod/mod_proxy.html">http://httpd.apache.org/docs/2.2/mod/mod_proxy.html</a>
2984 for more details.</p>
2988 privileges, I get an error about an unknown column.</a></h4>
2990 <p> The MySQL server's privilege tables are not up to date, you need to run
2991 the <tt>mysql_upgrade</tt> command on the server.</p>
2998 headers already sent by ..." is displayed, what's the problem?</a></h4>
3000 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3001 (I.E. no blank lines, no spaces, no characters...) neither before the
3002 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3003 tag at the end. We also got a report from a user under IIS, that used
3004 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3005 contained an end-of-line character (hex 0A) at the end; removing this character
3006 cleared his errors.</p>
3011 <p> Either there is an error with your PHP setup or your username/password is
3012 wrong. Try to make a small script which uses mysql_connect and see if it
3013 works. If it doesn't, it may be you haven't even compiled MySQL support
3014 into PHP.</p>
3018 connect to local MySQL server through socket '/tmp/mysql.sock'
3019 (111) ..." is displayed. What can I do?</a></h4>
3021 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3023 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3024 In your <i>php.ini</i> you will find a line</p>
3026 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3028 <p> change it to</p>
3030 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3032 <p> Then restart apache and it will work.</p>
3034 <p> Here is a fix suggested by Brad Ummer:</p>
3036 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3037 To do this, telnet to your server and go to the MySQL bin directory. In
3038 this directory there should be a file named <i>mysqladmin</i>. Type
3039 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3040 info about your MySQL server, including the socket
3041 (<i>/tmp/mysql.sock</i>, for example).</li>
3042 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3043 phpMyAdmin, you need to complete the socket information in the
3044 <i>config.inc.php</i>.<br />
3045 For example:
3047 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3048 <br /><br />
3050 Please also make sure that the permissions of this file allow to be readable
3051 by your webserver (i.e. '0755').</li>
3052 </ul>
3054 <p> Have also a look at the
3056 corresponding section of the MySQL documentation</a>.</p>
3060 what can I do?</a></h4>
3063 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3064 sometime.<br />
3065 Also have a look at your PHP version number: if it contains "4.0b..."
3066 it means you're running a beta version of PHP. That's not a so good idea,
3067 please upgrade to a plain revision.</p>
3071 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3072 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3074 <p> Check the value you set for the
3076 directive in the phpMyAdmin configuration file.</p>
3080 password: YES)"-error when trying to access a MySQL-Server on a
3081 host which is port-forwarded for my localhost.</a></h4>
3083 <p> When you are using a port on your localhost, which you redirect via
3084 port-forwarding to another host, MySQL is not resolving the localhost
3085 as expected.<br />
3086 Erik Wasser explains: The solution is: if your host is "localhost"
3087 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
3088 connection for speeding up things. And that doesn't work in this configuration
3089 with port forwarding.<br />
3095 <p> Themes are configured with
3099 <br />
3101 should not delete the directory "original" or its underlying
3102 structure, because this is the system theme used by phpMyAdmin.
3103 "original" contains all images and styles, for backwards
3104 compatibility and for all themes that would not include images or css-files.
3105 <br /><br />
3108 is enabled, you can select your favorite theme on the main page. Your
3109 selected theme will be stored in a cookie.<br /><br /></p>
3111 <p> To create a theme:</p>
3113 <ul><li>make a new subdirectory (for example "your_theme_name") under
3115 (by default <tt>themes</tt>)</li>
3116 <li>copy the files and directories from "original" to
3117 "your_theme_name"</li>
3118 <li>edit the css-files in "your_theme_name/css"</li>
3119 <li>put your new images in "your_theme_name/img"</li>
3120 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3121 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3122 contain your chosen theme name, that will be visible in user interface</li>
3123 <li>make a new screenshot of your theme and save it under
3124 "your_theme_name/screen.png"</li>
3125 </ul>
3127 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3128 theme verbose name, theme generation and theme version. These versions and
3129 generations are enumerated from 1 and do not have any direct dependence on
3130 phpMyAdmin version. Themes within same generation should be backwards
3131 compatible - theme with version 2 should work in phpMyAdmin requiring
3132 version 1. Themes with different generation are incompatible.</p>
3134 <p> If you do not want to use your own symbols and buttons, remove the
3135 directory "img" in "your_theme_name". phpMyAdmin will
3136 use the default icons and buttons (from the system-theme "original").
3137 </p>
3141 what can I do?</a></h4>
3143 <p> Here are a few points to check:</p>
3145 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3147 directive empty. See also
3149 </li>
3150 <li>Maybe you have a broken PHP installation or you need to upgrade
3151 your Zend Optimizer. See
3153 http://bugs.php.net/bug.php?id=31134</a>.
3154 </li>
3155 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3156 set to the default (200) or another low value, you could get this
3157 error if your table has a high number of columns. Adjust this setting
3158 accordingly. (Thanks to Klaus Dorninger for the hint).
3159 </li>
3160 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3161 of ";" will cause this error. Replace it with "&;".
3162 </li>
3164 you might want to increase
3166 </li>
3167 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3168 </li>
3169 </ul>
3176 who logged out can not log in again in with the same nick.</a></h4>
3178 <p> This is related to the authentication mechanism (protocol) used by
3179 phpMyAdmin. To bypass this problem: just close all the opened
3180 browser windows and then go back to phpMyAdmin. You should be able to
3181 log in again.</p>
3185 limit error or a time limit error.</a></h4>
3187 <p> Compressed dumps are built in memory and because of this are limited to
3188 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3189 using
3191 (enabled by default). Zip exports can not be handled this way, so if you need
3192 Zip files for larger dump, you have to use another way.</p>
3196 when I rename a table or a column.</a></h4>
3198 <p> This is an InnoDB bug, see <a href="http://bugs.mysql.com/bug.php?id=21704">http://bugs.mysql.com/bug.php?id=21704</a>.</p>
3202 bundled with the MySQL server distribution.</a></h4>
3204 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3206 <pre>
3207 -- MySQL dump 8.22
3208 --
3209 -- Host: localhost Database: database
3210 ---------------------------------------------------------
3211 -- Server version 3.23.54
3212 </pre>
3214 <p> The invalid part of the code is the horizontal line made of dashes that
3215 appears once in every dump created with mysqldump. If you want to run your
3216 dump you have to turn it into valid MySQL. This means, you have to add a
3217 whitespace after the first two dashes of the line or add a # before it:
3218 <br />
3219 <code>
3220 -- -------------------------------------------------------<br />
3221 </code>
3222 or<br />
3223 <code>
3224 #---------------------------------------------------------
3225 </code>
3226 </p>
3233 <p> Please note that you should not use the separating string multiple times
3234 without any characters between them, or at the beginning/end of your table
3235 name. If you have to, think about using another TableSeparator or disabling
3236 that feature</p>
3241 <p> In Relation view, being able to choose a table in another database,
3242 or having more than one index field in the foreign key.<br /><br/>
3243 In Query-by-example (Query), automatic generation of the query
3244 LEFT JOIN from the foreign table.<br /><br/>
3245 </p>
3249 I get series of errors like "Warning: unable to parse url". How
3250 can this be fixed?</a></h4>
3251 <p>
3252 Your table neither have a primary key nor an unique one, so we must use a
3253 long expression to identify this row. This causes problems to parse_url
3254 function. The workaround is to create a primary or unique key.
3255 <br />
3256 </p>
3260 a MIME-Transformation onto!</a></h4>
3262 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3263 nested forms can be put inside the table where phpMyAdmin displays the results.
3264 You can, however, use any form inside of a table if keep the parent
3265 form-container with the target to tbl_row_delete.php and just put your own
3266 input-elements inside. If you use a custom submit input field, the form will
3267 submit itself to the displaying page again, where you can validate the
3268 $HTTP_POST_VARS in a transformation.
3270 For a tutorial on how to effectively use transformations, see our
3272 on the official phpMyAdmin-homepage.</p>
3276 MySQL server</a></h4>
3278 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3281 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3282 the quote-character (") is interpreted as an identifier quote character and
3283 not as a string quote character, which makes many internal phpMyAdmin
3285 statements. There is no workaround to this behaviour. News to this item will
3286 be posted in Bug report
3287 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3288 </p>
3292 more that one column with the same value
3293 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3294 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3296 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3297 can use it for the Edit and Delete links.</p>
3302 <p> phpMyAdmin uses a quick method to get the row count, and this method
3303 only returns an approximate count in the case of InnoDB tables. See
3305 a way to modify those results, but
3306 this could have a serious impact on performance.</p>
3311 <p> The number of records in queries containing COUNT and GROUP BY is
3312 not correctly calculated. Also, sorting results of a query like
3317 containing an hyphen.
3318 </a></h4>
3319 <p>
3320 The tests I have made with current MySQL 4.1.11 API shows that the
3321 API does not accept this syntax for the USE command. Enclosing the
3322 db name with backquotes works. For further confusion, no backquotes
3323 are needed with command-line mysql.
3324 </p>
3327 <a href="#faq3_14">3.14 I am not able to browse a table when I don't have the right to SELECT one of the columns.</a></h4>
3328 <p>
3329 This has been a known limitation of phpMyAdmin since the beginning and
3330 it's not likely to be solved in the future.
3331 </p>
3333 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3336 <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
3337 need to install it for each customer.
3338 </a></h4>
3339 <p>
3340 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3341 your users. The development of this feature was kindly sponsored by
3342 NetCologne GmbH.
3343 This requires a properly setup MySQL user management and phpMyAdmin
3344 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3346 </p>
3350 access.
3351 </a></h4>
3352 <p>
3353 This depends on your system.<br />
3354 If you're running a server which cannot be accessed by other people, it's
3355 sufficient to use the directory protection bundled with your webserver
3357 If other people have telnet access to your server, you should use
3358 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3359 <br /><br />
3360 Suggestions:
3361 </p>
3362 <ul>
3363 <li>
3365 </li>
3366 <li>
3367 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3368 is a user whose password is only known to you, and apache is the
3369 group under which Apache runs.
3370 </li>
3371 <li>
3372 You should use PHP safe mode, to protect from other users that try
3374 </li>
3375 </ul>
3380 </a></h4>
3381 <p>
3386 </p>
3389 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3390 authentication.
3391 </a></h4>
3395 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3396 and/or
3398 are wrong.</li>
3400 <li>You have already setup a security mechanism for the
3401 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3402 phpMyAdmin's authentication, so remove it.</li>
3403 </ul>
3410 and put the privileges you want. For example,
3412 would let a user create/manage his/her database(s).</p>
3417 <p> If you have existing rules from an old .htaccess file, you can take them
3420 be a major benefit here if your installation is suited to using it. Then
3421 you can just add those updated lines into the
3425 <p> If you want a pre-made sample, you can try this fragment. It stops the
3426 'root' user from logging in from any networks other than the private
3429 <pre>
3430 //block root from logging in except from the private networks
3431 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3432 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3433 'deny root from all',
3434 'allow root from localhost',
3438 );
3439 </pre>
3444 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3445 different than the one set in your
3447 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3448 while a domain name is defined in the config file.</p>
3453 <p>When starting phpMyAdmin, you can use the <tt>db</tt>, <tt>pma_username</tt>, <tt>pma_password</tt> and <tt>server</tt> parameters. This last one can contain either the numeric host index (from <tt>$i</tt> of the configuration file) or one of the host names present in the configuration file. Using <tt>pma_username</tt> and <tt>pma_password</tt> has been tested along with the usage of 'cookie' <tt>auth_type</tt>.</p>
3459 when trying to create a table with more than 14 fields.
3460 </a></h4>
3461 <p>
3462 We could reproduce this problem only under Win98/98SE. Testing under
3463 WinNT4 or Win2K, we could easily create more than 60 fields.
3464 <br />
3465 A workaround is to create a smaller number of fields, then come back to
3466 your table properties and add the other fields.
3467 </p>
3471 <p>
3472 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3473 with each script/website that use forms.<br />
3474 Upgrade or downgrade your Xitami server.
3475 </p>
3478 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3479 <p>
3480 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3481 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3482 don't seem to work.<br />
3484 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3485 the user's temporary directory, so they must be moved before closing
3486 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3489 </p>
3493 Explorer never stores the cookies.
3494 </a></h4>
3495 <p>
3496 MS Internet Explorer seems to be really buggy about cookies, at least till
3498 in this area!
3499 <br />
3500 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3501 work!
3502 </p>
3506 rows.
3507 </a></h4>
3508 <p>
3510 </p>
3513 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3514 when trying to modify a row in a table with many fields, or with a text field
3515 </a></h4>
3516 <p>
3517 Your table neither have a primary key nor an unique one, so we must use a
3518 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
3519 those browsers, and this not happen in Netscape, for example. The
3520 workaround is to create a primary or unique key, or use another browser.
3521 <br />
3522 </p>
3526 page.
3527 </a></h4>
3528 <p>
3529 Some browsers support right-clicking into the frame you want to refresh,
3530 just do this in the right frame.<br />
3531 </p>
3535 query box.
3536 </a></h4>
3537 <p>
3538 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3539 Mozilla versions.<br />
3540 </p>
3544 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3545 </a></h4>
3546 <p>
3547 This is a Mozilla bug (see bug #26882 at
3549 </p>
3554 </a></h4>
3555 <p>
3556 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3557 data in octet-stream mode. Since we can't detect the specific Netscape
3558 version, we cannot workaround this bug.
3559 </p>
3563 wrong.</a></h4>
3565 <p> Please ensure that you have set your browser's character set to the one of the
3566 language file you have selected on phpMyAdmin's start page.
3567 Alternatively, you can try the auto detection mode that is supported by the
3568 recent versions of the most browsers.</p>
3571 <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
3574 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3575 Netscape and Mozilla do not have this problem.</p>
3578 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3579 I cannot manage two servers: I log in to the first one, then the other one,
3580 but if I switch back to the first, I have to log in on each operation.</a></h4>
3586 but nothing happens after that, only a blank screen.</a></h4>
3597 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3602 address and you are starting
3604 containing a domain name, or the reverse situation.</li>
3605 <li>Security settings in IE and/or Microsoft Security Center are
3606 too high, thus blocking scripts execution.</li>
3607 <li>The Windows Firewall is blocking Apache and MySQL. You must
3611 </ul>
3614 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3615 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3616 installed in their Firefox is causing the problem.</p>
3620 clause is generated when I browse a table.</a></h4>
3621 <p> This happens only when both of these conditions are met: using the
3631 </a></h4>
3632 <p>
3633 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3634 specifying a wrong field-type.<br />
3635 Common errors include:
3636 </p>
3637 <ul>
3640 </ul>
3641 <p>
3642 Also, look at the syntax chapter in the MySQL manual to confirm that your
3643 syntax is correct.
3644 </p>
3648 phpMyAdmin generates only one index with those two fields.
3649 </a></h4>
3650 <p>
3651 This is the way to create a multi-fields
3652 index. If you want two indexes, create the first one when creating the
3653 table, save, then display the table properties and click the Index link to
3654 create the other index.
3655 </p>
3659 <p>
3660 Since version 2.2.3, you have a checkbox for each field that can be null.
3662 field's value. Since version 2.5.5, you have to use the checkbox to get
3664 a literal NULL in the field, and not a NULL value (this works in PHP4).
3665 </p>
3670 <p> Click on a database or table name in the left frame, the properties will be
3672 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3673 statements that can be used to recreate your database/table.
3674 <br /><br />
3676 transmit the resulting dump to your station. Depending on your PHP
3677 configuration, you will see options to compress the dump. See also the
3679 configuration variable.<br /><br />
3682 this document.</p>
3687 </a></h4>
3689 <p> Click on a database name in the left frame, the properties will be
3691 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3693 the path to your dump filename, or use the Browse button. Then click Go.
3694 <br /><br />
3696 that you upgrade to take advantage of the new features.
3697 <br /><br />
3699 in this document.
3700 </p>
3705 <p> Here is an example with the tables persons, towns and countries, all
3707 table, create it as explained in the configuration section. Then create the
3708 example tables:</p>
3710 <pre>
3711 CREATE TABLE REL_countries (
3712 country_code char(1) NOT NULL default '',
3713 description varchar(10) NOT NULL default '',
3714 PRIMARY KEY (country_code)
3715 ) TYPE=MyISAM;
3717 INSERT INTO REL_countries VALUES ('C', 'Canada');
3719 CREATE TABLE REL_persons (
3720 id tinyint(4) NOT NULL auto_increment,
3721 person_name varchar(32) NOT NULL default '',
3723 country_code char(1) NOT NULL default '',
3724 PRIMARY KEY (id)
3725 ) TYPE=MyISAM;
3727 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3728 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3730 CREATE TABLE REL_towns (
3732 description varchar(30) NOT NULL default '',
3733 PRIMARY KEY (town_code)
3734 ) TYPE=MyISAM;
3736 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3737 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3738 </pre>
3744 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3748 </ul>
3756 <li>In the fields row, choose persons.person_name and click the
3758 <li>Do the same for towns.description and countries.descriptions in the
3761 the correct joins have been generated</li>
3763 </ul>
3767 <p>
3768 Starting from the previous example, create the pma_table_info as explained
3769 in the configuration section, then browse your persons table,
3770 and move the mouse over a town code or country code.
3771 <br /><br />
3772 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3773 enables: drop-down list of possible values.
3774 </p>
3777 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3778 <p>
3781 <br /><br />
3782 Then you need to think about your schema layout. Which tables will go on
3783 which pages?
3784 </p>
3785 <ul>
3791 page and click Go. If you like, you
3793 linked tables onto the new page.</li>
3794 <li>Select the name of the new page (making sure the Edit radio button
3795 is selected) and click Go.</li>
3797 Coordinates are relative; your diagram will
3798 be automatically scaled to fit the page. When initially placing tables
3799 on the page, just pick any coordinates -- say, 50x50. After clicking
3801 position the element correctly.</li>
3803 first be sure to click the Save
3804 button beneath the list of tables and coordinates, to save any changes
3805 you made there. Then scroll all the way down, select the
3807 you want, and click Go.</li>
3808 <li>Internet Explorer for Windows may suggest an incorrect filename when
3813 browsers on Windows, do not have this problem.</li>
3814 </ul>
3818 columns!</a></h4>
3820 <p> No, it's MySQL that is doing
3826 underscores in the database name?</a></h4>
3828 <p> If you do not put a backslash before the underscore, this is a wildcard
3831 john2db ...<br /><br />
3833 If you put a backslash before the underscore, it means that the database
3834 name will have a real underscore.</p>
3838 statistics pages?</a></h4>
3849 if it already exists during the import. It does NOT drop the table after
3850 your export, it only affects the import file.</li>
3852 Otherwise, you may get an error if the table name exists but has a
3853 different structure.</li>
3855 (if any) will be included in backup.</li>
3857 field and table names formed with special characters are protected.</li>
3859 types set in the pmadb in the dump as
3861 </li>
3862 </ul>
3867 command, for better documentation (but resulting file is bigger).</li>
3869 once the INSERT verb and the table name.</li>
3872 </li>
3874 more info is provided in the
3876 but basically with this selected, invalid values are adjusted and
3877 inserted rather than causing the entire statement to fail.</li>
3878 </ul>
3882 in its name.</a></h4>
3885 is the normal way to reference a database and table name. Worse, MySQL
3886 will usually let you create a database with a dot, but then you cannot
3887 work with it, nor delete it.</p>
3900 for usage.<br />
3901 On a more recent pear version, I had problems with the state of Net_DIME
3902 being beta, so this single command
3904 needed modules.<br />
3905 If you use the Validator, you should be aware that any
3907 submit will be stored anonymously (database/table/column names,
3908 strings, numbers replaced with generic values). The Mimer
3911 We utilize it as free SOAP service.</p>
3915 it, but MySQL says "BLOB column '...' used in key specification without
3918 <p> The right way to do this, is to create the field without any indexes,
3920 dialog. On this page, you will be able to choose your BLOB field, and
3921 set a size to the index, which is the condition to create an index on
3922 a BLOB field.</p>
3926 editing fields?</a></h4>
3928 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
3929 with many editing fields (table structure changes, row editing, etc.)
3930 (must be enabled in configuration - see.
3932 You can also have a look at the directive
3934 ('vertical') and see if this eases up editing for you.</p>
3938 WTF is this feature then useful for?</a></h4>
3940 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
3941 on them. Otherwise you could just put a comment on the field. Because entering
3942 your own mimetype will cause serious syntax checking issues and validation,
3943 this introduces a high-risk false-user-input situation. Instead you have to
3944 initialize mimetypes using functions or empty mimetype definitions.<br />
3945 Plus, you have a whole overview of available mimetypes. Who knows all those
3946 mimetypes by heart so he/she can enter it at will?</p>
3950 can't I see any bookmarks below the query box? What is this variable for?
3951 </a></h4>
3953 <p> Any query you have executed can be stored as a bookmark on the page where the
3954 results are displayed. You will find a button labeled 'Bookmark this query'
3955 just at the end of the page.<br />
3956 As soon as you have stored a bookmark, it is related to the database you run
3957 the query on. You can now access a bookmark dropdown on each page, the query
3958 box appears on for that database.<br /><br />
3960 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
3964 aware of that you HAVE to create a valid query, otherwise your query won't be
3965 even able to be stored in the database.<br />
3967 for your query will remain the way it is, but will be stripped of the /**/
3968 chars. So you can use:<br /><br />
3972 which will be expanded to<br /><br />
3976 in your query, where VARIABLE is the string you entered in the input box. If
3977 an empty string is provided, no replacements are made.<br /><br />
3979 A more complex example. Say you have stored this query:<br /><br />
3981 <br /><br />
3984 the full query will be:<br /><br />
3987 <br /><br />
3991 spaces inserted there
3992 will be later also inserted as spaces in your query and may lead to unexpected
3993 results especially when
3995 Your initial query which is going to be stored as a bookmark has to yield at
3996 least one result row so
3997 you can store the bookmark. You may have that to work around using well
4001 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4002 include exported table?</a></h4>
4004 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4005 document should look like following one (assuming you have table
4008 <pre>
4009 \documentclass{article} % or any class you want
4010 \usepackage{longtable} % for displaying table
4011 \begin{document} % start of document
4012 \include{table} % including exported table
4013 \end{document} % end of document
4014 </pre>
4018 access them.
4019 </a></h4>
4022 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4023 enable users to see all the database names.
4026 So if your users do not need those privileges, you can remove them and their
4027 databases list will shorten.</p>
4031 possible values for a field, based on some foreign table?</a></h4>
4033 <p> You have to setup appropriate links between the tables, and also
4037 foreign table, a drop-down list of values will be available.
4038 You will see two lists of values, the first list containing the key
4039 and the display field, the second list containing the display field
4040 and the key. The reason for this is to be able to type the first
4041 letter of either the key or the display field.<br /><br />
4043 For 100 values or more, a distinct window will appear, to browse foreign
4044 key values and choose one. To change the default limit of 100, see
4045 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4049 automatically when entering Browse mode for a table?</a></h4>
4051 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4052 </p>
4056 Excel files, how can I enable that?</a></h4>
4058 <p> Current version does support direct export to Microsoft Excel and Word
4059 versions 2000 and newer. If you need export older versions, you can use
4061 which works out of the box or you can
4063 several problems, most important are limitation of cell content to 255
4064 chars and no support for charsets, so think carefully whether you want to
4065 enable this.</b>. For enabling this you need to set
4069 module Spreadsheet_Excel_Writer into php include path. The
4070 installation can be done by following command:</p>
4072 <pre>
4073 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
4074 </pre>
4076 <p> First part of switches set we want to install beta version of that module
4077 (no stable version available yet) and then we tell pear we want to satisfy
4078 dependencies.</p>
4080 <p> If you are running in PHP safe mode, you will have to set
4083 modules are located, for example:</p>
4085 <pre>
4086 safe_mode_include_dir = /usr/local/lib/php
4087 </pre>
4091 <pre>
4092 cd phpMyAdmin
4093 mkdir tmp
4094 chmod o+rwx tmp
4095 </pre>
4099 what happens to my column comments stored in pmadb?</a></h4>
4101 <p> Automatic migration of a table's pmadb-style column comments to the native
4102 ones is done whenever you enter Structure page for this table.</p>
4107 <p> First, for general information about BLOB streaming on MySQL, visit <a href="http://blobstreaming.org">blobstreaming.org</a>. We currently support streaming if you are running MySQL 5.1 with the PBXT and PBMS storage engines.</p>
4109 <ol>
4110 <li>In <tt>config.inc.php</tt> your host should be defined with a FQDN (fully qualified domain name) instead of something like "localhost".</li>
4111 <li>A current limitation is that your first login via phpMyAdmin to a freshly-started server must be done with an account that has the SUPER privilege.</li>
4112 <li>On your target database, go to Operations and in the "BLOB Repository" section, click "Enable". This creates the PBMS system tables inside your database.</li>
4113 <li>Ensure that your target table is under the PBXT storage engine and has a LONGBLOB column.</li>
4114 <li>When you insert or update a row in this table, put a checkmark on the "Upload to BLOB repository" optional choice; otherwise, the upload will be done directly in your column instead of the repository.</li>
4115 <li>Finally when you browse your table, you'll see in your column a link to stream your data, for example "View image". A header containing the correct MIME-type will be sent to your browser; this MIME-type was stored at upload time but in case it's incorrect, it's possible to edit it by clicking on the displayed MIME-type.</li>
4116 </ol>
4123 <p> Our Bug Tracker is located at
4125 under the Bugs section.<br /><br />
4127 But please first discuss your bug with other users:<br />
4133 existing language, where do I start?</a></h4>
4135 <p> Always use the current SVN version of your language file.
4137 don't know how to get the SVN version, please ask one of the developers.
4138 <br />
4139 Please note that we try not to use HTML entities like &eacute; in
4140 the translations, since we define the right character set in the file.
4141 With HTML entities, the text on JavaScript messages would not
4142 display correctly.
4143 However there are some entities that need to be there, for quotes
4144 ,non-breakable spaces, ampersands, less than, greater than.<br />
4145 You can then put your translations, as a zip file to avoid losing special
4146 characters, on the sourceforge.net translation tracker.<br />
4147 It would be a good idea to subscribe to the phpmyadmin-translators mailing
4148 list, because this is where we ask for translations of new messages.</p>
4152 phpMyAdmin. How should I proceed?</a></h4>
4157 <tt>svn co https://phpmyadmin.svn.sourceforge.net/svnroot/phpmyadmin/trunk/phpMyAdmin</tt><br />
4158 </li>
4160 <li>generate patch with your changes:
4162 </li>
4165 tracker of the phpMyAdmin project</a>.
4166 </li>
4167 </ol>
4169 <p> Write access to the SVN tree is granted only to experienced developers who
4170 have already contributed something useful to phpMyAdmin.<br />
4176 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4178 <p> Please refer to
4179 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4180 </p>
4185 <p> If you use Apache web server, phpMyAdmin exports information about
4186 authentication to Apache environment and it can be used in Apache logs.
4187 Currently there are two variables available:
4188 </p>
4189 <dl>
4191 <dd>User name of currently active user (he does not have to be logged
4192 in).</dd>
4199 </dl>
4200 <p>
4202 </p>
4203 <pre>
4206 </pre>
4207 <p>
4208 You can then use any log analyzing tools to detect possible break in
4209 attempts.
4210 </p>
4212 <!-- DEVELOPERS -->
4215 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4216 great features have been written by other people and you too can help to
4217 make phpMyAdmin a useful tool.</p>
4219 <p> If you're planning to contribute source, please read the following
4220 information:</p>
4226 it free from other code.<br />
4227 Commonly used functions should be added to
4230 <li>Obviously, you're free to use whatever coding style you want. But
4231 please try to keep your code as simple as possible: beginners are
4232 using phpMyAdmin as an example application.<br />
4233 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4234 compliant on one hand, they fit the
4237 coding standards</a>
4238 on the other hand. Please pay attention to this.</li>
4239 <li>Please try to keep up the file-naming conventions. Table-related stuff
4242 <li>Please don't put message strings in your code, instead add the string
4247 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4248 better debug and profile their code.<br />
4249 Please see the
4251 options for more information.<br />
4252 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4253 lost during its re-entry into Earth's atmosphere and in memory of the
4254 brave men and women who gave their lives for the people of Earth.</li>
4255 </ul>
4259 <pre>
4270 </pre>
4272 <p>
4273 This program is free software; you can redistribute it and/or modify
4274 it under the terms of the GNU General Public License version 2,
4275 as published by the Free Software Foundation.
4276 </p>
4278 <p>
4279 This program is distributed in the hope that it will be useful,
4280 but WITHOUT ANY WARRANTY; without even the implied warranty of
4281 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4282 GNU General Public License for more details.
4283 </p>
4285 <p>
4286 You should have received a copy of the GNU General Public License
4287 along with this program; if not, write to the Free Software
4289 </p>
4291 <!-- CREDITS -->
4296 <ul>
4299 <ul>
4302 </ul></li>
4305 <ul>
4310 </ul></li>
4313 <ul>
4319 </ul></li>
4322 <ul>
4324 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4325 generate XHTML1.0 and CSS2 compliant codes</li>
4328 </ul></li>
4331 <ul>
4339 </ul></li>
4342 <ul>
4347 </ul></li>
4350 <ul>
4353 </ul></li>
4356 <ul>
4358 </ul></li>
4361 <ul>
4364 </ul></li>
4367 <ul>
4371 </ul></li>
4374 <ul>
4377 </ul></li>
4380 <ul>
4387 </ul></li>
4390 <ul>
4394 </ul></li>
4397 <ul>
4403 </ul></li>
4406 (http://sf.net/projects/phpmysqlformgen/)
4407 <ul>
4409 </ul></li>
4412 <ul>
4414 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4419 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4423 </ul></li>
4426 <ul>
4428 </ul></li>
4431 <ul>
4433 </ul></li>
4436 <ul>
4438 </ul></li>
4441 <ul>
4442 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4443 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4444 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4445 </ul></li>
4448 <ul>
4450 </ul></li>
4453 <ul>
4455 </ul></li>
4458 <ul>
4460 </ul></li>
4463 <ul>
4466 </ul></li>
4469 <ul>
4472 </ul></li>
4475 <ul>
4477 </ul></li>
4480 <ul>
4483 </ul></li>
4485 <li>Ivan A Kirillov
4486 <ul>
4488 </ul></li>
4491 <ul>
4493 </ul></li>
4496 <ul>
4498 </ul></li>
4500 </ul>
4502 <p>
4503 And also to the following people who have contributed minor changes,
4504 enhancements, bugfixes or support for a new language since version 2.1.0:
4505 </p>
4507 <p>
4508 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4509 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4510 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4511 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4513 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4514 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4515 Luís V., Martijn W. van der Lee,
4516 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4518 </p>
4523 <p>
4524 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4525 to create a web-based interface to MySQL using PHP3. Although I have not
4526 used any of his source-code, there are some concepts I've borrowed from
4527 him. phpMyAdmin was created because Peter told me he wasn't going to
4528 further develop his (great) tool.
4529 </p>
4530 <p>
4531 Thanks go to
4532 </p>
4533 <ul>
4535 code for the check when dropping a table or database. He also suggested
4536 that you should be able to specify the primary key on tbl_create.php3. To
4537 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4538 well as a bug-report. Plus many smaller improvements.
4539 </li>
4541 were introduced in 1.3.0 (including quite significant ones like the
4542 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4543 bug-fixes and help.
4544 </li>
4546 language-independent by outsourcing the strings to a separate file. He
4547 also contributed the French translation.
4548 </li>
4550 tbl_select.php3, a feature to display only some fields from a table.
4551 </li>
4553 functions in tbl_change.php3. He also added the
4555 </li>
4557 servers and is a regular contributor for bug-fixes.
4558 </li>
4560 features for 2.0.6.
4561 </li>
4562 </ul>
4563 <p>
4564 The following people have contributed minor changes, enhancements, bugfixes
4565 or support for a new language:
4566 </p>
4567 <p>
4568 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4569 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4570 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4571 G. Wieggers.
4572 </p>
4573 <p>
4574 And thanks to everyone else who sent me email with suggestions, bug-reports
4575 and or just some feedback.
4576 </p>
4582 <ul>
4584 - the default name of Apache's directory-level configuration file.</li>
4588 - a software application that enables a user to display and interact with
4589 text, images, and other information typically located on a web page at a
4590 website on the World Wide Web.</li>
4592 - a free software/open source data compression algorithm and program
4593 developed by Julian Seward.</li>
4595 - an important World Wide Web technology that enables a client web browser
4596 to request data from a program executed on the Web server.</li>
4598 - a log or record of changes made to a project.</li>
4600 - a computer system that accesses a (remote) service on another computer
4601 by some kind of network.</li>
4603 - a set of data values of a particular simple type, one for each row of
4604 the table.</li>
4606 - a packet of information sent by a server to a World Wide Web browser
4607 and then sent back by the browser each time it accesses that server.</li>
4609 - Comma-separated values</li>
4612 - an organized collection of data.</li>
4615 - a PHP module that extends PHP with additional functionality.</li>
4617 - a list of commonly asked question and there answers.</li>
4619 - one part of divided data/columns.</li>
4621 - a field or group of fields in a database record that point to a key
4622 field or group of fields forming a key of another database record in some
4623 (usually different) table.</li>
4625 - the free PDF library</li>
4627 GD Graphics Library</a> - a library by Thomas Boutell and others for
4628 dynamically manipulating images.</li>
4631 - gzip is short for GNU zip, a GNU free software file compression
4632 program.</li>
4634 - any machine connected to a computer network, a node that has a hostname.</li>
4636 - the unique name by which a network attached device is known on a network.</li>
4638 (HyperText Transfer Protocol)</a>
4639 - the primary method used to transfer or convey information on the World
4640 Wide Web.</li>
4643 additional security measures.</li>
4644 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4645 - a set of Internet-based services for servers using Microsoft Windows.</li>
4647 - a feature that allows quick access to the rows in a table.</li>
4649 - a data-oriented protocol used by source and destination hosts for
4650 communicating data across a packet-switched internetwork.</li>
4652 - a unique number that devices use in order to identify and communicate
4653 with each other on a network utilizing the Internet Protocol standard.</li>
4655 (Internet Server Application Programming Interface)</a>
4656 - the API of Internet Information Services (IIS).</li>
4658 - a business or organization that offers users access to the Internet and related services.</li>
4660 - a most commonly used standard method of lossy compression for
4661 photographic images.</li>
4667 - line of personal computers is designed, developed, manufactured, and
4668 marketed by Apple Computer.</li>
4669 <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>
4670 - the operating system which is included with all currently shipping Apple
4671 Macintosh computers in the consumer and professional markets.</li>
4673 - a cryptographic library.</li>
4675 - the MCrypt PHP extension.</li>
4676 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4677 - an Internet Standard for the format of e-mail.</li>
4679 - some sort of extension for the Apache Webserver.</li>
4681 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4682 Management System (DBMS).</li>
4684 - the improved MySQL client PHP extension.</li>
4686 - the MySQL client PHP extension.</li>
4688 - open standard for office documents.</li>
4689 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4690 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4692 (Portable Document Format)</a>
4693 - a file format developed by Adobe Systems for representing two
4694 dimensional documents in a device independent and resolution independent
4695 format.</li>
4697 - the PHP Extension and Application Repository.</li>
4699 - the perl-compatible regular expression functions for PHP</li>
4701 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4702 programming language used mainly for developing server-side applications
4703 and dynamic web content, and more recently, a broader range of software
4704 applications.</li>
4706 - a connection through which data is sent and received.</li>
4708 - Request for Comments (RFC) documents are a series of memoranda
4709 encompassing new research, innovations, and methodologies applicable to
4710 Internet technologies.</li>
4714 - represents a single, implicitly structured data item in a table.</li>
4716 - a computer system that provides services to other computing
4717 systems over a network.</li>
4718 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4719 - handlers for different table types</li>
4721 - a form of inter-process communication.</li>
4723 Sockets Layer)</a>
4724 - a cryptographic protocol which provides secure communication on the Internet.</li>
4726 - Structured Query Language</li>
4728 - a set of data elements (cells) that is organized, defined and stored as
4729 horizontal rows and vertical columns where each item can be uniquely
4730 identified by a label or key or by it?s position in relation to other items.</li>
4733 - a type of archive file format: the Tape ARchive format.</li>
4735 - one of the core protocols of the Internet protocol suite.</li>
4739 - a sequence of characters, conforming to a standardized format, that is
4740 used for referring to resources, such as documents and images on the
4741 Internet, by their location.</li>
4743 - A computer (program) that is responsible for accepting HTTP requests
4744 from clients and serving them Web pages.</li>
4746 - a W3C-recommended general-purpose markup language for creating
4747 special-purpose markup languages, capable of describing many different
4748 kinds of data.</li>
4750 - a popular data compression and archival format.</li>
4752 - an open-source, cross-platform data compression library by Jean-loup
4753 Gailly and Mark Adler.</li>
4754 </ul>
4755 </div>
4758 <li>Copyright © 2003 - 2009 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
4761 <li class="last">Valid <a href="http://validator.w3.org/check/referer">HTML</a> and <a href="http://jigsaw.w3.org/css-validator/check/referer">CSS</a></li>
4762 </ul>
4764 </body>
4765 </html>