| blob | d22b518ebe9dd444a48e24933729dae3aa42b223 |
3 <!--
4 vim: expandtab ts=4 sw=4 sts=4 tw=78
5 -->
8 <!-- $Id$ -->
9 <head>
15 </head>
19 <h1>
21 3.3.9-rc1
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 </ul>
58 <!-- REQUIREMENTS -->
65 and the Standard PHP Library (SPL) extension.
66 </li>
69 currently default), you should install mbstring and ctype
70 extensions.
71 </li>
72 <li>You need GD2 support in PHP to display inline
74 original aspect ratio</li>
80 load pages significantly slower.
81 </li>
84 </ul>
85 </li>
88 </ul>
90 <!-- INTRODUCTION -->
93 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
94 a single database. To accomplish the latter you'll need a properly set up
95 MySQL user who can read/write only the desired database. It's up to you to
96 look up the appropriate part in the MySQL manual.
97 </p>
102 <li>create, copy, drop, rename and alter databases, tables, fields and
103 indexes</li>
104 <li>maintenance server, databases and tables, with proposals on server
105 configuration</li>
106 <li>execute, edit and bookmark any
108 batch-queries</li>
111 </li>
118 OpenDocument Text and Spreadsheet,
120 <abbr title="Microsoft Excel 97-2003 and Excel 2007">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
121 </li>
122 <li>import data and MySQL structures from <abbr title="Microsoft Excel 97-2003 and Excel 2007">Microsoft Excel</abbr> and OpenDocument spreadsheets, as well as <abbr title="Extensible Markup Language">XML</abbr>, <abbr title="Comma Separated Values">CSV</abbr>, and <abbr title="Server Query Language">SQL</abbr> files</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>
140 </li>
141 <li>synchronize two databases residing on the same as well as remote servers
143 </li>
145 </ul>
148 <p> Many people have difficulty
149 understanding the concept of user management with regards to phpMyAdmin. When
150 a user logs in to phpMyAdmin, that username and password are passed directly
151 to MySQL. phpMyAdmin does no account management on its own (other than
152 allowing one to manipulate the MySQL user account information); all users
153 must be valid MySQL users.</p>
162 <!-- INSTALLATION -->
170 </ol>
173 phpMyAdmin does not apply any special security methods to the MySQL database
174 server. It is still the system administrator's job to grant permissions on
176 be used for this.
177 </p>
185 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
186 before uploading them to your server, as PHP seems not to like
191 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
192 Downloads page. Some kits contain only the English messages,
193 others contain all languages in UTF-8 format (this should be fine
194 in most situations), others contain all
195 languages and all character sets. We'll assume you chose a kit whose
197 </li>
198 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
200 document root. If you don't have direct access to your document root,
201 put the files in a directory on your local machine, and, after step 4,
202 transfer the directory on your web server using, for example, ftp.</li>
203 <li>Ensure that all the scripts have the appropriate owner (if PHP is
204 running in safe mode, having some scripts with an owner different
205 from the owner of other scripts will be a
210 <li>Now you must configure your installation. There are two methods that
211 can be used. Traditionally, users have hand-edited a copy of
213 provided for those who prefer a graphical installation. Creating a
214 <tt>config.inc.php</tt> is still a quick way to get started and needed for some advanced features.
215 <ul><li>To manually create the file, simply use your text editor to
218 file) in the main (top-level) phpMyAdmin directory (the one
222 default value is okay for a particular setting, there is no
224 few directives to get going, a simple configuration may look
225 like this:
226 <pre>
227 <?php
228 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
230 $i=0;
231 $i++;
232 $cfg['Servers'][$i]['auth_type'] = 'cookie';
233 ?>
234 </pre>
235 Or, if you prefer to not be prompted every time you log in:
236 <pre>
237 <?php
239 $i=0;
240 $i++;
241 $cfg['Servers'][$i]['user'] = 'root';
242 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
243 $cfg['Servers'][$i]['auth_type'] = 'config';
244 ?>
245 </pre>
246 For a full explanation of possible configuration values, see the
252 directory. This is a security measure. On a Linux/Unix system you
253 can use the following commands:
254 <pre>
255 cd phpMyAdmin
256 mkdir config # create directory for saving
257 chmod o+rw config # give it world writable permissions
258 </pre>
259 And to edit an existing configuration, copy it over first:
260 <pre>
261 cp config.inc.php config/ # copy current configuration for editing
262 chmod o+w config/config.inc.php # give it world writable permissions
263 </pre>
264 On other platforms, simply create the folder and ensure that your
273 the webserver does not have the proper permissions you may see the
275 config/</tt> directory exists and has the proper permissions -
277 and upload (via FTP or some similar means) to the proper location.<br /><br />
279 Once the file has been saved, it must be moved out of the <tt>
280 config/</tt> directory and the permissions must be reset, again
281 as a security measure:
282 <pre>
283 mv config/config.inc.php . # move file to current directory
284 chmod o-rw config.inc.php # remove world read and write permissions
285 rm -rf config # remove not needed directory
286 </pre>
287 Now the file is ready to be used. You can choose to review or edit
288 the file with your favorite editor, if you prefer to set some
289 advanced options which the setup script does not provide.</li></ul></li>
290 <li>If you are using the
292 protect the phpMyAdmin installation directory because using
293 config does not require a user to
294 enter a password to access the phpMyAdmin installation. Use of an alternate
295 authentication method is recommended, for example with
303 in your browser. phpMyAdmin should now display a welcome screen
304 and your databases, or a login dialog if using
306 authentication mode.</li>
309 Apache you can use supplied .htaccess file in that folder, for other
310 webservers, you should configure this yourself. Such configuration
311 prevents from possible path exposure and cross side scripting
312 vulnerabilities that might happen to be found in that code.</li>
313 <li>
314 It is generally good idea to protect public phpMyAdmin installation
315 against access by robots as they usually can not do anything good
317 your webserver or limit access by web server configuration. You can
320 </li>
321 </ol>
325 <p> For a whole set of new features (bookmarks, comments,
327 tracking mechanism,
329 transformation, etc.) you need to create a set of special tables. Those
330 tables can be located in your own database, or in a central database for a
331 multi-user installation (this database would then be accessed by the
332 controluser, so no other user should have rights to it).</p>
342 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
343 that you may need special (administrator) privileges to create the database
344 and tables, and that the script may need some tuning, depending on the
345 database name.</p>
350 section</a>. You will also need to have a controluser with the proper rights
357 unpacked one. Configuration files from old versions may
358 require some tweaking as some options have been changed or removed; in
360 so you better remove it from your file and just use the default one.
362 statement that you might find near the end of your configuration file.</p>
366 is version-specific.</p>
369 version 5.x or newer and if you use the pmadb/linked table infrastructure,
370 you should run the SQL script found in
377 where you want to give users access to their own database and don't want
378 them to play around with others.<br />
379 Nevertheless be aware that MS Internet Explorer seems to be really buggy
383 that your user/password pair are not in clear in the configuration file.
384 </li>
387 authentication modes are more secure: the MySQL login information does
388 not need to be set in the phpMyAdmin configuration file (except possibly
390 However, keep in mind that the password travels in plain text, unless
391 you are using the HTTPS protocol.<br />
392 In cookie mode, the password is stored, encrypted with the blowfish
393 algorithm, in a temporary cookie.</li>
395 <li>Note: this section is only applicable if
405 file under the
407 $cfg['Servers'][$i]['controluser']</a></tt> and
412 only an example: use something else in your file!</b> Input these
413 statements from the phpMyAdmin SQL Query window or mysql command–line
414 client.<br />
416 if it's not the same as the MySQL server's one.
418 <pre>
419 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
420 GRANT SELECT (
421 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
422 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
423 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
424 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
425 Execute_priv, Repl_slave_priv, Repl_client_priv
426 ) ON mysql.user TO 'pma'@'localhost';
427 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
428 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
429 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
430 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
432 If you want to use the many new relation and bookmark features:
434 <pre>
436 </pre>
442 on a set of particular databases. Normally you shouldn't give global
443 privileges to an ordinary user, unless you understand the impact of those
444 privileges (for example, you are creating a superuser).<br />
448 <pre>
449 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
450 </pre>
452 What the user may now do is controlled entirely by the MySQL user
453 management system.<br />
455 authentication mode, you don't need to fill the user/password fields
457 array.</li>
458 </ul>
463 method and allows you to log in as any valid MySQL user.</li>
464 <li>Is supported with most PHP configurations. For
477 mode.</li>
478 </ul>
482 <ul><li>You can use this method as a replacement for the
484 (for example, if you're running
486 <li>Obviously, the user must enable cookies in the browser, but this is
487 now a requirement for all authentication modes.</li>
488 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
489 with the same username.</li>
490 <li>If you want to log in to arbitrary server see
495 not required.</li>
496 </ul>
500 <ul><li>This mode is a convenient way of using credentials from another
501 application to authenticate to phpMyAdmin.</li>
502 <li>The other application has to store login information into
503 session data.</li>
505 section.</li>
506 </ul>
509 <ul><li>This mode is the less secure one because it requires you to fill the
511 $cfg['Servers'][$i]['user']</a> and
513 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
514 can read your config.inc.php can discover your username and password).
515 <br />
522 is an entry explaining how to protect your configuration file.</li>
523 <li>For additional security in this mode, you may wish to consider the Host
524 authentication
526 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
528 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
529 directives.</li>
530 <li>Unlike cookie and http, does not require a user to log in when first
531 loading the phpMyAdmin site. This is by design but could allow any
532 user to access your installation. Use of some restriction method is
534 HTTP-AUTH directive or disallowing incoming HTTP requests at
535 one’s router or firewall will suffice (both of which
536 are beyond the scope of this manual but easily searchable with Google).</li>
537 </ul>
539 <p>
540 The Swekey is a low cost authentication USB key that can be used in
541 web applications.<br /><br />
542 When Swekey authentication is activated, phpMyAdmin requires the
543 users's Swekey to be plugged before entering the login page (currently
544 supported for cookie authentication mode only). Swekey Authentication is
545 disabled by default.<br /><br />
547 </p>
548 <pre>
549 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
550 </pre>
551 <p>
553 each user with their Swekey Id. It is important to place this file outside
554 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
556 users' information.<br /><br />
557 If you want to purchase a Swekey please visit
559 since this link provides funding for phpMyAdmin.
560 </p>
561 <!-- CONFIGURATION -->
565 users:</span> PHP does not seem to like
569 before saving a script you have modified.</p>
574 section to create one. This file only needs to contain the parameters you want to
575 change from their corresponding default value in
578 <p> The parameters which relate to design (like colors) are placed in
581 your site specific code to be included on start and end of each page.</p>
585 (with full path) to your phpMyAdmin installation's directory.
588 some web servers are case–sensitive.
591 Starting with version 2.3.0, it is advisable to try leaving this
592 blank. In most cases phpMyAdmin automatically detects the proper
593 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
594 href="https://sourceforge.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
595 A good test is to browse a table, edit a row and save it. There should
596 be an error message if phpMyAdmin is having trouble auto–detecting
597 the correct value. If you get an error that this must be set or if
598 the autodetect code fails to detect your path, please post a bug
599 report on our bug tracker so we can improve the code.</dd>
603 with master / foreign – tables (see
605 <br />
606 If you tried to set this up and it does not work for you, have a look on
608 use it. You will find a link that will analyze why those features have
609 been disabled.<br />
610 If you do not want to use those features set this variable to
614 <dd>A warning is displayed on the main page if Suhosin is detected.
616 from appearing.</dd>
619 <dd>Disable the default warning that is displayed if mcrypt is missing for
620 cookie authentication.
622 from appearing.</dd>
626 domain to call phpMyAdmin inside a frame, and is a potential security
627 hole allowing cross-frame scripting attacks.</dd>
631 algorithm to encrypt the password.<br />
633 passphrase of your choice. It will be used internally by the blowfish
634 algorithm: you won’t be prompted for this passphrase. There is
635 no maximum length for this secret.<br /><br />
637 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
638 makes a bit weaker security as this generated secret is stored in
639 session and furthermore it makes impossible to recall user name from
640 cookie.</dd>
644 MySQL servers. Therefore, a
646 been added which contains the login information for the different servers.
647 The first
649 contains the hostname of the first server, the second
651 the hostname of the second server, etc. In
653 server definition, however you can put as many as you need in
655 have to define all settings, just those you need to change).</dd>
659 $i-th MySQL-server. E.g. localhost.</dd>
664 ignores this port number and connects with the socket, so if you want
665 to connect to a port different from the default port, use
668 </dd>
672 To determine the correct socket, check your MySQL configuration or, using the
674 Among the resulting information displayed will be the socket used.</dd>
677 <dd>Whether to enable SSL for connection to MySQL server.
678 </dd>
681 <dd>What type connection to use with the MySQL server. Your options are
683 is nearly guaranteed to be available on all MySQL servers, while
684 sockets are not supported on some platforms.<br /><br />
686 To use the socket mode, your MySQL server must be on the same machine
687 as the Web server.</dd>
690 <dd>What php MySQL extension to use for the connection. Valid options are:
691 <br /><br />
694 The classic MySQL extension. This is the recommended and default
695 method at this time.<br /><br />
698 The improved MySQL extension. This extension became available
699 with php 5.0.0 and is the recommended way to connect to a server
703 <dd>Whether to use a compressed protocol for the MySQL server connection
704 or not (experimental).<br />
710 </dt>
712 all relational features (see
714 and, for a MySQL server running with
717 authentication mode).<br /><br />
720 cookie authentication modes (or 'config'
721 authentication mode since phpMyAdmin 2.2.1), you need to supply the
726 This account is used to check what databases the user will see at
727 login.<br />
731 In phpMyAdmin versions before 2.2.5, those were called
735 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
736 <dd>Whether config or cookie or
738 should be used for this server.
740 is the plain old way: username and password are stored in
742 <li>'cookie' authentication mode
744 2.2.3 allows you to log in as any valid MySQL user with the
745 help of cookies. Username and password are stored in
746 cookies during the session and password is deleted when it
747 ends. This can also allow you to log in in arbitrary server if
748 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
749 </li>
750 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
751 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
752 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
753 <li>'signon' authentication mode
755 as introduced in 2.10.0 allows you to log in from prepared PHP
756 session data. This is useful for implementing single signon
757 from another application. Sample way how to seed session is in
763 </ul>
766 for more information.
767 </dd>
769 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
770 </dt>
771 <dd>
773 names for hardware authentication. Leave empty to deactivate this feature.
774 </dd>
778 </dt>
779 <dd>
780 When using auth_type = 'config', this is the user/password-pair
781 which phpMyAdmin will use to connect to the
782 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
783 cookie authentication is used and should be empty.</dd>
785 <span
787 </dt>
788 <dd>
789 Allow attempt to log in without password when a login with password
790 fails. This can be used together with http authentication, when
791 authentication is done some other way and phpMyAdmin gets user name
792 from auth and uses empty password for connecting to MySQL. Password
793 login is still tried first, but as fallback, no password method is
794 tried.</dd>
797 </dt>
798 <dd>
799 If set to a (an array of) database name(s), only this (these) database(s)
800 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
801 database(s) name(s) may contain MySQL wildcards characters
805 This setting is an efficient way to lower the server load since the
806 latter does not need to send MySQL requests to build the available
808 privileges rules of the MySQL database server</span>. If set, it just
809 means only these databases will be displayed but
811 <br /><br />
813 An example of using more that one database:
815 <br /><br />
817 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
818 databases in the left frame, so that you can individually arrange your databases.<br />
819 If you want to have certain databases at the top, but don't care about the others, you do not
820 need to specify all other databases. Use:
822 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
823 order.</dd>
826 </dt>
827 <dd>Regular expression for hiding some databases. This only hides them
828 from listing, but a user is still able to access them (using, for example,
829 the SQL query area). To limit access, use the MySQL privilege system.
830 <br /><br />
835 More information on regular expressions can be found in the
837 PCRE pattern syntax</a> portion of the PHP reference manual.
838 </dd>
841 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
842 this string will be displayed instead of the hostname in the pull-down
843 menu on the main page. This can be useful if you want to show only
844 certain databases on your system, for example. For HTTP auth, all
845 non-US-ASCII characters will be stripped.</dd>
849 </dt>
850 <dd>The name of the database containing the linked-tables infrastructure.
851 <br /><br />
854 section in this document to see the benefits of this infrastructure,
855 and for a quick way of creating this database and the needed tables.
856 <br /><br />
858 If you are the only user of this phpMyAdmin installation, you can
859 use your current database to store those special tables; in this
860 case, just put your current database name in
862 set this parameter to the name of your central database containing
863 the linked-tables infrastructure.</dd>
867 </dt>
869 useful for queries you often run.<br /><br />
871 To allow the usage of this functionality:
873 <li>enter the table name in
875 </ul>
876 </dd>
880 </dt>
882 which field is a key in another table (a foreign key). phpMyAdmin
883 currently uses this to
884 <ul><li>make clickable, when you browse the master table, the data values
885 that point to the foreign table;</li>
887 when browsing the master table, if you move the mouse to a column
888 containing a foreign key (use also the 'table_info' table);<br />
891 <li>in edit/insert mode, display a drop-down list of possible foreign
895 <li>display links on the table properties page, to check referential
896 integrity (display missing foreign keys) for each described key;
897 </li>
901 schema of your database (also uses the table_coords table).</li>
902 </ul>
904 The keys can be numeric or character.<br /><br />
906 To allow the usage of this functionality:
909 infrastructure</li>
910 <li>put the relation table name in
912 <li>now as normal user open phpMyAdmin and for each one of your
913 tables where you want to use this feature, click
915 </li>
916 </ul>
920 future development of the cross-db relations.
921 </dd>
925 </dt>
926 <dd>
927 Since release 2.3.0 you can describe, in a special 'table_info'
928 table, which field is to be displayed as a tool-tip when moving the
929 cursor over the corresponding key.<br />
930 This configuration variable will hold the name of this special
931 table. To allow the usage of this functionality:
933 <li>put the table name in
935 'pma_table_info')</li>
936 <li>then for each table where you want to use this feature,
938 to choose the field.</li>
939 </ul>
941 </dd>
945 </dt>
948 the relations between your tables. To do this it needs two tables
953 schema output).<br /><br />
957 To allow the usage of this functionality:
960 infrastructure</li>
961 <li>put the correct table names in
964 </ul>
967 </dd>
971 </dt>
973 Since release 2.3.0 you can store comments to describe each column for
975 <br /><br />
977 Starting with release 2.5.0, comments are consequently used on the table
978 property pages and table browse view, showing up as tool-tips above the
979 column name (properties page) or embedded within the header of table in
980 browse view. They can also be shown in a table dump. Please see the
981 relevant configuration directives later on.<br /><br />
983 Also new in release 2.5.0 is a MIME-transformation system which is also
985 Transformations</a> for further information. To use the
986 MIME-transformation system, your column_info table has to have the three
987 new fields 'mimetype', 'transformation', 'transformation_options'.
988 <br /><br />
990 To allow the usage of this functionality:
992 infrastructure</li>
993 <li>put the table name in
995 'pma_column_info')</li>
998 <pre>
999 ALTER TABLE `pma_column_comments`
1000 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1001 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1002 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1003 </pre>
1006 renamed from<br />
1009 </ul>
1010 </dd>
1014 </dt>
1017 all queries you entered manually into the phpMyAdmin interface. If you
1018 don't want to use a table-based history, you can use the JavaScript-based
1019 history. Using that, all your history items are deleted when closing the
1020 window.<br /><br />
1022 Using
1024 you can specify an amount of history items you want to have on hold. On
1025 every login, this list gets cut to the maximum amount.<br /><br />
1027 The query history is only available if JavaScript is enabled in your
1028 browser.<br /><br />
1030 To allow the usage of this functionality:
1033 infrastructure</li>
1035 (e.g. 'pma_history')
1036 </li>
1037 </ul>
1038 </dd>
1042 </dt>
1043 <dd>
1044 Since release 3.3.x a tracking mechanism is available.
1046 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1047 and data definition statements. After enabling it you can create versions of tables.
1048 <br/><br/>
1049 The creation of a version has two effects:
1051 <ul>
1053 <li>phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1054 </ul>
1056 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1057 For the report you can use filters, for example you can get a list of statements within a date range.
1058 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1059 In addition you can export the (filtered) report to a file or to a temporary database.
1060 <br/><br/>
1062 To allow the usage of this functionality:
1064 <ul>
1067 </ul>
1068 </dd>
1071 <span id="cfg_Servers_tracking_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1072 </dt>
1073 <dd>
1074 Whether the tracking mechanism creates versions for tables and views automatically. Default value is false.
1075 <br/><br/>
1076 If this is set to true and you create a table or view with
1078 <ul>
1081 </ul>
1083 and no version exists for it, the mechanism will
1084 create a version for you automatically.
1085 </dd>
1088 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1089 </dt>
1090 <dd>
1091 Defines the list of statements the auto-creation uses for new versions. Default value is
1092 <br/>
1094 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1095 CREATE INDEX,DROP INDEX,
1096 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1097 CREATE VIEW,ALTER VIEW,DROP VIEW,
1098 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1099 </dd>
1102 <span id="cfg_Servers_tracking_drop_view">$cfg['Servers'][$i]['tracking_version_drop_view']</span> boolean
1103 </dt>
1104 <dd>
1105 Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view. Default value is true.
1106 <br/><br/>
1107 </dd>
1111 <span id="cfg_Servers_tracking_drop_table">$cfg['Servers'][$i]['tracking_version_drop_table']</span> boolean
1112 </dt>
1113 <dd>
1114 Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table. Default value is true.
1115 <br/><br/>
1116 </dd>
1119 <span id="cfg_Servers_tracking_drop_database">$cfg['Servers'][$i]['tracking_version_drop_database']</span> boolean
1120 </dt>
1121 <dd>
1122 Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database. Default value is true.
1123 <br/><br/>
1124 </dd>
1129 </dt>
1131 to visually manage the relations.
1132 <br /><br />
1134 To allow the usage of this functionality:
1137 infrastructure</li>
1138 <li>put the table name in <tt>$cfg['Servers'][$i]['designer_coords']</tt> (e.g. 'pma_designer_coords')
1139 </li>
1140 </ul>
1141 </dd>
1144 </dt>
1146 column_info table got enhanced with three new fields. If the above variable
1148 latest table structure available. If not, it will emit a warning to the
1149 superuser.<br /><br />
1151 You can disable this checking behavior by setting the variable to false,
1152 which should offer a performance increase.<br /><br />
1154 Recommended to set to FALSE, when you are sure, your table structure is
1155 up to date.</dd>
1157 boolean</dt>
1158 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1159 </dd>
1161 boolean</dt>
1162 <dd>Whether to allow logins without a password. The default
1164 to a MySQL server with was left with an empty password for root or
1165 on which an anonymous (blank) user is defined.
1166 </dd>
1169 </dt>
1171 authentication is disabled.<br /><br />
1174 all deny rules followed by allow rules. Access is allowed by default. Any
1175 client which does not match a Deny command or does match an Allow command
1176 will be allowed access to the server. <br /><br />
1179 applies all allow rules followed by deny rules. Access is denied by
1180 default. Any client which does not match an Allow directive or does
1181 match a Deny directive will be denied access to the server.<br /><br />
1183 If your rule order is set to 'explicit', the authentication is
1184 performed in a similar fashion to rule order 'deny,allow', with the
1188 and was available in Apache by specifying allow and deny rules without
1189 setting any order.<br /><br />
1191 Please also see <a
1193 address behind proxies.
1194 </dd>
1196 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1197 </dt>
1198 <dd>The general format for the rules is as such:
1200 <pre>
1202 </pre>
1207 well (please note that those containing SERVER_ADDRESS might not be
1208 available on all webservers):
1209 <pre>
1215 </pre>
1217 Having an empty rule list is equivalent to either using
1223 following work:<br />
1225 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1226 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1227 But the following does not work:<br />
1230 Also IPv6 addresses are not supported.
1231 </dd>
1233 <dd>Disable using <tt>INFORMATION_SCHEMA</tt> to retrieve information (use <tt>SHOW</tt> commands instead), because of speed issues when many databases are present. Currently used in some parts of the code, more to come.
1234 </dd>
1235 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1237 DATABASES</tt> command used to fetch the name of available databases will
1238 probably be too slow, so it can be replaced by faster commands (see
1240 </dd>
1242 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1243 </dd>
1244 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1245 <dd>Name of session which will be used for signon authentication method.
1246 </dd>
1248 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1249 </dd>
1251 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1252 </dd>
1255 <dd>If you have more than one server configured, you can set
1257 that server when phpMyAdmin is started, or set it to 0 to be given a
1258 list of servers without logging in.<br />
1260 MUST be set to that server.</dd>
1263 <dd>The maximum number of database names to be displayed in the
1264 navigation frame and the database list.</dd>
1267 <dd>The maximum number of table names to be displayed in the
1268 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1269 when in Light mode.</dd>
1272 <dd>The maximum number of characters when a SQL query is displayed. The
1273 default limit of 1000 should be correct to avoid the display of tons
1274 of hexadecimal codes that represent BLOBs, but some users have real
1275 SQL queries that are longer than 1000 characters. Also, if a query's
1276 length exceeds this limit, this query is not saved in the history.</dd>
1279 <dd>Defines whether to use GZip output buffering for increased
1281 Set to true/false for enabling/disabling. When set to 'auto' (string),
1282 phpMyAdmin tries to enable output buffering and will automatically disable
1283 it if your browser has some problems with buffering. IE6 with a certain patch
1284 is known to cause data corruption when having enabled buffering.</dd>
1287 <dd>Whether persistent connections should be used or not (mysql_connect or
1288 mysql_pconnect).</dd>
1294 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1295 to zero, no time limit is imposed.<br />
1296 This setting is used while importing/exporting dump files and in the
1297 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1300 <dd>Set the number of bytes a script is allowed to allocate. If set
1301 to zero, no limit is imposed.<br />
1302 This setting is used while importing/exporting dump files and at some
1303 other places in phpMyAdmin so you definitely don't want to put here
1304 a too low value. It has no effect when PHP is running in safe mode.<br />
1305 You can also use any string as in php.ini, eg. '16M'. Ensure
1309 <dd>Mark used tables and make it possible to show databases with locked
1314 generated by phpMyAdmin should be displayed or not.</dd>
1317 <dd>Defines whether normal users (non-administrator) are allowed to
1318 delete their own database or not. If set as FALSE, the link "Drop
1320 mydatabase" will be rejected. Quite practical for
1322 customers.<br />
1323 Please note that this limitation of SQL queries is not as strict as
1324 when using MySQL privileges. This is due to nature of SQL queries
1325 which might be quite complicated. So this choice should be viewed as
1326 help to avoid accidental dropping rather than strict privilege
1327 limitation.</dd>
1331 displayed when you're about to lose data.</dd>
1334 <dd>Define whether the previous login should be recalled or not in cookie
1335 authentication mode.<br /><br />
1337 This is automatically disabled if you do not have configured
1339 </dd>
1342 <dd>Define how long is login cookie valid. Please note that php
1343 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1344 might limit session validity and if session is lost, login cookie is
1346 not lower than the value of $cfg['LoginCookieValidity'].</dd>
1350 means that it will be kept for existing session. This is recommended
1351 for not trusted environments.</dd>
1354 <dd>If enabled (default), logout deletes cookies for all servers,
1355 otherwise only for current one. Setting this to false makes it easy to
1356 forget to log out from other server, when you are using more of
1357 them.</dd>
1363 <dd>Define whether phpMyAdmin will continue executing a multi-query
1364 statement if one of the queries fails. Default is to abort execution.</dd>
1367 <dd>Define whether phpMyAdmin will output the results of each query of a
1368 multi-query statement embedded into the
1373 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1374 <br /><br />
1377 MySQL servers behind the firewall where your
1379 </dd>
1388 <dd>Defines whether to use a select-based menu and display only the current
1389 tables in the left frame (smaller page). Only in Non-Lightmode you can
1390 use the feature to display nested folders using
1392 </dd>
1395 <dd>In light mode, defines whether to display the names of databases (in the
1396 selector) using a tree, see also
1398 </dd>
1401 string or array</dt>
1402 <dd>The string used to separate the parts of the database name when showing
1403 them in a tree. Alternatively you can specify more strings in an array
1404 and all of them will be used as a separator.</dd>
1407 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1408 This means if you have tables like 'first__second__third' this will be
1410 If set to FALSE or empty, the feature is disabled. NOTE: You should
1411 not use this separator at the beginning or end of a
1412 table name or multiple times after another without any other
1413 characters in between.</dd>
1416 <dd>Defines how many sublevels should be displayed when splitting
1417 up tables by the above separator.</dd>
1420 <dd>Defines whether to display table comment as tool-tip in left frame or
1421 not.</dd>
1424 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1425 comment and the real name. That means that if you have a table called
1426 'user0001' and add the comment 'MyName' on it, you will see the name
1427 'MyName' used consequently in the left frame and the tool-tip shows
1428 the real name of the DB.</dd>
1431 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1433 When setting this to 'nested', the Alias of the Tablename is only used
1434 to split/nest the tables according to the
1436 directive. So only the folder is called like the Alias, the tablename itself
1437 stays the real tablename.</dd>
1440 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1443 <dd>Enter URL where logo in the navigation frame will point to.
1444 For use especially with self made theme which changes this.
1453 <dd>Defines whether or not to display a server choice at the top of the left frame.
1454 Defaults to FALSE.</dd>
1456 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1457 Defaults to FALSE (drop-down).</dd>
1459 <dd>Defines whether to display database choice in light navigation frame as links
1460 instead of in a drop-down. Defaults to 'auto' - on main page list is
1461 shown, when database is selected, only drop down is displayed.</dd>
1464 <dd>Defines the tab displayed by default when clicking the small
1465 icon next to each table name in the navigation panel. Possible
1471 <dd>Defines whether or not to display space usage and statistics about databases
1472 and tables.<br />
1473 Note that statistics requires at least MySQL 3.23.3 and that, at this
1474 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1477 <dd>Defines whether to display detailed server information on main page.
1478 You can additionally hide more information by using
1480 </dd>
1485 </dt>
1488 not at the starting main (right) frame. This setting
1489 does not check MySQL commands entered directly.<br /><br />
1491 Please note that to block the usage of phpinfo() in scripts, you
1498 hard coded password value in the configuration file, end users can't
1499 be allowed to change their passwords.</dd>
1502 <dd>Defines whether to suggest a database name on the
1506 <dd>Defines whether navigation bar buttons and the right panel top menu
1507 contain text or symbols only. A value of TRUE displays icons, FALSE
1508 displays text and 'both' displays both icons and text.</dd>
1511 <dd>Defines whether a user should be displayed a
1515 <dd>Number of rows displayed when browsing a result set. If the result set
1522 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1526 option is ticked by default.</dd>
1530 from editing when browsing a table's content. Valid values are:
1535 </ul>
1536 </dd>
1539 <dd>Defines whether or not MySQL functions fields should be initially
1540 displayed in edit/insert mode. Since version 2.10, the user can
1541 toggle this setting from the interface.
1542 </dd>
1545 <dd>Defines which type of editing controls should be used for CHAR and
1546 VARCHAR fields. Possible values are:
1547 <ul><li>input - this allows to limit size of text to size of field in
1548 MySQL, but has problems with newlines in fields</li>
1549 <li>textarea - no problems with newlines in fields, but also no
1550 length limitations</li>
1551 </ul>
1552 Default is old behavior so input.</dd>
1558 <dd>If there are fewer items than this in the set of foreign keys, then a
1559 drop-down box of foreign keys is presented, in the style described by the
1561 setting.</dd>
1564 <dd>For the foreign key drop-down fields, there are several methods of
1565 display, offering both the key and value data. The contents of the
1566 array should be one or both of the following strings:
1572 </dt>
1573 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1574 creating a dump file</dd>
1577 </dt>
1578 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1579 compressed exports. This doesn't affect smaller dumps and allows users to
1580 create larger dumps that won't otherwise fit in memory due to php
1581 memory limit. Produced files contain more GZip/BZip2 headers, but all
1582 normal programs handle this correctly.</dd>
1586 mainframe.</dd>
1590 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1595 <dd>How many columns will be utilized to display the tables on the
1596 database property view? Default is 1 column. When setting this to a
1597 value larger than 1, the type of the database will be omitted for more
1598 display space.</dd>
1602 <dd>Defines the tab displayed by default on server view. Possible
1609 <dd>Defines the tab displayed by default on database view. Possible
1614 <dd>Defines the tab displayed by default on table view. Possible
1621 points to the MySQL documentation (type depends
1622 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1623 generated.<br />
1625 for more information about MySQL manuals and their types.</dd>
1628 <dd>Type of MySQL documentation:
1634 </ul>
1635 </dd>
1638 <dd>Defines the default language to use, if not browser-defined or
1639 user-defined.<br />
1641 this setting.</dd>
1644 <dd>Defines the default connection collation to use, if not
1645 user-defined.<br />
1650 <dd>Force: always use this language (must be defined in the
1654 <dd>Limit list of available languages to those matching the given regular
1655 expression. For example if you want only Czech and English, you should
1659 <dd>Default character set to use for recoding of MySQL queries. This must be
1660 enabled and it's described by
1662 option.<br />
1663 You can give here any character set which is in
1665 array and this is just default choice, user can select any of them.</dd>
1668 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1669 support (compiled in or module) in PHP to allow MySQL queries recoding
1670 and used language file must have it enabled (by default only these
1671 which are in Unicode, just to avoid losing some characters).<br /><br />
1674 in the Export and Import pages, to choose the character set when
1675 exporting a file. The default value in this menu comes from
1677 </dd>
1680 <dd>You can select here which functions will be used for character set
1681 conversion. Possible values are:
1682 <ul><li>auto - automatically use available one (first is tested
1683 iconv, then recode)</li>
1686 </ul>
1687 Default is auto.</dd>
1690 <dd>Specify some parameters for iconv used in charset conversion. See
1693 used, so that invalid characters will be transliterated.</dd>
1696 <dd>Available character sets for MySQL conversion. You can add your own (any of
1697 supported by recode/iconv) or remove these which you don't use.
1698 Character sets will be shown in same order as here listed, so if you
1699 frequently use some of these move them to the top.</dd>
1704 default empty, you need to fill in some trusted proxy servers if you
1705 want to use rules for IP addresses behind proxy.<br /><br />
1707 The following example specifies that phpMyAdmin should trust a
1709 <pre>
1710 $cfg['TrustedProxies'] =
1712 </pre>
1713 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1714 client's IP address as usual.
1715 </dd>
1719 MIME transformations.<br />
1720 Possible values are:
1721 <ul><li>auto - automatically detect, this is a bit expensive
1723 according to your server real possibilities</li>
1726 </ul>
1727 Default is auto.
1728 </dd>
1731 <dd>
1732 We normally check the permissions on the configuration file to ensure
1733 it's not world writable. However, phpMyAdmin could be installed on
1734 a NTFS filesystem mounted on a non-Windows server, in which case the
1735 permissions seems wrong but in fact cannot be detected. In this case
1737 </dd>
1740 <dd>
1741 Limit for length of URL in links. When length would be above this limit, it
1742 is replaced by form with button.
1743 This is required as some web servers (IIS) have problems with long URLs.
1745 </dd>
1749 </dd>
1751 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1752 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1753 </dt>
1754 <dd>The background styles used for both the frames.
1757 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1759 <dd>The style used for the pointer in the navi frame.
1763 </dt>
1764 <dd>The color used for the database name in the navi frame.
1773 </dd>
1777 <dd>The style used for table headers. See
1782 </dd>
1786 </dd>
1788 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1790 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1792 </dt>
1794 The former feature highlights the row over which your mouse is passing
1795 and the latter lets you visually mark/unmark rows by clicking on
1796 them.<br />
1801 <dd>You put here a valid CSS font family value, for example
1806 <dd>You put here a valid CSS font family value, for example
1820 </dt>
1822 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1824 The Char* values are used for CHAR and VARCHAR editing (if configured
1828 </dt>
1832 </dt>
1833 <dd>Defines if the whole textarea of the query box will be selected on
1834 click.</dd>
1837 </dt>
1838 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1839 editing.</dd>
1842 <dd>Maximum number of characters shown in any non-numeric field on browse view.
1843 Can be turned off by a toggle button on the browse page.</dd>
1847 </dt>
1848 <dd>Defines the place where modify and delete links would be put when
1849 tables contents are displayed (you may have them displayed both at the
1850 left and at the right).
1856 </dt>
1858 Define which one is displayed by default. The first mode displays each
1859 row on a horizontal line, the second rotates the headers by 90
1860 degrees, so you can use descriptive headers even though fields only
1861 contain small values and still print them out. The vertical mode sorts
1862 each row on a vertical lineup.<br /><br />
1864 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1865 the rotation of the header for horizontalflipped is done via CSS. If
1866 set to 'fake' PHP does the transformation for you, but of course this
1867 does not look as good as CSS.</dd>
1871 string or integer</dt>
1872 <dd>When editing/creating new columns in a table all fields normally get
1873 lined up one field a line. (default: 'horizontal'). If you set this to
1874 'vertical' you can have each field lined up vertically beneath each
1875 other. You can save up a lot of place on the horizontal direction and
1876 no longer have to scroll. If you set this to integer, editing of fewer
1877 columns will appear in 'vertical' mode, while editing of more fields
1878 still in 'horizontal' mode. This way you can still effectively edit
1879 large number of fields, while having full view on few of them.</dd>
1883 </dt>
1885 display of column comments in Browse or Property display. In browse
1886 mode, the comments are shown inside the header. In property mode,
1887 comments are displayed using a CSS-formatted dashed-line below the
1888 name of the field. The comment is shown as a tool-tip for that field.
1889 </dd>
1901 <dd>Whether to display a link to validate a query in any SQL Query box.
1908 <dd>
1909 The name of the directory where
1911 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1912 are available under a drop-down box when you click the database or
1913 table name, then the Import tab.
1914 <br /><br />
1916 If you want different directory for each user, %u will be replaced
1917 with username.<br /><br />
1921 compressed formats is enabled).<br /><br />
1923 This feature is useful when your file is too big to be uploaded via
1925 uploads are disabled in PHP.<br /><br />
1927 Please note that if PHP is running in safe mode, this directory must
1928 be owned by the same user as the owner of the phpMyAdmin scripts.
1929 <br /><br />
1933 alternatives.
1934 </dd>
1937 <dd>
1938 The name of the directory where dumps can be saved.<br /><br />
1940 If you want different directory for each user, %u will be replaced
1941 with username.<br /><br />
1943 Please note that the directory must exist and has to be writable for
1944 the user running webserver.<br /><br />
1946 Please note that if PHP is running in safe mode, this directory must
1947 be owned by the same user as the owner of the phpMyAdmin scripts.
1948 </dd>
1951 <dd>
1952 The name of the directory where temporary files can be stored.
1953 <br /><br />
1955 This is needed for native MS Excel export, see
1961 <br /><br />
1963 If the directory where phpMyAdmin is installed is subject to an
1965 temporary directory in some directory accessible by the web
1966 server. However for security reasons, this directory should be outside
1967 the tree published by webserver. If you cannot avoid having this
1968 directory published by webserver, place at least an empty
1970 possible.
1971 <br /><br />
1973 This directory should have as strict permissions as possible as the only
1974 user required to access this directory is the one who runs the
1975 webserver. If you have root privileges, simply make this user owner of
1976 this directory and make it accessible only by it:
1977 <br /><br />
1979 <pre>
1980 chown www-data:www-data tmp
1981 chmod 700 tmp
1982 </pre>
1984 If you cannot change owner of the directory, you can achieve a similar
1987 <pre>
1988 chmod 700 tmp
1989 setfacl -m "g:www-data:rwx" tmp
1990 setfacl -d -m "g:www-data:rwx" tmp
1991 </pre>
1993 If neither of above works for you, you can still make the directory
1995 system reading and writing data in this directory.
1996 </dd>
1999 <dd>
2000 In this array are defined default parameters for export, names of
2001 items are similar to texts seen on export page, so you can easily
2002 identify what they mean.
2003 </dd>
2006 <dd>
2007 In this array are defined default parameters for import, names of
2008 items are similar to texts seen on import page, so you can easily
2009 identify what they mean.
2010 </dd>
2013 <dd>
2014 Repeat the headers every X cells, or 0 to deactivate.
2015 </dd>
2023 </dt>
2024 <dd>
2025 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2026 or icon is always displayed on the left panel. If JavaScript is enabled in
2027 your browser, a click on this opens a distinct query window, which is
2028 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2029 changes to display a query box.<br /><br />
2031 The size of this query window can be customized with
2033 - both integers for the size in pixels. Note that normally, those
2035 theme you are using.<br /><br />
2039 opens the query window and puts the current query
2040 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2041 query in the right panel's query box.
2042 <br /><br />
2043 The usage of the JavaScript query window is recommended if you have a
2044 JavaScript enabled browser. Basic functions are used to exchange quite
2045 a few variables, so most 4th generation browsers should be capable to
2046 use that feature. It currently is only tested with Internet Explorer 6
2047 and Mozilla 1.x.
2048 <br /><br />
2050 to a table, which has to be created by you (see <a
2052 all your queries will be appended to the form, but only as long as
2053 your window is opened they remain saved.
2054 <br /><br />
2055 When using the JavaScript based query window, it will always get
2056 updated when you click on a new table/db to browse and will focus if
2057 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2058 the query window by checking the box "Do not overwrite this query from
2059 outside the window" below the query textarea. Then you can browse
2060 tables/databases in the background without losing the contents of the
2061 textarea, so this is especially useful when composing a query with
2062 tables you first have to look in. The checkbox will get automatically
2063 checked whenever you change the contents of the textarea. Please
2064 uncheck the button whenever you definitely want the query window to
2065 get updated even though you have made alterations.
2066 <br /><br />
2069 <br /><br />
2070 The query window also has a custom tabbed look to group the features.
2072 default tab to be used when opening the query window. It can be set to
2073 either 'sql', 'files', 'history' or 'full'.</dd>
2079 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2081 If the approximate row count as returned by
2084 count will be used.
2085 </dd>
2087 <dd>For VIEWs, since obtaining the exact count could have an
2088 impact on performance, this value is the maximum to be displayed, using
2090 any row counting.
2091 </dd>
2095 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
2097 page. By clicking on the button 'toggle scratchboard' on the page
2098 where you edit x/y coordinates of those elements you can activate a
2099 scratchboard where all your elements are placed. By clicking on an
2100 element, you can move them around in the pre-defined area and the x/y
2101 coordinates will get updated dynamically. Likewise, when entering a
2102 new position directly into the input field, the new position in the
2103 scratchboard changes after your cursor leaves the input field.<br />
2104 You have to click on the 'OK'-button below the tables to save the new
2105 positions. If you want to place a new element, first add it to the
2106 table of elements and then you can drag the new element around.<br />
2107 By changing the paper size and the orientation you can change the size
2108 of the scratchboard as well. You can do so by just changing the
2109 dropdown field below, and the scratchboard will resize automatically,
2110 without interfering with the current placement of the elements.<br />
2111 If ever an element gets out of range you can either enlarge the paper
2112 size or click on the 'reset' button to place all elements below each
2113 other.<br />
2115 get this control to work. The basic Drag&Drop script functionality
2116 was kindly borrowed from www.youngpup.net and is underlying so
2117 specific license.</dd>
2120 <dd>Sorts database and table names according to natural order (for example,
2121 t1, t2, t10). Currently implemented in the left panel (Light mode)
2122 and in Database view, for the table list.</dd>
2133 <dd>Allows you to specify window's title bar. Following magic string can
2134 be used to get special values:
2135 <dl>
2141 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
2150 </dl>
2151 </dd>
2161 </dd>
2164 <dd>If theme manager is active, use this as the path of the subdirectory
2165 containing all the themes.</dd>
2179 </dt>
2180 <dd>Default queries that will be displayed in query boxes when user didn't
2181 specify any. Use %d for database name, %t for table name and %f for a
2182 comma separated list of field names. Note that %t and %f are only
2186 <dd>
2187 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
2188 default we use HTML to format the query, but you can disable this by
2190 </dd>
2193 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2194 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2195 query inside a bracket is indented. By changing
2198 specifies the units of the indent amount that you specified. This is
2199 used via stylesheets.</dd>
2202 <dd>This array is used to define the colours for each type of element of
2203 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2205 If you specify an empty string for the color of a class, it is ignored
2206 in creating the stylesheet.
2207 You should not alter the class names, only the colour strings.<br />
2228 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2232 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2233 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2234 </ul>
2235 </dd>
2239 <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,
2240 as originally published on
2242 <br />
2243 For help in setting up your system to use the service, see the
2245 </dd>
2249 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2250 and any password, so we use those by default. Instead, if
2251 you have an account with them, you can put your login details
2252 here, and it will be used in place of the anonymous login.</dd>
2253 </dl>
2254 </dd>
2257 <dd><b>DEVELOPERS ONLY!</b></dd>
2260 <dd><b>DEVELOPERS ONLY!</b><br />
2261 Enable logging queries and execution times to be displayed in the bottom
2262 of main page (right frame).</dd>
2265 <dd><b>DEVELOPERS ONLY!</b><br />
2266 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2267 the code.<br />
2268 For help in setting up your system to this, see the
2272 <dd><b>DEVELOPERS ONLY!</b><br />
2273 Enable profiling support for phpMyAdmin. This will append a chunk of data
2274 to the end of every page displayed in the main window with profiling
2275 statistics for that page.<br />
2276 You may need to increase the maximum execution time for this to
2277 complete successfully.<i>Profiling was removed from the code for
2278 version 2.9.0 due to licensing issues.</i></dd>
2280 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2281 <dd><b>DEVELOPERS ONLY!</b><br />
2282 When profiling data is displayed, this variable controls the threshold of
2283 display for any profiling data, based on the average time each time has
2284 taken. If it is over the threshold it is displayed, otherwise it is not
2285 displayed. This takes a value in milliseconds. In most cases you don't need
2286 to edit this.</dd>
2289 <dd>All possible types of a MySQL column. In most cases you don't need to
2290 edit this.</dd>
2293 <dd>Possible attributes for fields. In most cases you don't need to edit
2294 this.</dd>
2297 <dd>A list of functions MySQL supports. In most cases you don't need to
2298 edit this.</dd>
2301 <dd>Mapping of column types to meta types used for preferring displayed
2302 functions. In most cases you don't need to edit this.</dd>
2305 <dd>Functions preferred for column meta types as defined in
2306 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2307 to edit this.</dd>
2310 <dd>Functions selected by default when inserting/changing row, Functions
2311 are defined for meta types from
2313 <code>first_timestamp</code>, which is used for first timestamp column
2314 in table.</dd>
2317 <dd>Operators available for search operations on numeric and date fields.
2318 </dd>
2321 <dd>Operators available for search operations on character fields.
2322 Note that we put <code>LIKE</code> by default instead of
2323 <code>LIKE %...%</code>, to avoid unintended performance problems
2324 in case of huge tables.</dd>
2327 <dd>Operators available for search operations on enum fields.</dd>
2330 <dd>Additional operators available for search operations when the
2331 field can be null.</dd>
2333 </dl>
2335 <!-- TRANSFORMATIONS -->
2341 </ol>
2345 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2347 section</a> on how to do so.</p>
2349 <p> You can apply different transformations to the contents of each field. The
2350 transformation will take the content of each field and transform it with
2351 certain rules defined in the selected transformation.</p>
2353 <p> Say you have a field 'filename' which contains a filename. Normally you would
2354 see in phpMyAdmin only this filename. Using transformations you can transform
2355 that filename into a HTML link, so you can click inside of the phpMyAdmin
2356 structure on the field's link and will see the file displayed in a new browser
2357 window. Using transformation options you can also specify strings to
2358 append/prepend to a string or the format you want the output stored in.</p>
2360 <p> For a general overview of all available transformations and their options,
2361 you can consult your
2362 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2363 installation.</p>
2365 <p> For a tutorial on how to effectively use transformations, see our
2367 the official phpMyAdmin homepage.</p>
2371 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2372 clicking on the 'Structure' link for a table). There click on
2373 "Change" (or change icon) and there you will see three new fields at
2374 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2375 'Transformation options'.</p>
2377 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2378 that corresponds to the column's contents. Please note that
2379 transformations are inactive as long as no MIME-type is selected.</li>
2381 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2382 hopefully growing amount of pre-defined transformations. See below for information on
2383 how to build your own transformation.<br />
2385 There are global transformations and mimetype-bound transformations. Global transformations
2386 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2387 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2388 transformations which operate on the main mimetype (like 'image'), which will most likely
2389 take the subtype into regard, and those who only operate on a
2390 specific subtype (like 'image/jpeg').<br />
2392 You can use transformations on mimetypes for which the function was not defined for. There
2393 is no security check for you selected the right transformation, so take care of what the
2394 output will be like.</li>
2396 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2397 transform-function specific options here. Usually the transforms can operate with default
2398 options, but it is generally a good idea to look up the overview to see which options are
2399 necessary.<br />
2401 Much like the ENUM/SET-Fields, you have to split up several options using the format
2402 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2403 parsed as an array, leaving the first value the first element in the array, and so
2404 forth.<br />
2406 If you want to specify a MIME character set you can define it in the transformation_options.
2407 You have to put that outside of the pre-defined options of the specific mime-transform,
2409 for which you can specify 2 options and you want to append a character set, enter "'first
2410 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2412 </ul>
2416 <p> All mimetypes and their transformations are defined through single files in
2417 the directory 'libraries/transformations/'.</p>
2419 <p> They are stored in files to ease up customization and easy adding of new
2420 transformations.</p>
2422 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2423 always work. It makes no sense to apply a transformation to a mimetype, the
2424 transform-function doesn't know to handle.</p>
2426 <p> One can, however, use empty mime-types and global transformations which should work
2427 for many mimetypes. You can also use transforms on a different mimetype they where built
2428 for, but pay attention to option usage as well as what the transformation does to your
2429 field.</p>
2431 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2432 any other transform function and provides some basic functions.</p>
2434 <p> There are 5 possible file names:</p>
2436 <ol><li>A mimetype+subtype transform:<br /><br />
2438 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2440 Please not that mimetype and subtype are separated via '_', which shall
2441 not be contained in their names. The transform function/filename may
2442 contain only characters which cause no problems in the file system as
2443 well as the PHP function naming convention.<br /><br />
2445 The transform function will the be called
2446 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2448 <b>Example:</b><br /><br />
2450 <tt>text_html__formatted.inc.php</tt><br />
2451 <tt>PMA_transform_text_html__formatted()</tt></li>
2453 <li>A mimetype (w/o subtype) transform:<br /><br />
2455 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2457 Please note that there are no single '_' characters.
2458 The transform function/filename may contain only characters which cause
2459 no problems in the file system as well as the PHP function naming
2460 convention.<br /><br />
2462 The transform function will the be called
2463 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2465 <b>Example:</b><br /><br />
2467 <tt>text__formatted.inc.php</tt><br />
2468 <tt>PMA_transform_text__formatted()</tt></li>
2470 <li>A mimetype+subtype without specific transform function<br /><br />
2472 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2474 Please note that there are no '__' characters in the filename. Do not
2475 use special characters in the filename causing problems with the file
2476 system.<br /><br />
2478 No transformation function is defined in the file itself.<br /><br />
2480 <b>Example:</b><br /><br />
2482 <tt>text_plain.inc.php</tt><br />
2483 (No function)</li>
2485 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2487 <tt>[mimetype].inc.php</tt><br /><br />
2489 Please note that there are no '_' characters in the filename. Do not use
2490 special characters in the filename causing problems with the file system.
2491 <br /><br />
2493 No transformation function is defined in the file itself.<br /><br />
2495 <b>Example:</b><br /><br />
2497 <tt>text.inc.php</tt><br />
2498 (No function)</li>
2500 <li>A global transform function with no specific mimetype<br /><br />
2502 <tt>global__[transform].inc.php</tt><br /><br />
2504 The transform function will the be called
2505 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2507 <b>Example:</b><br /><br />
2509 <tt>global__formatted</tt><br />
2510 <tt>PMA_transform_global__formatted()</tt></li>
2511 </ol>
2513 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2514 transform function.</p>
2516 <p> All filenames containing no '__' in themselves are not shown as valid transform
2517 functions in the dropdown.</p>
2519 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2520 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2521 without a transform function. Also note the introduction of a function description in
2522 the language files. For each function a $strTransformation_[filename without .inc.php]
2523 has to exist.</p>
2525 <p> You can use the template generator to generate new functions and entries in the
2526 language file.</p>
2528 <p> To create a new transform function please see
2529 <tt>libraries/transformations/template_generator.sh</tt>.
2530 To create a new, empty mimetype please see
2531 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2533 <p> A transform function always gets passed three variables:</p>
2535 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2536 you want to transform.</li>
2537 <li><b>$options</b> - Contains any user-passed options to a transform function
2538 as an array.</li>
2539 <li><b>$meta</b> - Contains an object with field information to your column.
2540 The data is drawn from the output of the
2542 function. This means, all object properties described on the
2544 available in this variable and can be used to transform a field accordingly
2545 to unsigned/zerofill/not_null/... properties.<br />
2546 The $meta->mimetype variable contains the original MIME-type of the
2547 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2548 </ol>
2550 <!-- FAQ -->
2557 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2562 </ol>
2564 <p> Please have a look at our
2566 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2567 features and or interface.</p>
2573 action is required or phpMyAdmin sends a blank page or a page full of
2574 cryptic characters to my browser, what can I do?</a></h4>
2577 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2578 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2579 configuration file.<br /></p>
2584 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2585 See also the
2587 entry about PHP bugs with output buffering.<br />
2588 If your server keeps crashing, please ask for help in the various Apache
2589 support groups.</p>
2598 application misbehaved by not returning a complete set of
2600 </h4>
2602 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2603 Have a look at the last message in this
2605 official PHP bug database.</p>
2610 and/or many error messages with the
2612 mode.</a></h4>
2614 <p> This is a known problem with the PHP
2616 filter: it's not so stable. Please use instead the cookie authentication mode.
2617 </p>
2622 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2623 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2624 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2625 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2626 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2631 work.</a></h4>
2633 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2634 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2635 or not, and so on). So, you must have Zlib/Bzip2
2636 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br /></p>
2640 an error about safe mode being in effect.</a></h4>
2642 <p> Your uploaded file is saved by PHP in the "upload dir", as
2643 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2644 the system default is <i>/tmp</i>).<br />
2645 We recommend the following setup for Apache servers running in safe mode,
2646 to enable uploads of files while being reasonably secure:</p>
2648 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2649 <li>give ownership to the Apache server's user.group:
2650 <tt>chown apache.apache /tmp/php</tt></li>
2651 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2652 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2653 <li>restart Apache</li>
2654 </ul>
2658 general file uploads don't work on my system and uploaded files have a
2659 <tt>Content-Type:</tt> header in the first line.</a></h4>
2661 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2662 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2663 So the problem is that this package has a serious bug that was corrected
2664 ages ago in PHP (2001-01-28: see
2666 for more details). The problem is that the bugged package is still
2667 available though it was corrected (see
2669 for more details).<br />
2670 So please download
2671 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2672 and the problem should go away.<br />
2673 And that fixes the \r\n problem with file uploads!</p>
2677 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2678 I'm using the Apache server.</a></h4>
2680 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2681 your <i>httpd.conf</i>:</p>
2685 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2689 uploading a file from the query box.</a></h4>
2691 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2692 restrictions. However you need to create temporary directory and
2694 The uploaded files will be moved there, and after execution of your
2700 <p> The MySQL manual explains how to
2702 reset the permissions</a>.</p>
2707 execute a bookmark.</a></h4>
2709 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2710 cannot access the uploaded query.</p>
2715 submit a query from the convenient text area.</a></h4>
2717 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2718 and try to increase it.</p>
2722 </h4>
2724 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2725 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2726 names to align with current standards.</p>
2731 </h4>
2733 <p> Starting with version 2.7.0, the import engine has been re–written and these
2734 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2735 to take advantage of the new import features.</p>
2737 <p> The first things to check (or ask your host provider to check) are the
2738 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2739 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2740 All of these three settings limit the maximum size of data that can be
2741 submitted and handled by PHP. One user also said that post_max_size
2742 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2744 There exist several workarounds if your upload is too big or your
2745 hosting provider is unwilling to change the settings:</p>
2748 feature. This allows one to
2749 upload a file to the server via scp, ftp, or your favorite file transfer
2750 method. PhpMyAdmin is then able to import the files from the temporary
2752 section</a> of this document.</li>
2754 BigDump</a>) to split the files before uploading. We cannot support this
2755 or any third party applications, but are aware of users having success
2756 with it.</li>
2757 <li>If you have shell (command line) access, use MySQL to import the files
2758 directly. You can do this by issuing the "source" command from
2759 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2760 </ul>
2764 support?</a></h4>
2766 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2767 older MySQL versions, you need to use the latest 2.x branch. phpMyAdmin can
2768 connect to your MySQL server using PHP's classic
2771 is available in php 5.0. The latter one should be used unless you have
2772 good reason not to do so.<br />
2773 When compiling php, we strongly recommend that you manually link the MySQL
2774 extension of your choice to a MySQL client library of at least the same
2775 minor version since the one that is bundled with some PHP distributions is
2781 message, "Client does not support authentication protocol requested
2782 by server; consider upgrading MySQL client"</a></h5>
2784 <p> You tried to access MySQL with an old MySQL client library. The version of
2785 your MySQL client library can be checked in your phpinfo() output.
2786 In general, it should have at least the same minor version as your server
2790 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2791 changed the authentication hash and your PHP is trying to use the old method.
2793 with the proper client library to match your MySQL installation. Your
2794 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2795 More information (and several workarounds) are located in the
2797 </p>
2804 script seems not to know the font face I'm using!</a></h4>
2806 <p> The "FPDF" library we're using for this feature requires some
2807 special files to use font faces.<br />
2809 these files.</p>
2813 check PHP Configuration".</a></h4>
2815 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2816 "MySQL extension". This extension may be part of the PHP
2817 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2818 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2819 to load the extension but failed.<br /><br />
2821 Usually, the problem is solved by installing a software package called
2822 "PHP-MySQL" or something similar.</p>
2827 and I cannot log in using cookie auth.</a></h4>
2829 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2833 so I cannot upload.</a></h4>
2835 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2836 parameter is not set to "on".</p>
2840 a new table the table and field names are changed to lowercase!</a></h4>
2842 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2843 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2844 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2845 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2846 directory and add the following line to the group [mysqld]:</p>
2848 <pre>set-variable = lower_case_table_names=0</pre>
2850 <p> Next, save the file and restart the MySQL service. You can always check the
2851 value of this directive using the query</p>
2853 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2860 and I get problems, such as undefined variables when I run a
2863 <p> A tip from Jose Fandos: put a comment on the following two lines
2864 in httpd.conf, like this:</p>
2866 <pre>
2867 # mod_gzip_item_include file \.php$
2869 </pre>
2871 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2872 PHP scripts. Of course you have to restart Apache.</p>
2877 I get the error "No input file specified" when trying to
2878 run phpMyAdmin.</a></h4>
2880 <p> This is a permission problem. Right-click on the phpmyadmin folder
2881 and choose properties. Under the tab Security, click on "Add"
2882 and select the user "IUSR_machine" from the list. Now set his
2883 permissions and it should work.</p>
2887 db_structure.php with plenty of tables).</a></h4>
2890 GZIP output buffering is enabled. If you turn off it (by
2892 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2893 PHP 5.0.0.</p>
2897 message 'Errorcode: 13'. What does this mean?</a></h4>
2899 <p> This can happen due to a MySQL bug when having database / table names with
2900 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2901 To fix this, turn off this directive, convert all database and table names
2902 to lower case and turn it on again. Alternatively, there's a bug-fix
2903 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2907 and the fields are duplicated.</a></h4>
2909 <p> It is possible to configure Apache in such a way that PHP has problems
2910 interpreting .php files.</p>
2912 <p> The problems occur when two different (and conflicting) set of directives
2913 are used:</p>
2915 <pre>
2916 SetOutputFilter PHP
2917 SetInputFilter PHP
2918 </pre>
2920 <p> and</p>
2922 <pre>AddType application/x-httpd-php .php</pre>
2924 <p> In the case we saw, one set of directives was in
2925 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2926 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2927 The recommended way is with <tt>AddType</tt>, so just comment out
2928 the first set of lines and restart Apache:</p>
2930 <pre>
2931 #SetOutputFilter PHP
2932 #SetInputFilter PHP
2933 </pre>
2938 <p> This problem is known to happen when the server is running Turck MMCache
2939 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2944 <p> Yes.<br />
2945 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2946 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2947 <tt>error_reporting</tt> settings.
2948 </p>
2951 <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>
2953 <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>
2956 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2957 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2958 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2959 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2960 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2961 enabled.) Click <tt>OK</tt>.</li>
2962 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2963 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2964 </ol>
2968 PHP 5.0.4 on 64-bit systems?</a></h4>
2970 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2971 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2977 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
2978 the order of the server paragraph in <tt>config.inc.php</tt>.
2979 Table and script parts are optional. If you want
2980 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2981 some configuration. Following lines apply only for <a
2983 that you have enabled some features within global configuration. You need
2984 <code>Options FollowSymLinks</code> and <code>AllowOverride
2985 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2986 you need mod_rewrite to be enabled. Then you just need to create following
2987 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2988 (don't forget to change directory name inside of it):</p>
2990 <pre>
2991 RewriteEngine On
2992 RewriteBase /path_to_phpMyAdmin
2993 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
2994 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
2995 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
2996 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
2997 </pre>
3000 <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>
3002 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3003 following rewrite rule:</p>
3005 <pre>
3006 RewriteEngine On
3007 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3008 </pre>
3012 </h4>
3013 <p>
3014 There can be many explanations to this and a look at your server's
3015 error log file might give a clue.
3016 </p>
3020 password encryption in cookie auth doesn't work.</a></h4>
3022 <p> If your cluster consist of different architectures, PHP code used for
3023 encryption/decryption won't work correct. This is caused by use of
3024 pack/unpack functions in code. Only solution is to use mcrypt extension
3025 which works fine in this case.</p>
3030 <p> Yes but the default configuration values of Suhosin are known to cause
3031 problems with some operations, for example editing a table with many
3032 columns and no primary key or with textual primary key.
3033 </p>
3034 <p>
3035 Suhosin configuration might lead to malfunction in some cases and it can
3036 not be fully avoided as phpMyAdmin is kind of application which needs to
3037 transfer big amounts of fields in single HTTP request, what is something
3038 what Suhosin tries to prevent. Generally all
3039 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3040 <code>suhosin.get.*</code> directives can have negative effect on
3041 phpMyAdmin usability. You can always find in your error logs which limit
3042 did cause dropping of variable, so you can diagnose the problem and adjust
3043 matching configuration variable.
3044 </p>
3045 <p>
3046 The default values for most Suhosin configuration options will work in most
3047 scenarios, however you might want to adjust at least following parameters:
3048 </p>
3050 <ul>
3051 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.request.max_vars">suhosin.request.max_vars</a> should be increased (eg. 2048)</li>
3052 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.post.max_vars">suhosin.post.max_vars</a> should be increased (eg. 2048)</li>
3053 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.request.max_array_index_length">suhosin.request.max_array_index_length</a> should be increased (eg. 256)</li>
3054 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.post.max_array_index_length">suhosin.post.max_array_index_length</a> should be increased (eg. 256)</li>
3055 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.request.max_totalname_length">suhosin.request.max_totalname_length</a> should be increased (eg. 8192)</li>
3056 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.post.max_totalname_length">suhosin.post.max_totalname_length</a> should be increased (eg. 8192)</li>
3057 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.sql.bailout_on_error">suhosin.sql.bailout_on_error</a> needs to be disabled (the default)</li>
3058 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#logging_configuration">suhosin.log.*</a> should not include SQL, otherwise you get big slowdown</li>
3059 </ul>
3061 <p>
3063 <tt>SuhosinDisableWarning</tt> directive</a>.
3064 </p>
3068 but then my connection is redirected back to http. What can cause this
3069 behavior?</a></h4>
3071 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3072 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>
3075 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work.</a></h4>
3077 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3078 Example from the Apache 2.2 documentation:</p>
3079 <pre>
3080 ProxyPass /mirror/foo/ http://backend.example.com/
3081 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3082 ProxyPassReverseCookieDomain backend.example.com public.example.com
3083 ProxyPassReverseCookiePath / /mirror/foo/
3084 </pre>
3086 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3087 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3088 This is not specific to phpmyadmin, it's just the behavior of Apache.
3089 </p>
3091 <pre>
3092 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3093 ProxyPassReverse /mirror/foo/
3094 http://backend.example.com/%7Euser/phpmyadmin
3095 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3096 </pre>
3098 <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>
3099 for more details.</p>
3103 privileges, I get an error about an unknown column.</a></h4>
3105 <p> The MySQL server's privilege tables are not up to date, you need to run
3106 the <tt>mysql_upgrade</tt> command on the server.</p>
3113 headers already sent by ..." is displayed, what's the problem?</a></h4>
3115 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3116 (I.E. no blank lines, no spaces, no characters...) neither before the
3117 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3118 tag at the end. We also got a report from a user under IIS, that used
3119 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3120 contained an end-of-line character (hex 0A) at the end; removing this character
3121 cleared his errors.</p>
3126 <p> Either there is an error with your PHP setup or your username/password is
3127 wrong. Try to make a small script which uses mysql_connect and see if it
3128 works. If it doesn't, it may be you haven't even compiled MySQL support
3129 into PHP.</p>
3133 connect to local MySQL server through socket '/tmp/mysql.sock'
3134 (111) ..." is displayed. What can I do?</a></h4>
3136 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3138 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3139 In your <i>php.ini</i> you will find a line</p>
3141 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3143 <p> change it to</p>
3145 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3147 <p> Then restart apache and it will work.</p>
3149 <p> Here is a fix suggested by Brad Ummer:</p>
3151 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3152 To do this, telnet to your server and go to the MySQL bin directory. In
3153 this directory there should be a file named <i>mysqladmin</i>. Type
3154 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3155 info about your MySQL server, including the socket
3156 (<i>/tmp/mysql.sock</i>, for example).</li>
3157 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3158 phpMyAdmin, you need to complete the socket information in the
3159 <i>config.inc.php</i>.<br />
3160 For example:
3162 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3163 <br /><br />
3165 Please also make sure that the permissions of this file allow to be readable
3166 by your webserver (i.e. '0755').</li>
3167 </ul>
3169 <p> Have also a look at the
3171 corresponding section of the MySQL documentation</a>.</p>
3175 what can I do?</a></h4>
3178 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3179 sometime.<br />
3180 Also have a look at your PHP version number: if it contains "4.0b..."
3181 it means you're running a beta version of PHP. That's not a so good idea,
3182 please upgrade to a plain revision.</p>
3186 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3187 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3189 <p> Check the value you set for the
3191 directive in the phpMyAdmin configuration file.</p>
3195 password: YES)"-error when trying to access a MySQL-Server on a
3196 host which is port-forwarded for my localhost.</a></h4>
3198 <p> When you are using a port on your localhost, which you redirect via
3199 port-forwarding to another host, MySQL is not resolving the localhost
3200 as expected.<br />
3201 Erik Wasser explains: The solution is: if your host is "localhost"
3202 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
3203 connection for speeding up things. And that doesn't work in this configuration
3204 with port forwarding.<br />
3210 <p> Themes are configured with
3214 <br />
3216 should not delete the directory "original" or its underlying
3217 structure, because this is the system theme used by phpMyAdmin.
3218 "original" contains all images and styles, for backwards
3219 compatibility and for all themes that would not include images or css-files.
3220 <br /><br />
3223 is enabled, you can select your favorite theme on the main page. Your
3224 selected theme will be stored in a cookie.<br /><br /></p>
3226 <p> To create a theme:</p>
3228 <ul><li>make a new subdirectory (for example "your_theme_name") under
3230 (by default <tt>themes</tt>)</li>
3231 <li>copy the files and directories from "original" to
3232 "your_theme_name"</li>
3233 <li>edit the css-files in "your_theme_name/css"</li>
3234 <li>put your new images in "your_theme_name/img"</li>
3235 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3236 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3237 contain your chosen theme name, that will be visible in user interface</li>
3238 <li>make a new screenshot of your theme and save it under
3239 "your_theme_name/screen.png"</li>
3240 </ul>
3242 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3243 theme verbose name, theme generation and theme version. These versions and
3244 generations are enumerated from 1 and do not have any direct dependence on
3245 phpMyAdmin version. Themes within same generation should be backwards
3246 compatible - theme with version 2 should work in phpMyAdmin requiring
3247 version 1. Themes with different generation are incompatible.</p>
3249 <p> If you do not want to use your own symbols and buttons, remove the
3250 directory "img" in "your_theme_name". phpMyAdmin will
3251 use the default icons and buttons (from the system-theme "original").
3252 </p>
3256 what can I do?</a></h4>
3258 <p> Here are a few points to check:</p>
3260 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3262 directive empty. See also
3264 </li>
3265 <li>Maybe you have a broken PHP installation or you need to upgrade
3266 your Zend Optimizer. See
3268 http://bugs.php.net/bug.php?id=31134</a>.
3269 </li>
3270 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3271 set to the default (200) or another low value, you could get this
3272 error if your table has a high number of columns. Adjust this setting
3273 accordingly. (Thanks to Klaus Dorninger for the hint).
3274 </li>
3275 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3276 of ";" will cause this error. Replace it with "&;".
3277 </li>
3279 you might want to increase
3281 </li>
3282 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3283 </li>
3284 </ul>
3289 <p> To be able to see a progress bar during your uploads, your server must
3292 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3293 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3300 who logged out can not log in again in with the same nick.</a></h4>
3302 <p> This is related to the authentication mechanism (protocol) used by
3303 phpMyAdmin. To bypass this problem: just close all the opened
3304 browser windows and then go back to phpMyAdmin. You should be able to
3305 log in again.</p>
3309 limit error or a time limit error.</a></h4>
3311 <p> Compressed dumps are built in memory and because of this are limited to
3312 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3313 using
3315 (enabled by default). Zip exports can not be handled this way, so if you need
3316 Zip files for larger dump, you have to use another way.</p>
3320 when I rename a table or a column.</a></h4>
3322 <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>
3326 bundled with the MySQL server distribution.</a></h4>
3328 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3330 <pre>
3331 -- MySQL dump 8.22
3332 --
3333 -- Host: localhost Database: database
3334 ---------------------------------------------------------
3335 -- Server version 3.23.54
3336 </pre>
3338 <p> The invalid part of the code is the horizontal line made of dashes that
3339 appears once in every dump created with mysqldump. If you want to run your
3340 dump you have to turn it into valid MySQL. This means, you have to add a
3341 whitespace after the first two dashes of the line or add a # before it:
3342 <br />
3343 <code>
3344 -- -------------------------------------------------------<br />
3345 </code>
3346 or<br />
3347 <code>
3348 #---------------------------------------------------------
3349 </code>
3350 </p>
3357 <p> Please note that you should not use the separating string multiple times
3358 without any characters between them, or at the beginning/end of your table
3359 name. If you have to, think about using another TableSeparator or disabling
3360 that feature</p>
3365 <p> In Relation view, being able to choose a table in another database,
3366 or having more than one index field in the foreign key.<br /><br/>
3367 In Query-by-example (Query), automatic generation of the query
3368 LEFT JOIN from the foreign table.<br /><br/>
3369 </p>
3373 I get series of errors like "Warning: unable to parse url". How
3374 can this be fixed?</a></h4>
3375 <p>
3376 Your table neither have a primary key nor an unique one, so we must use a
3377 long expression to identify this row. This causes problems to parse_url
3378 function. The workaround is to create a primary or unique key.
3379 <br />
3380 </p>
3384 a MIME-Transformation onto!</a></h4>
3386 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3387 nested forms can be put inside the table where phpMyAdmin displays the results.
3388 You can, however, use any form inside of a table if keep the parent
3389 form-container with the target to tbl_row_delete.php and just put your own
3390 input-elements inside. If you use a custom submit input field, the form will
3391 submit itself to the displaying page again, where you can validate the
3392 $HTTP_POST_VARS in a transformation.
3394 For a tutorial on how to effectively use transformations, see our
3396 on the official phpMyAdmin-homepage.</p>
3400 MySQL server</a></h4>
3402 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3405 http://dev.mysql.com/doc/mysql/en/ansi-mode.html</a>). Most important of all,
3406 the quote-character (") is interpreted as an identifier quote character and
3407 not as a string quote character, which makes many internal phpMyAdmin
3409 statements. There is no workaround to this behaviour. News to this item will
3410 be posted in Bug report
3411 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3412 </p>
3416 more that one column with the same value
3417 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3418 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3420 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3421 can use it for the Edit and Delete links.</p>
3426 <p> phpMyAdmin uses a quick method to get the row count, and this method
3427 only returns an approximate count in the case of InnoDB tables. See
3429 a way to modify those results, but
3430 this could have a serious impact on performance.</p>
3435 <p> The number of records in queries containing COUNT and GROUP BY is
3436 not correctly calculated. Also, sorting results of a query like
3441 containing an hyphen.
3442 </a></h4>
3443 <p>
3444 The tests I have made with current MySQL 4.1.11 API shows that the
3445 API does not accept this syntax for the USE command. Enclosing the
3446 db name with backquotes works. For further confusion, no backquotes
3447 are needed with command-line mysql.
3448 </p>
3451 <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>
3452 <p>
3453 This has been a known limitation of phpMyAdmin since the beginning and
3454 it's not likely to be solved in the future.
3455 </p>
3457 <!-- Begin: Excel import limitations -->
3460 <a href="#faq3_15">3.15 When I import an Excel spreadsheet, some cells with calculations do not display correctly.</a></h4>
3461 <p>
3462 phpMyAdmin uses the <a href="http://www.codeplex.com/PHPExcel/" target="_blank">PHPExcel</a> library to parse Excel XLS and XLSX spreadsheets.
3463 Therefore, any limitations that are listed on their page regarding Excel calculations will also apply here.
3464 <br /><br />
3465 PHPExcel will be kept up to date so as to make all improvements available to phpMyAdmin users.
3466 </p>
3469 <a href="#faq3_16">3.16 When I compress (gzip, bzip2, zip) an Excel workbook and attempt to import it, nothing happens.</a></h4>
3470 <p>
3471 Since Excel XLSX workbooks are already compressed, there is often times only a small benefit from compressing them yet again.
3472 Support for compressed Excel XLSX and XLS workbooks may be added in the future.
3473 </p>
3476 <a href="#faq3_17">3.17 When I import an Excel spreadsheet, my custom cell types are not represented as they are in Excel.</a></h4>
3477 <p>
3478 Excel's internal representation of custom cell types is rather muddled (especially in Excel 97-2003 binary XLS files). If possible,
3479 consider using a built-in type. These are almost always guarenteed to import correctly.
3480 </p>
3482 <!-- End: Excel import limitations -->
3483 <!-- Begin: CSV import limitations -->
3486 <a href="#faq3_18">3.18 When I import a CSV file that contains multiple tables, they are lumped together into a single table.</a></h4>
3487 <p>
3488 There is no reliable way to differetiate tables in CSV format. For the time being, you will have to break apart CSV files containing multiple tables.
3489 </p>
3491 <!-- End: CSV import limitations -->
3492 <!-- Begin: Import type-detection limitations -->
3495 <a href="#faq3_19">3.19 When I import a file and have phpMyAdmin determine the appropriate data structure it only uses int, decimal, and varchar types.</a></h4>
3496 <p>
3497 Currently, the import type-detection system can only assign these MySQL types to columns. In future, more will likely be added but for the time being
3498 you will have to edit the structure to your liking post-import.
3499 <br /><br />
3500 Also, you should note the fact that phpMyAdmin will use the size of the largest item in any given column as the column size for the appropriate type. If you
3501 know you will be adding larger items to that column then you should manually adjust the column sizes accordingly. This is done for the sake of efficiency.
3502 </p>
3504 <!-- End: Import type-detection limitations -->
3506 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3509 <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
3510 need to install it for each customer.
3511 </a></h4>
3512 <p>
3513 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3514 your users. The development of this feature was kindly sponsored by
3515 NetCologne GmbH.
3516 This requires a properly setup MySQL user management and phpMyAdmin
3517 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3519 </p>
3523 access.
3524 </a></h4>
3525 <p>
3526 This depends on your system.<br />
3527 If you're running a server which cannot be accessed by other people, it's
3528 sufficient to use the directory protection bundled with your webserver
3530 If other people have telnet access to your server, you should use
3531 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3532 <br /><br />
3533 Suggestions:
3534 </p>
3535 <ul>
3536 <li>
3538 </li>
3539 <li>
3540 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3541 is a user whose password is only known to you, and apache is the
3542 group under which Apache runs.
3543 </li>
3544 <li>
3545 You should use PHP safe mode, to protect from other users that try
3547 </li>
3548 </ul>
3553 </a></h4>
3554 <p>
3559 </p>
3562 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3563 authentication.
3564 </a></h4>
3568 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3569 and/or
3571 are wrong.</li>
3573 <li>You have already setup a security mechanism for the
3574 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3575 phpMyAdmin's authentication, so remove it.</li>
3576 </ul>
3583 and put the privileges you want. For example,
3585 would let a user create/manage his/her database(s).</p>
3590 <p> If you have existing rules from an old .htaccess file, you can take them
3593 be a major benefit here if your installation is suited to using it. Then
3594 you can just add those updated lines into the
3598 <p> If you want a pre-made sample, you can try this fragment. It stops the
3599 'root' user from logging in from any networks other than the private
3602 <pre>
3603 //block root from logging in except from the private networks
3604 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3605 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3606 'deny root from all',
3607 'allow root from localhost',
3611 );
3612 </pre>
3617 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3618 different than the one set in your
3620 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3621 while a domain name is defined in the config file.</p>
3626 <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>
3632 when trying to create a table with more than 14 fields.
3633 </a></h4>
3634 <p>
3635 We could reproduce this problem only under Win98/98SE. Testing under
3636 WinNT4 or Win2K, we could easily create more than 60 fields.
3637 <br />
3638 A workaround is to create a smaller number of fields, then come back to
3639 your table properties and add the other fields.
3640 </p>
3644 <p>
3645 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3646 with each script/website that use forms.<br />
3647 Upgrade or downgrade your Xitami server.
3648 </p>
3651 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3652 <p>
3653 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3654 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3655 don't seem to work.<br />
3657 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3658 the user's temporary directory, so they must be moved before closing
3659 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3662 </p>
3666 Explorer never stores the cookies.
3667 </a></h4>
3668 <p>
3669 MS Internet Explorer seems to be really buggy about cookies, at least till
3670 version 6.
3671 </p>
3675 rows.
3676 </a></h4>
3677 <p>
3679 </p>
3682 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3683 when trying to modify a row in a table with many fields, or with a text field
3684 </a></h4>
3685 <p>
3686 Your table neither have a primary key nor an unique one, so we must use a
3687 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
3688 those browsers, and this not happen in Netscape, for example. The
3689 workaround is to create a primary or unique key, or use another browser.
3690 <br />
3691 </p>
3695 page.
3696 </a></h4>
3697 <p>
3698 Some browsers support right-clicking into the frame you want to refresh,
3699 just do this in the right frame.<br />
3700 </p>
3704 query box.
3705 </a></h4>
3706 <p>
3707 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3708 Mozilla versions.<br />
3709 </p>
3713 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3714 </a></h4>
3715 <p>
3716 This is a Mozilla bug (see bug #26882 at
3718 </p>
3723 </a></h4>
3724 <p>
3725 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3726 data in octet-stream mode. Since we can't detect the specific Netscape
3727 version, we cannot workaround this bug.
3728 </p>
3732 wrong.</a></h4>
3734 <p> Please ensure that you have set your browser's character set to the one of the
3735 language file you have selected on phpMyAdmin's start page.
3736 Alternatively, you can try the auto detection mode that is supported by the
3737 recent versions of the most browsers.</p>
3740 <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
3743 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3744 Netscape and Mozilla do not have this problem.</p>
3747 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3748 I cannot manage two servers: I log in to the first one, then the other one,
3749 but if I switch back to the first, I have to log in on each operation.</a></h4>
3755 but nothing happens after that, only a blank screen.</a></h4>
3766 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3771 address and you are starting
3773 containing a domain name, or the reverse situation.</li>
3774 <li>Security settings in IE and/or Microsoft Security Center are
3775 too high, thus blocking scripts execution.</li>
3776 <li>The Windows Firewall is blocking Apache and MySQL. You must
3780 </ul>
3783 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3784 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3785 installed in their Firefox is causing the problem.</p>
3789 clause is generated when I browse a table.</a></h4>
3790 <p> This happens only when both of these conditions are met: using the
3800 </a></h4>
3801 <p>
3802 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3803 specifying a wrong field-type.<br />
3804 Common errors include:
3805 </p>
3806 <ul>
3809 </ul>
3810 <p>
3811 Also, look at the syntax chapter in the MySQL manual to confirm that your
3812 syntax is correct.
3813 </p>
3817 phpMyAdmin generates only one index with those two fields.
3818 </a></h4>
3819 <p>
3820 This is the way to create a multi-fields
3821 index. If you want two indexes, create the first one when creating the
3822 table, save, then display the table properties and click the Index link to
3823 create the other index.
3824 </p>
3828 <p>
3829 Since version 2.2.3, you have a checkbox for each field that can be null.
3831 field's value. Since version 2.5.5, you have to use the checkbox to get
3833 a literal NULL in the field, and not a NULL value (this works in PHP4).
3834 </p>
3839 <p> Click on a database or table name in the left frame, the properties will be
3841 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3842 statements that can be used to recreate your database/table.
3843 <br /><br />
3845 transmit the resulting dump to your station. Depending on your PHP
3846 configuration, you will see options to compress the dump. See also the
3848 configuration variable.<br /><br />
3851 this document.</p>
3856 </a></h4>
3858 <p> Click on a database name in the left frame, the properties will be
3860 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3862 the path to your dump filename, or use the Browse button. Then click Go.
3863 <br /><br />
3865 that you upgrade to take advantage of the new features.
3866 <br /><br />
3868 in this document.
3869 </p>
3874 <p> Here is an example with the tables persons, towns and countries, all
3876 table, create it as explained in the configuration section. Then create the
3877 example tables:</p>
3879 <pre>
3880 CREATE TABLE REL_countries (
3881 country_code char(1) NOT NULL default '',
3882 description varchar(10) NOT NULL default '',
3883 PRIMARY KEY (country_code)
3884 ) TYPE=MyISAM;
3886 INSERT INTO REL_countries VALUES ('C', 'Canada');
3888 CREATE TABLE REL_persons (
3889 id tinyint(4) NOT NULL auto_increment,
3890 person_name varchar(32) NOT NULL default '',
3892 country_code char(1) NOT NULL default '',
3893 PRIMARY KEY (id)
3894 ) TYPE=MyISAM;
3896 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3897 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3899 CREATE TABLE REL_towns (
3901 description varchar(30) NOT NULL default '',
3902 PRIMARY KEY (town_code)
3903 ) TYPE=MyISAM;
3905 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3906 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3907 </pre>
3913 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3917 </ul>
3925 <li>In the fields row, choose persons.person_name and click the
3927 <li>Do the same for towns.description and countries.descriptions in the
3930 the correct joins have been generated</li>
3932 </ul>
3936 <p>
3937 Starting from the previous example, create the pma_table_info as explained
3938 in the configuration section, then browse your persons table,
3939 and move the mouse over a town code or country code.
3940 <br /><br />
3941 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3942 enables: drop-down list of possible values.
3943 </p>
3946 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3947 <p>
3950 <br /><br />
3951 Then you need to think about your schema layout. Which tables will go on
3952 which pages?
3953 </p>
3954 <ul>
3960 page and click Go. If you like, you
3962 linked tables onto the new page.</li>
3963 <li>Select the name of the new page (making sure the Edit radio button
3964 is selected) and click Go.</li>
3966 Coordinates are relative; your diagram will
3967 be automatically scaled to fit the page. When initially placing tables
3968 on the page, just pick any coordinates -- say, 50x50. After clicking
3970 position the element correctly.</li>
3972 first be sure to click the Save
3973 button beneath the list of tables and coordinates, to save any changes
3974 you made there. Then scroll all the way down, select the
3976 you want, and click Go.</li>
3977 <li>Internet Explorer for Windows may suggest an incorrect filename when
3982 browsers on Windows, do not have this problem.</li>
3983 </ul>
3987 columns!</a></h4>
3989 <p> No, it's MySQL that is doing
3995 underscores in the database name?</a></h4>
3997 <p> If you do not put a backslash before the underscore, this is a wildcard
4000 john2db ...<br /><br />
4002 If you put a backslash before the underscore, it means that the database
4003 name will have a real underscore.</p>
4007 statistics pages?</a></h4>
4018 if it already exists during the import. It does NOT drop the table after
4019 your export, it only affects the import file.</li>
4021 Otherwise, you may get an error if the table name exists but has a
4022 different structure.</li>
4024 (if any) will be included in backup.</li>
4026 field and table names formed with special characters are protected.</li>
4028 types set in the pmadb in the dump as
4030 </li>
4031 </ul>
4036 command, for better documentation (but resulting file is bigger).</li>
4038 once the INSERT verb and the table name.</li>
4041 </li>
4043 more info is provided in the
4045 but basically with this selected, invalid values are adjusted and
4046 inserted rather than causing the entire statement to fail.</li>
4047 </ul>
4051 in its name.</a></h4>
4054 is the normal way to reference a database and table name. Worse, MySQL
4055 will usually let you create a database with a dot, but then you cannot
4056 work with it, nor delete it.</p>
4069 for usage.<br />
4070 On a more recent pear version, I had problems with the state of Net_DIME
4071 being beta, so this single command
4073 needed modules.<br />
4074 If you use the Validator, you should be aware that any
4076 submit will be stored anonymously (database/table/column names,
4077 strings, numbers replaced with generic values). The Mimer
4080 We utilize it as free SOAP service.</p>
4084 it, but MySQL says "BLOB column '...' used in key specification without
4087 <p> The right way to do this, is to create the field without any indexes,
4089 dialog. On this page, you will be able to choose your BLOB field, and
4090 set a size to the index, which is the condition to create an index on
4091 a BLOB field.</p>
4095 editing fields?</a></h4>
4097 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4098 with many editing fields (table structure changes, row editing, etc.)
4099 (must be enabled in configuration - see.
4101 You can also have a look at the directive
4103 ('vertical') and see if this eases up editing for you.</p>
4107 WTF is this feature then useful for?</a></h4>
4109 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4110 on them. Otherwise you could just put a comment on the field. Because entering
4111 your own mimetype will cause serious syntax checking issues and validation,
4112 this introduces a high-risk false-user-input situation. Instead you have to
4113 initialize mimetypes using functions or empty mimetype definitions.<br />
4114 Plus, you have a whole overview of available mimetypes. Who knows all those
4115 mimetypes by heart so he/she can enter it at will?</p>
4119 can't I see any bookmarks below the query box? What is this variable for?
4120 </a></h4>
4122 <p> Any query you have executed can be stored as a bookmark on the page where the
4123 results are displayed. You will find a button labeled 'Bookmark this query'
4124 just at the end of the page.<br />
4125 As soon as you have stored a bookmark, it is related to the database you run
4126 the query on. You can now access a bookmark dropdown on each page, the query
4127 box appears on for that database.<br /><br />
4129 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4133 aware of that you HAVE to create a valid query, otherwise your query won't be
4134 even able to be stored in the database.<br />
4136 for your query will remain the way it is, but will be stripped of the /**/
4137 chars. So you can use:<br /><br />
4141 which will be expanded to<br /><br />
4145 in your query, where VARIABLE is the string you entered in the input box. If
4146 an empty string is provided, no replacements are made.<br /><br />
4148 A more complex example. Say you have stored this query:<br /><br />
4150 <br /><br />
4153 the full query will be:<br /><br />
4156 <br /><br />
4160 spaces inserted there
4161 will be later also inserted as spaces in your query and may lead to unexpected
4162 results especially when
4164 Your initial query which is going to be stored as a bookmark has to yield at
4165 least one result row so
4166 you can store the bookmark. You may have that to work around using well
4170 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4171 include exported table?</a></h4>
4173 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4174 document should look like following one (assuming you have table
4177 <pre>
4178 \documentclass{article} % or any class you want
4179 \usepackage{longtable} % for displaying table
4180 \begin{document} % start of document
4181 \include{table} % including exported table
4182 \end{document} % end of document
4183 </pre>
4187 access them.
4188 </a></h4>
4190 <p> You have one of these global privileges: CREATE
4191 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4192 enable users to see all the database names.
4195 So if your users do not need those privileges, you can remove them and their
4196 databases list will shorten.</p>
4200 possible values for a field, based on some foreign table?</a></h4>
4202 <p> You have to setup appropriate links between the tables, and also
4206 foreign table, a drop-down list of values will be available.
4207 You will see two lists of values, the first list containing the key
4208 and the display field, the second list containing the display field
4209 and the key. The reason for this is to be able to type the first
4210 letter of either the key or the display field.<br /><br />
4212 For 100 values or more, a distinct window will appear, to browse foreign
4213 key values and choose one. To change the default limit of 100, see
4214 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4218 automatically when entering Browse mode for a table?</a></h4>
4220 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4221 </p>
4225 Excel files, how can I enable that?</a></h4>
4227 <p> You can use
4229 which works out of the box, but phpMyAdmin supports direct export
4230 to Microsoft Excel version 97 and newer. For this to work, you need to set
4235 <pre>
4236 cd phpMyAdmin
4237 mkdir tmp
4238 chmod o+rwx tmp
4239 </pre>
4243 what happens to my column comments stored in pmadb?</a></h4>
4245 <p> Automatic migration of a table's pmadb-style column comments to the native
4246 ones is done whenever you enter Structure page for this table.</p>
4251 <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. Moreover, only PBMS 0.5.04 is supported.</p>
4253 <ol>
4254 <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>
4255 <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>
4256 <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>
4257 <li>Ensure that your target table is under the PBXT storage engine and has a LONGBLOB column.</li>
4258 <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>
4259 <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>
4260 </ol>
4265 <p> Click the first row of the range, hold the shift key and click the last row of the range. This works everywhere you see rows, for example in Browse mode or on the Structure page.</p>
4273 <p> Our Bug Tracker is located at
4275 under the Bugs section.<br /><br />
4277 But please first discuss your bug with other users:<br />
4283 existing language, where do I start?</a></h4>
4285 <p> Always use the current SVN version of your language file.
4287 don't know how to get the SVN version, please ask one of the developers.
4288 <br />
4289 Please note that we try not to use HTML entities like &eacute; in
4290 the translations, since we define the right character set in the file.
4291 With HTML entities, the text on JavaScript messages would not
4292 display correctly.
4293 However there are some entities that need to be there, for quotes
4294 ,non-breakable spaces, ampersands, less than, greater than.<br />
4295 You can then put your translations, as a zip file to avoid losing special
4296 characters, on the sourceforge.net translation tracker.<br />
4297 It would be a good idea to subscribe to the phpmyadmin-translators mailing
4298 list, because this is where we ask for translations of new messages.</p>
4302 phpMyAdmin. How should I proceed?</a></h4>
4307 <tt>git clone
4308 git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin</tt><br />
4309 </li>
4311 <li>generate patch with your changes:
4313 </li>
4316 tracker of the phpMyAdmin project</a>.
4317 </li>
4318 </ol>
4320 <p>More details on git are available on <a href="http://wiki.phpmyadmin.net/pma/Devel:Git">our wiki</a>.</p>
4322 <p> Write access to the repository is granted only to experienced developers who
4323 have already contributed something useful to phpMyAdmin.<br />
4329 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4331 <p> Please refer to
4332 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4333 </p>
4338 <p> If you use Apache web server, phpMyAdmin exports information about
4339 authentication to Apache environment and it can be used in Apache logs.
4340 Currently there are two variables available:
4341 </p>
4342 <dl>
4344 <dd>User name of currently active user (he does not have to be logged
4345 in).</dd>
4352 </dl>
4353 <p>
4355 </p>
4356 <pre>
4359 </pre>
4360 <p>
4361 You can then use any log analyzing tools to detect possible break-in
4362 attempts.
4363 </p>
4369 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4370 It allows you to connect to local as well as remote servers.This requires you to enter
4371 server host name, username, password, port and the name of the database. Therefore you can
4372 now synchronize your databases placed on the same server or some remote server.
4373 </p>
4375 <p>For more details see <a href="./documentation-gsoc/Synchronization_User_Manual.htm">How to synchronize</a>
4376 </p>
4378 <!-- DEVELOPERS -->
4381 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4382 great features have been written by other people and you too can help to
4383 make phpMyAdmin a useful tool.</p>
4385 <p> If you're planning to contribute source, please read the following
4386 information:</p>
4392 it free from other code.<br />
4393 Commonly used functions should be added to
4396 <li>Obviously, you're free to use whatever coding style you want. But
4397 please try to keep your code as simple as possible: beginners are
4398 using phpMyAdmin as an example application.<br />
4399 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4400 compliant on one hand, they fit the
4403 coding standards</a>
4404 on the other hand. Please pay attention to this.</li>
4405 <li>Please enable showing PHP errors and warnings by the
4407 configuration directive.</li>
4408 <li>Please try to keep up the file-naming conventions. Table-related stuff
4411 <li>Please don't put message strings in your code, instead add the string
4416 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4417 better debug and profile their code.<br />
4418 Please see the
4420 options for more information.<br />
4421 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4422 lost during its re-entry into Earth's atmosphere and in memory of the
4423 brave men and women who gave their lives for the people of Earth.</li>
4424 </ul>
4428 <pre>
4439 </pre>
4441 <p>
4442 This program is free software; you can redistribute it and/or modify
4443 it under the terms of the GNU General Public License version 2,
4444 as published by the Free Software Foundation.
4445 </p>
4447 <p>
4448 This program is distributed in the hope that it will be useful,
4449 but WITHOUT ANY WARRANTY; without even the implied warranty of
4450 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4451 GNU General Public License for more details.
4452 </p>
4454 <p>
4455 You should have received a copy of the GNU General Public License
4456 along with this program; if not, write to the Free Software
4458 </p>
4460 <!-- CREDITS -->
4465 <ul>
4468 <ul>
4471 </ul></li>
4474 <ul>
4479 </ul></li>
4482 <ul>
4488 </ul></li>
4491 <ul>
4493 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4494 generate XHTML1.0 and CSS2 compliant codes</li>
4497 </ul></li>
4500 <ul>
4508 </ul></li>
4511 <ul>
4516 </ul></li>
4519 <ul>
4522 </ul></li>
4525 <ul>
4527 </ul></li>
4530 <ul>
4533 </ul></li>
4536 <ul>
4540 </ul></li>
4543 <ul>
4546 </ul></li>
4549 <ul>
4556 </ul></li>
4559 <ul>
4563 </ul></li>
4566 <ul>
4572 </ul></li>
4575 (http://sf.net/projects/phpmysqlformgen/)
4576 <ul>
4578 </ul></li>
4581 <ul>
4583 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4588 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4592 </ul></li>
4595 <ul>
4597 </ul></li>
4600 <ul>
4602 </ul></li>
4605 <ul>
4607 </ul></li>
4610 <ul>
4611 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4612 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4613 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4614 </ul></li>
4617 <ul>
4619 </ul></li>
4622 <ul>
4624 </ul></li>
4627 <ul>
4629 </ul></li>
4632 <ul>
4635 </ul></li>
4638 <ul>
4641 </ul></li>
4644 <ul>
4646 </ul></li>
4649 <ul>
4652 </ul></li>
4654 <li>Ivan A Kirillov
4655 <ul>
4657 </ul></li>
4660 <ul>
4662 </ul></li>
4665 <ul>
4667 </ul></li>
4670 <ul>
4672 </ul></li>
4675 <ul>
4677 </ul></li>
4680 <ul>
4682 </ul></li>
4685 <ul>
4687 </ul></li>
4689 </ul>
4691 <p>
4692 And also to the following people who have contributed minor changes,
4693 enhancements, bugfixes or support for a new language since version 2.1.0:
4694 </p>
4696 <p>
4697 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4698 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4699 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4700 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4702 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4703 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4704 Luís V., Martijn W. van der Lee,
4705 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4707 </p>
4712 <p>
4713 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4714 to create a web-based interface to MySQL using PHP3. Although I have not
4715 used any of his source-code, there are some concepts I've borrowed from
4716 him. phpMyAdmin was created because Peter told me he wasn't going to
4717 further develop his (great) tool.
4718 </p>
4719 <p>
4720 Thanks go to
4721 </p>
4722 <ul>
4724 code for the check when dropping a table or database. He also suggested
4725 that you should be able to specify the primary key on tbl_create.php3. To
4726 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4727 well as a bug-report. Plus many smaller improvements.
4728 </li>
4730 were introduced in 1.3.0 (including quite significant ones like the
4731 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4732 bug-fixes and help.
4733 </li>
4735 language-independent by outsourcing the strings to a separate file. He
4736 also contributed the French translation.
4737 </li>
4739 tbl_select.php3, a feature to display only some fields from a table.
4740 </li>
4742 functions in tbl_change.php3. He also added the
4744 </li>
4746 servers and is a regular contributor for bug-fixes.
4747 </li>
4749 features for 2.0.6.
4750 </li>
4751 </ul>
4752 <p>
4753 The following people have contributed minor changes, enhancements, bugfixes
4754 or support for a new language:
4755 </p>
4756 <p>
4757 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4758 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4759 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4760 G. Wieggers.
4761 </p>
4762 <p>
4763 And thanks to everyone else who sent me email with suggestions, bug-reports
4764 and or just some feedback.
4765 </p>
4771 <ul>
4773 - the default name of Apache's directory-level configuration file.</li>
4777 - a software application that enables a user to display and interact with
4778 text, images, and other information typically located on a web page at a
4779 website on the World Wide Web.</li>
4781 - a free software/open source data compression algorithm and program
4782 developed by Julian Seward.</li>
4784 - an important World Wide Web technology that enables a client web browser
4785 to request data from a program executed on the Web server.</li>
4787 - a log or record of changes made to a project.</li>
4789 - a computer system that accesses a (remote) service on another computer
4790 by some kind of network.</li>
4792 - a set of data values of a particular simple type, one for each row of
4793 the table.</li>
4795 - a packet of information sent by a server to a World Wide Web browser
4796 and then sent back by the browser each time it accesses that server.</li>
4798 - Comma-separated values</li>
4801 - an organized collection of data.</li>
4804 - a PHP module that extends PHP with additional functionality.</li>
4806 - a list of commonly asked question and there answers.</li>
4808 - one part of divided data/columns.</li>
4810 - a field or group of fields in a database record that point to a key
4811 field or group of fields forming a key of another database record in some
4812 (usually different) table.</li>
4814 - the free PDF library</li>
4816 GD Graphics Library</a> - a library by Thomas Boutell and others for
4817 dynamically manipulating images.</li>
4820 - gzip is short for GNU zip, a GNU free software file compression
4821 program.</li>
4823 - any machine connected to a computer network, a node that has a hostname.</li>
4825 - the unique name by which a network attached device is known on a network.</li>
4827 (HyperText Transfer Protocol)</a>
4828 - the primary method used to transfer or convey information on the World
4829 Wide Web.</li>
4832 additional security measures.</li>
4833 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4834 - a set of Internet-based services for servers using Microsoft Windows.</li>
4836 - a feature that allows quick access to the rows in a table.</li>
4838 - a data-oriented protocol used by source and destination hosts for
4839 communicating data across a packet-switched internetwork.</li>
4841 - a unique number that devices use in order to identify and communicate
4842 with each other on a network utilizing the Internet Protocol standard.</li>
4844 (Internet Server Application Programming Interface)</a>
4845 - the API of Internet Information Services (IIS).</li>
4847 - a business or organization that offers users access to the Internet and related services.</li>
4849 - a most commonly used standard method of lossy compression for
4850 photographic images.</li>
4856 - line of personal computers is designed, developed, manufactured, and
4857 marketed by Apple Computer.</li>
4858 <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>
4859 - the operating system which is included with all currently shipping Apple
4860 Macintosh computers in the consumer and professional markets.</li>
4862 - a cryptographic library.</li>
4864 - the MCrypt PHP extension.</li>
4865 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4866 - an Internet Standard for the format of e-mail.</li>
4868 - some sort of extension for the Apache Webserver.</li>
4870 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4871 Management System (DBMS).</li>
4873 - the improved MySQL client PHP extension.</li>
4875 - the MySQL client PHP extension.</li>
4877 - open standard for office documents.</li>
4878 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4879 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4881 (Portable Document Format)</a>
4882 - a file format developed by Adobe Systems for representing two
4883 dimensional documents in a device independent and resolution independent
4884 format.</li>
4886 - the PHP Extension and Application Repository.</li>
4888 - the perl-compatible regular expression functions for PHP</li>
4890 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4891 programming language used mainly for developing server-side applications
4892 and dynamic web content, and more recently, a broader range of software
4893 applications.</li>
4895 - a connection through which data is sent and received.</li>
4897 - Request for Comments (RFC) documents are a series of memoranda
4898 encompassing new research, innovations, and methodologies applicable to
4899 Internet technologies.</li>
4903 - represents a single, implicitly structured data item in a table.</li>
4905 - a computer system that provides services to other computing
4906 systems over a network.</li>
4907 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/en/storage-engines.html">Storage Engines</a>
4908 - handlers for different table types</li>
4910 - a form of inter-process communication.</li>
4912 Sockets Layer)</a>
4913 - a cryptographic protocol which provides secure communication on the Internet.</li>
4915 - Structured Query Language</li>
4917 - a set of data elements (cells) that is organized, defined and stored as
4918 horizontal rows and vertical columns where each item can be uniquely
4919 identified by a label or key or by it?s position in relation to other items.</li>
4922 - a type of archive file format: the Tape ARchive format.</li>
4924 - one of the core protocols of the Internet protocol suite.</li>
4928 - a sequence of characters, conforming to a standardized format, that is
4929 used for referring to resources, such as documents and images on the
4930 Internet, by their location.</li>
4932 - A computer (program) that is responsible for accepting HTTP requests
4933 from clients and serving them Web pages.</li>
4935 - a W3C-recommended general-purpose markup language for creating
4936 special-purpose markup languages, capable of describing many different
4937 kinds of data.</li>
4939 - a popular data compression and archival format.</li>
4941 - an open-source, cross-platform data compression library by Jean-loup
4942 Gailly and Mark Adler.</li>
4943 </ul>
4944 </div>
4947 <li>Copyright © 2003 - 2010 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
4950 <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>
4951 </ul>
4953 </body>
4954 </html>