| blob | ab7ae2752931ec2547e9421d68f1c4eafcfe43ba |
3 <!--
4 vim: expandtab ts=4 sw=4 sts=4 tw=78
5 -->
8 <!-- $Id$ -->
9 <head>
15 </head>
19 <h1>
21 3.3.8-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>
58 </li>
59 </ul>
61 <!-- REQUIREMENTS -->
68 and the Standard PHP Library (SPL) extension.
69 </li>
72 currently default), you should install mbstring and ctype
73 extensions.
74 </li>
75 <li>You need GD2 support in PHP to display inline
77 original aspect ratio</li>
83 load pages significantly slower.
84 </li>
87 </ul>
88 </li>
91 </ul>
93 <!-- INTRODUCTION -->
96 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
97 a single database. To accomplish the latter you'll need a properly set up
98 MySQL user who can read/write only the desired database. It's up to you to
99 look up the appropriate part in the MySQL manual.
100 </p>
105 <li>create, copy, drop, rename and alter databases, tables, fields and
106 indexes</li>
107 <li>maintenance server, databases and tables, with proposals on server
108 configuration</li>
109 <li>execute, edit and bookmark any
111 batch-queries</li>
114 </li>
121 OpenDocument Text and Spreadsheet,
123 <abbr title="Microsoft Excel 97-2003 and Excel 2007">Excel</abbr> and L<sup>A</sup>T<sub><big>E</big></sub>X formats
124 </li>
125 <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>
129 <li>using Query-by-example (QBE), create complex queries automatically
130 connecting required tables</li>
132 your Database layout</li>
134 <li>transform stored data into any format using a set of predefined
135 functions, like displaying BLOB-data as image or download-link
136 </li>
143 </li>
144 <li>synchronize two databases residing on the same as well as remote servers
146 </li>
148 </ul>
151 <p> Many people have difficulty
152 understanding the concept of user management with regards to phpMyAdmin. When
153 a user logs in to phpMyAdmin, that username and password are passed directly
154 to MySQL. phpMyAdmin does no account management on its own (other than
155 allowing one to manipulate the MySQL user account information); all users
156 must be valid MySQL users.</p>
165 <!-- INSTALLATION -->
173 </ol>
176 phpMyAdmin does not apply any special security methods to the MySQL database
177 server. It is still the system administrator's job to grant permissions on
179 be used for this.
180 </p>
188 So you'll have to resave as in BBEdit to Unix style ALL phpMyAdmin scripts
189 before uploading them to your server, as PHP seems not to like
194 <ol><li>Choose an appropriate distribution kit from the phpmyadmin.net
195 Downloads page. Some kits contain only the English messages,
196 others contain all languages in UTF-8 format (this should be fine
197 in most situations), others contain all
198 languages and all character sets. We'll assume you chose a kit whose
200 </li>
201 <li>Untar or unzip the distribution (be sure to unzip the subdirectories):
203 document root. If you don't have direct access to your document root,
204 put the files in a directory on your local machine, and, after step 4,
205 transfer the directory on your web server using, for example, ftp.</li>
206 <li>Ensure that all the scripts have the appropriate owner (if PHP is
207 running in safe mode, having some scripts with an owner different
208 from the owner of other scripts will be a
213 <li>Now you must configure your installation. There are two methods that
214 can be used. Traditionally, users have hand-edited a copy of
216 provided for those who prefer a graphical installation. Creating a
217 <tt>config.inc.php</tt> is still a quick way to get started and needed for some advanced features.
218 <ul><li>To manually create the file, simply use your text editor to
221 file) in the main (top-level) phpMyAdmin directory (the one
225 default value is okay for a particular setting, there is no
227 few directives to get going, a simple configuration may look
228 like this:
229 <pre>
230 <?php
231 $cfg['blowfish_secret'] = 'ba17c1ec07d65003'; // use here a value of your choice
233 $i=0;
234 $i++;
235 $cfg['Servers'][$i]['auth_type'] = 'cookie';
236 ?>
237 </pre>
238 Or, if you prefer to not be prompted every time you log in:
239 <pre>
240 <?php
242 $i=0;
243 $i++;
244 $cfg['Servers'][$i]['user'] = 'root';
245 $cfg['Servers'][$i]['password'] = 'cbb74bc'; // use here your password
246 $cfg['Servers'][$i]['auth_type'] = 'config';
247 ?>
248 </pre>
249 For a full explanation of possible configuration values, see the
255 directory. This is a security measure. On a Linux/Unix system you
256 can use the following commands:
257 <pre>
258 cd phpMyAdmin
259 mkdir config # create directory for saving
260 chmod o+rw config # give it world writable permissions
261 </pre>
262 And to edit an existing configuration, copy it over first:
263 <pre>
264 cp config.inc.php config/ # copy current configuration for editing
265 chmod o+w config/config.inc.php # give it world writable permissions
266 </pre>
267 On other platforms, simply create the folder and ensure that your
276 the webserver does not have the proper permissions you may see the
278 config/</tt> directory exists and has the proper permissions -
280 and upload (via FTP or some similar means) to the proper location.<br /><br />
282 Once the file has been saved, it must be moved out of the <tt>
283 config/</tt> directory and the permissions must be reset, again
284 as a security measure:
285 <pre>
286 mv config/config.inc.php . # move file to current directory
287 chmod o-rw config.inc.php # remove world read and write permissions
288 rm -rf config # remove not needed directory
289 </pre>
290 Now the file is ready to be used. You can choose to review or edit
291 the file with your favorite editor, if you prefer to set some
292 advanced options which the setup script does not provide.</li></ul></li>
293 <li>If you are using the
295 protect the phpMyAdmin installation directory because using
296 config does not require a user to
297 enter a password to access the phpMyAdmin installation. Use of an alternate
298 authentication method is recommended, for example with
306 in your browser. phpMyAdmin should now display a welcome screen
307 and your databases, or a login dialog if using
309 authentication mode.</li>
312 Apache you can use supplied .htaccess file in that folder, for other
313 webservers, you should configure this yourself. Such configuration
314 prevents from possible path exposure and cross side scripting
315 vulnerabilities that might happen to be found in that code.</li>
316 <li>
317 It is generally good idea to protect public phpMyAdmin installation
318 against access by robots as they usually can not do anything good
320 your webserver or limit access by web server configuration. You can
323 </li>
324 </ol>
328 <p> For a whole set of new features (bookmarks, comments,
330 tracking mechanism,
332 transformation, etc.) you need to create a set of special tables. Those
333 tables can be located in your own database, or in a central database for a
334 multi-user installation (this database would then be accessed by the
335 controluser, so no other user should have rights to it).</p>
345 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
346 that you may need special (administrator) privileges to create the database
347 and tables, and that the script may need some tuning, depending on the
348 database name.</p>
353 section</a>. You will also need to have a controluser with the proper rights
360 unpacked one. Configuration files from old versions may
361 require some tweaking as some options have been changed or removed; in
363 so you better remove it from your file and just use the default one.
365 statement that you might find near the end of your configuration file.</p>
369 is version-specific.</p>
372 version 5.x or newer and if you use the pmadb/linked table infrastructure,
373 you should run the SQL script found in
380 where you want to give users access to their own database and don't want
381 them to play around with others.<br />
382 Nevertheless be aware that MS Internet Explorer seems to be really buggy
386 that your user/password pair are not in clear in the configuration file.
387 </li>
390 authentication modes are more secure: the MySQL login information does
391 not need to be set in the phpMyAdmin configuration file (except possibly
393 However, keep in mind that the password travels in plain text, unless
394 you are using the HTTPS protocol.<br />
395 In cookie mode, the password is stored, encrypted with the blowfish
396 algorithm, in a temporary cookie.</li>
398 <li>Note: this section is only applicable if
408 file under the
410 $cfg['Servers'][$i]['controluser']</a></tt> and
415 only an example: use something else in your file!</b> Input these
416 statements from the phpMyAdmin SQL Query window or mysql command–line
417 client.<br />
419 if it's not the same as the MySQL server's one.
421 <pre>
422 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
423 GRANT SELECT (
424 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
425 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
426 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
427 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
428 Execute_priv, Repl_slave_priv, Repl_client_priv
429 ) ON mysql.user TO 'pma'@'localhost';
430 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
431 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
432 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
433 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
435 If you want to use the many new relation and bookmark features:
437 <pre>
439 </pre>
445 on a set of particular databases. Normally you shouldn't give global
446 privileges to an ordinary user, unless you understand the impact of those
447 privileges (for example, you are creating a superuser).<br />
451 <pre>
452 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
453 </pre>
455 What the user may now do is controlled entirely by the MySQL user
456 management system.<br />
458 authentication mode, you don't need to fill the user/password fields
460 array.</li>
461 </ul>
466 method and allows you to log in as any valid MySQL user.</li>
467 <li>Is supported with most PHP configurations. For
480 mode.</li>
481 </ul>
485 <ul><li>You can use this method as a replacement for the
487 (for example, if you're running
489 <li>Obviously, the user must enable cookies in the browser, but this is
490 now a requirement for all authentication modes.</li>
491 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
492 with the same username.</li>
493 <li>If you want to log in to arbitrary server see
498 not required.</li>
499 </ul>
503 <ul><li>This mode is a convenient way of using credentials from another
504 application to authenticate to phpMyAdmin.</li>
505 <li>The other application has to store login information into
506 session data.</li>
508 section.</li>
509 </ul>
512 <ul><li>This mode is the less secure one because it requires you to fill the
514 $cfg['Servers'][$i]['user']</a> and
516 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
517 can read your config.inc.php can discover your username and password).
518 <br />
525 is an entry explaining how to protect your configuration file.</li>
526 <li>For additional security in this mode, you may wish to consider the Host
527 authentication
529 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
531 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
532 directives.</li>
533 <li>Unlike cookie and http, does not require a user to log in when first
534 loading the phpMyAdmin site. This is by design but could allow any
535 user to access your installation. Use of some restriction method is
537 HTTP-AUTH directive or disallowing incoming HTTP requests at
538 one’s router or firewall will suffice (both of which
539 are beyond the scope of this manual but easily searchable with Google).</li>
540 </ul>
542 <p>
543 The Swekey is a low cost authentication USB key that can be used in
544 web applications.<br /><br />
545 When Swekey authentication is activated, phpMyAdmin requires the
546 users's Swekey to be plugged before entering the login page (currently
547 supported for cookie authentication mode only). Swekey Authentication is
548 disabled by default.<br /><br />
550 </p>
551 <pre>
552 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
553 </pre>
554 <p>
556 each user with their Swekey Id. It is important to place this file outside
557 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
559 users' information.<br /><br />
560 If you want to purchase a Swekey please visit
562 since this link provides funding for phpMyAdmin.
563 </p>
564 <!-- CONFIGURATION -->
568 users:</span> PHP does not seem to like
572 before saving a script you have modified.</p>
577 section to create one. This file only needs to contain the parameters you want to
578 change from their corresponding default value in
581 <p> The parameters which relate to design (like colors) are placed in
584 your site specific code to be included on start and end of each page.</p>
588 (with full path) to your phpMyAdmin installation's directory.
591 some web servers are case–sensitive.
594 Starting with version 2.3.0, it is advisable to try leaving this
595 blank. In most cases phpMyAdmin automatically detects the proper
596 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
597 href="https://sourceforge.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
598 A good test is to browse a table, edit a row and save it. There should
599 be an error message if phpMyAdmin is having trouble auto–detecting
600 the correct value. If you get an error that this must be set or if
601 the autodetect code fails to detect your path, please post a bug
602 report on our bug tracker so we can improve the code.</dd>
606 with master / foreign – tables (see
608 <br />
609 If you tried to set this up and it does not work for you, have a look on
611 use it. You will find a link that will analyze why those features have
612 been disabled.<br />
613 If you do not want to use those features set this variable to
617 <dd>A warning is displayed on the main page if Suhosin is detected.
619 from appearing.</dd>
622 <dd>Disable the default warning that is displayed if mcrypt is missing for
623 cookie authentication.
625 from appearing.</dd>
629 domain to call phpMyAdmin inside a frame, and is a potential security
630 hole allowing cross-frame scripting attacks.</dd>
634 algorithm to encrypt the password.<br />
636 passphrase of your choice. It will be used internally by the blowfish
637 algorithm: you won’t be prompted for this passphrase. There is
638 no maximum length for this secret.<br /><br />
640 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
641 makes a bit weaker security as this generated secret is stored in
642 session and furthermore it makes impossible to recall user name from
643 cookie.</dd>
647 MySQL servers. Therefore, a
649 been added which contains the login information for the different servers.
650 The first
652 contains the hostname of the first server, the second
654 the hostname of the second server, etc. In
656 server definition, however you can put as many as you need in
658 have to define all settings, just those you need to change).</dd>
662 $i-th MySQL-server. E.g. localhost.</dd>
667 ignores this port number and connects with the socket, so if you want
668 to connect to a port different from the default port, use
671 </dd>
675 To determine the correct socket, check your MySQL configuration or, using the
677 Among the resulting information displayed will be the socket used.</dd>
680 <dd>Whether to enable SSL for connection to MySQL server.
681 </dd>
684 <dd>What type connection to use with the MySQL server. Your options are
686 is nearly guaranteed to be available on all MySQL servers, while
687 sockets are not supported on some platforms.<br /><br />
689 To use the socket mode, your MySQL server must be on the same machine
690 as the Web server.</dd>
693 <dd>What php MySQL extension to use for the connection. Valid options are:
694 <br /><br />
697 The classic MySQL extension. This is the recommended and default
698 method at this time.<br /><br />
701 The improved MySQL extension. This extension became available
702 with php 5.0.0 and is the recommended way to connect to a server
706 <dd>Whether to use a compressed protocol for the MySQL server connection
707 or not (experimental).<br />
713 </dt>
715 all relational features (see
717 and, for a MySQL server running with
720 authentication mode).<br /><br />
723 cookie authentication modes (or 'config'
724 authentication mode since phpMyAdmin 2.2.1), you need to supply the
729 This account is used to check what databases the user will see at
730 login.<br />
734 In phpMyAdmin versions before 2.2.5, those were called
738 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
739 <dd>Whether config or cookie or
741 should be used for this server.
743 is the plain old way: username and password are stored in
745 <li>'cookie' authentication mode
747 2.2.3 allows you to log in as any valid MySQL user with the
748 help of cookies. Username and password are stored in
749 cookies during the session and password is deleted when it
750 ends. This can also allow you to log in in arbitrary server if
751 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
752 </li>
753 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
754 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
755 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
756 <li>'signon' authentication mode
758 as introduced in 2.10.0 allows you to log in from prepared PHP
759 session data. This is useful for implementing single signon
760 from another application. Sample way how to seed session is in
766 </ul>
769 for more information.
770 </dd>
772 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
773 </dt>
774 <dd>
776 names for hardware authentication. Leave empty to deactivate this feature.
777 </dd>
781 </dt>
782 <dd>
783 When using auth_type = 'config', this is the user/password-pair
784 which phpMyAdmin will use to connect to the
785 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
786 cookie authentication is used and should be empty.</dd>
788 <span
790 </dt>
791 <dd>
792 Allow attempt to log in without password when a login with password
793 fails. This can be used together with http authentication, when
794 authentication is done some other way and phpMyAdmin gets user name
795 from auth and uses empty password for connecting to MySQL. Password
796 login is still tried first, but as fallback, no password method is
797 tried.</dd>
800 </dt>
801 <dd>
802 If set to a (an array of) database name(s), only this (these) database(s)
803 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
804 database(s) name(s) may contain MySQL wildcards characters
808 This setting is an efficient way to lower the server load since the
809 latter does not need to send MySQL requests to build the available
811 privileges rules of the MySQL database server</span>. If set, it just
812 means only these databases will be displayed but
814 <br /><br />
816 An example of using more that one database:
818 <br /><br />
820 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
821 databases in the left frame, so that you can individually arrange your databases.<br />
822 If you want to have certain databases at the top, but don't care about the others, you do not
823 need to specify all other databases. Use:
825 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
826 order.</dd>
829 </dt>
830 <dd>Regular expression for hiding some databases. This only hides them
831 from listing, but a user is still able to access them (using, for example,
832 the SQL query area). To limit access, use the MySQL privilege system.
833 <br /><br />
838 More information on regular expressions can be found in the
840 PCRE pattern syntax</a> portion of the PHP reference manual.
841 </dd>
844 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
845 this string will be displayed instead of the hostname in the pull-down
846 menu on the main page. This can be useful if you want to show only
847 certain databases on your system, for example. For HTTP auth, all
848 non-US-ASCII characters will be stripped.</dd>
852 </dt>
853 <dd>The name of the database containing the linked-tables infrastructure.
854 <br /><br />
857 section in this document to see the benefits of this infrastructure,
858 and for a quick way of creating this database and the needed tables.
859 <br /><br />
861 If you are the only user of this phpMyAdmin installation, you can
862 use your current database to store those special tables; in this
863 case, just put your current database name in
865 set this parameter to the name of your central database containing
866 the linked-tables infrastructure.</dd>
870 </dt>
872 useful for queries you often run.<br /><br />
874 To allow the usage of this functionality:
876 <li>enter the table name in
878 </ul>
879 </dd>
883 </dt>
885 which field is a key in another table (a foreign key). phpMyAdmin
886 currently uses this to
887 <ul><li>make clickable, when you browse the master table, the data values
888 that point to the foreign table;</li>
890 when browsing the master table, if you move the mouse to a column
891 containing a foreign key (use also the 'table_info' table);<br />
894 <li>in edit/insert mode, display a drop-down list of possible foreign
898 <li>display links on the table properties page, to check referential
899 integrity (display missing foreign keys) for each described key;
900 </li>
904 schema of your database (also uses the table_coords table).</li>
905 </ul>
907 The keys can be numeric or character.<br /><br />
909 To allow the usage of this functionality:
912 infrastructure</li>
913 <li>put the relation table name in
915 <li>now as normal user open phpMyAdmin and for each one of your
916 tables where you want to use this feature, click
918 </li>
919 </ul>
923 future development of the cross-db relations.
924 </dd>
928 </dt>
929 <dd>
930 Since release 2.3.0 you can describe, in a special 'table_info'
931 table, which field is to be displayed as a tool-tip when moving the
932 cursor over the corresponding key.<br />
933 This configuration variable will hold the name of this special
934 table. To allow the usage of this functionality:
936 <li>put the table name in
938 'pma_table_info')</li>
939 <li>then for each table where you want to use this feature,
941 to choose the field.</li>
942 </ul>
944 </dd>
948 </dt>
951 the relations between your tables. To do this it needs two tables
956 schema output).<br /><br />
960 To allow the usage of this functionality:
963 infrastructure</li>
964 <li>put the correct table names in
967 </ul>
970 </dd>
974 </dt>
976 Since release 2.3.0 you can store comments to describe each column for
978 <br /><br />
980 Starting with release 2.5.0, comments are consequently used on the table
981 property pages and table browse view, showing up as tool-tips above the
982 column name (properties page) or embedded within the header of table in
983 browse view. They can also be shown in a table dump. Please see the
984 relevant configuration directives later on.<br /><br />
986 Also new in release 2.5.0 is a MIME-transformation system which is also
988 Transformations</a> for further information. To use the
989 MIME-transformation system, your column_info table has to have the three
990 new fields 'mimetype', 'transformation', 'transformation_options'.
991 <br /><br />
993 To allow the usage of this functionality:
995 infrastructure</li>
996 <li>put the table name in
998 'pma_column_info')</li>
1001 <pre>
1002 ALTER TABLE `pma_column_comments`
1003 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1004 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1005 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1006 </pre>
1009 renamed from<br />
1012 </ul>
1013 </dd>
1017 </dt>
1020 all queries you entered manually into the phpMyAdmin interface. If you
1021 don't want to use a table-based history, you can use the JavaScript-based
1022 history. Using that, all your history items are deleted when closing the
1023 window.<br /><br />
1025 Using
1027 you can specify an amount of history items you want to have on hold. On
1028 every login, this list gets cut to the maximum amount.<br /><br />
1030 The query history is only available if JavaScript is enabled in your
1031 browser.<br /><br />
1033 To allow the usage of this functionality:
1036 infrastructure</li>
1038 (e.g. 'pma_history')
1039 </li>
1040 </ul>
1041 </dd>
1045 </dt>
1046 <dd>
1047 Since release 3.3.x a tracking mechanism is available.
1049 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1050 and data definition statements. After enabling it you can create versions of tables.
1051 <br/><br/>
1052 The creation of a version has two effects:
1054 <ul>
1056 <li>phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1057 </ul>
1059 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1060 For the report you can use filters, for example you can get a list of statements within a date range.
1061 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1062 In addition you can export the (filtered) report to a file or to a temporary database.
1063 <br/><br/>
1065 To allow the usage of this functionality:
1067 <ul>
1070 </ul>
1071 </dd>
1074 <span id="cfg_Servers_tracking_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1075 </dt>
1076 <dd>
1077 Whether the tracking mechanism creates versions for tables and views automatically. Default value is false.
1078 <br/><br/>
1079 If this is set to true and you create a table or view with
1081 <ul>
1084 </ul>
1086 and no version exists for it, the mechanism will
1087 create a version for you automatically.
1088 </dd>
1091 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1092 </dt>
1093 <dd>
1094 Defines the list of statements the auto-creation uses for new versions. Default value is
1095 <br/>
1097 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1098 CREATE INDEX,DROP INDEX,
1099 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1100 CREATE VIEW,ALTER VIEW,DROP VIEW,
1101 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1102 </dd>
1105 <span id="cfg_Servers_tracking_drop_view">$cfg['Servers'][$i]['tracking_version_drop_view']</span> boolean
1106 </dt>
1107 <dd>
1108 Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view. Default value is true.
1109 <br/><br/>
1110 </dd>
1114 <span id="cfg_Servers_tracking_drop_table">$cfg['Servers'][$i]['tracking_version_drop_table']</span> boolean
1115 </dt>
1116 <dd>
1117 Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table. Default value is true.
1118 <br/><br/>
1119 </dd>
1122 <span id="cfg_Servers_tracking_drop_database">$cfg['Servers'][$i]['tracking_version_drop_database']</span> boolean
1123 </dt>
1124 <dd>
1125 Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database. Default value is true.
1126 <br/><br/>
1127 </dd>
1132 </dt>
1134 to visually manage the relations.
1135 <br /><br />
1137 To allow the usage of this functionality:
1140 infrastructure</li>
1141 <li>put the table name in <tt>$cfg['Servers'][$i]['designer_coords']</tt> (e.g. 'pma_designer_coords')
1142 </li>
1143 </ul>
1144 </dd>
1147 </dt>
1149 column_info table got enhanced with three new fields. If the above variable
1151 latest table structure available. If not, it will emit a warning to the
1152 superuser.<br /><br />
1154 You can disable this checking behavior by setting the variable to false,
1155 which should offer a performance increase.<br /><br />
1157 Recommended to set to FALSE, when you are sure, your table structure is
1158 up to date.</dd>
1160 boolean</dt>
1161 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1162 </dd>
1164 boolean</dt>
1165 <dd>Whether to allow logins without a password. The default
1167 to a MySQL server with was left with an empty password for root or
1168 on which an anonymous (blank) user is defined.
1169 </dd>
1172 </dt>
1174 authentication is disabled.<br /><br />
1177 all deny rules followed by allow rules. Access is allowed by default. Any
1178 client which does not match a Deny command or does match an Allow command
1179 will be allowed access to the server. <br /><br />
1182 applies all allow rules followed by deny rules. Access is denied by
1183 default. Any client which does not match an Allow directive or does
1184 match a Deny directive will be denied access to the server.<br /><br />
1186 If your rule order is set to 'explicit', the authentication is
1187 performed in a similar fashion to rule order 'deny,allow', with the
1191 and was available in Apache by specifying allow and deny rules without
1192 setting any order.<br /><br />
1194 Please also see <a
1196 address behind proxies.
1197 </dd>
1199 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1200 </dt>
1201 <dd>The general format for the rules is as such:
1203 <pre>
1205 </pre>
1210 well (please note that those containing SERVER_ADDRESS might not be
1211 available on all webservers):
1212 <pre>
1218 </pre>
1220 Having an empty rule list is equivalent to either using
1226 following work:<br />
1228 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1229 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1230 But the following does not work:<br />
1233 Also IPv6 addresses are not supported.
1234 </dd>
1236 <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.
1237 </dd>
1238 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1240 DATABASES</tt> command used to fetch the name of available databases will
1241 probably be too slow, so it can be replaced by faster commands (see
1243 </dd>
1245 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1246 </dd>
1247 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1248 <dd>Name of session which will be used for signon authentication method.
1249 </dd>
1251 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1252 </dd>
1254 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1255 </dd>
1258 <dd>If you have more than one server configured, you can set
1260 that server when phpMyAdmin is started, or set it to 0 to be given a
1261 list of servers without logging in.<br />
1263 MUST be set to that server.</dd>
1266 <dd>The maximum number of database names to be displayed in the
1267 navigation frame and the database list.</dd>
1270 <dd>The maximum number of table names to be displayed in the
1271 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1272 when in Light mode.</dd>
1275 <dd>The maximum number of characters when a SQL query is displayed. The
1276 default limit of 1000 should be correct to avoid the display of tons
1277 of hexadecimal codes that represent BLOBs, but some users have real
1278 SQL queries that are longer than 1000 characters. Also, if a query's
1279 length exceeds this limit, this query is not saved in the history.</dd>
1282 <dd>Defines whether to use GZip output buffering for increased
1284 Set to true/false for enabling/disabling. When set to 'auto' (string),
1285 phpMyAdmin tries to enable output buffering and will automatically disable
1286 it if your browser has some problems with buffering. IE6 with a certain patch
1287 is known to cause data corruption when having enabled buffering.</dd>
1290 <dd>Whether persistent connections should be used or not (mysql_connect or
1291 mysql_pconnect).</dd>
1297 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1298 to zero, no time limit is imposed.<br />
1299 This setting is used while importing/exporting dump files and in the
1300 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1303 <dd>Set the number of bytes a script is allowed to allocate. If set
1304 to zero, no limit is imposed.<br />
1305 This setting is used while importing/exporting dump files and at some
1306 other places in phpMyAdmin so you definitely don't want to put here
1307 a too low value. It has no effect when PHP is running in safe mode.<br />
1308 You can also use any string as in php.ini, eg. '16M'. Ensure
1312 <dd>Mark used tables and make it possible to show databases with locked
1317 generated by phpMyAdmin should be displayed or not.</dd>
1320 <dd>Defines whether normal users (non-administrator) are allowed to
1321 delete their own database or not. If set as FALSE, the link "Drop
1323 mydatabase" will be rejected. Quite practical for
1325 customers.<br />
1326 Please note that this limitation of SQL queries is not as strict as
1327 when using MySQL privileges. This is due to nature of SQL queries
1328 which might be quite complicated. So this choice should be viewed as
1329 help to avoid accidental dropping rather than strict privilege
1330 limitation.</dd>
1334 displayed when you're about to lose data.</dd>
1337 <dd>Define whether the previous login should be recalled or not in cookie
1338 authentication mode.<br /><br />
1340 This is automatically disabled if you do not have configured
1342 </dd>
1345 <dd>Define how long is login cookie valid. Please note that php
1346 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1347 might limit session validity and if session is lost, login cookie is
1349 not lower than the value of $cfg['LoginCookieValidity'].</dd>
1353 means that it will be kept for existing session. This is recommended
1354 for not trusted environments.</dd>
1357 <dd>If enabled (default), logout deletes cookies for all servers,
1358 otherwise only for current one. Setting this to false makes it easy to
1359 forget to log out from other server, when you are using more of
1360 them.</dd>
1366 <dd>Define whether phpMyAdmin will continue executing a multi-query
1367 statement if one of the queries fails. Default is to abort execution.</dd>
1370 <dd>Define whether phpMyAdmin will output the results of each query of a
1371 multi-query statement embedded into the
1376 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1377 <br /><br />
1380 MySQL servers behind the firewall where your
1382 </dd>
1391 <dd>Defines whether to use a select-based menu and display only the current
1392 tables in the left frame (smaller page). Only in Non-Lightmode you can
1393 use the feature to display nested folders using
1395 </dd>
1398 <dd>In light mode, defines whether to display the names of databases (in the
1399 selector) using a tree, see also
1401 </dd>
1404 string or array</dt>
1405 <dd>The string used to separate the parts of the database name when showing
1406 them in a tree. Alternatively you can specify more strings in an array
1407 and all of them will be used as a separator.</dd>
1410 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1411 This means if you have tables like 'first__second__third' this will be
1413 If set to FALSE or empty, the feature is disabled. NOTE: You should
1414 not use this separator at the beginning or end of a
1415 table name or multiple times after another without any other
1416 characters in between.</dd>
1419 <dd>Defines how many sublevels should be displayed when splitting
1420 up tables by the above separator.</dd>
1423 <dd>Defines whether to display table comment as tool-tip in left frame or
1424 not.</dd>
1427 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1428 comment and the real name. That means that if you have a table called
1429 'user0001' and add the comment 'MyName' on it, you will see the name
1430 'MyName' used consequently in the left frame and the tool-tip shows
1431 the real name of the DB.</dd>
1434 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1436 When setting this to 'nested', the Alias of the Tablename is only used
1437 to split/nest the tables according to the
1439 directive. So only the folder is called like the Alias, the tablename itself
1440 stays the real tablename.</dd>
1443 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1446 <dd>Enter URL where logo in the navigation frame will point to.
1447 For use especially with self made theme which changes this.
1456 <dd>Defines whether or not to display a server choice at the top of the left frame.
1457 Defaults to FALSE.</dd>
1459 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1460 Defaults to FALSE (drop-down).</dd>
1462 <dd>Defines whether to display database choice in light navigation frame as links
1463 instead of in a drop-down. Defaults to 'auto' - on main page list is
1464 shown, when database is selected, only drop down is displayed.</dd>
1467 <dd>Defines the tab displayed by default when clicking the small
1468 icon next to each table name in the navigation panel. Possible
1474 <dd>Defines whether or not to display space usage and statistics about databases
1475 and tables.<br />
1476 Note that statistics requires at least MySQL 3.23.3 and that, at this
1477 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1480 <dd>Defines whether to display detailed server information on main page.
1481 You can additionally hide more information by using
1483 </dd>
1488 </dt>
1491 not at the starting main (right) frame. This setting
1492 does not check MySQL commands entered directly.<br /><br />
1494 Please note that to block the usage of phpinfo() in scripts, you
1501 hard coded password value in the configuration file, end users can't
1502 be allowed to change their passwords.</dd>
1505 <dd>Defines whether to suggest a database name on the
1509 <dd>Defines whether navigation bar buttons and the right panel top menu
1510 contain text or symbols only. A value of TRUE displays icons, FALSE
1511 displays text and 'both' displays both icons and text.</dd>
1514 <dd>Defines whether a user should be displayed a
1518 <dd>Number of rows displayed when browsing a result set. If the result set
1525 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1529 option is ticked by default.</dd>
1533 from editing when browsing a table's content. Valid values are:
1538 </ul>
1539 </dd>
1542 <dd>Defines whether or not MySQL functions fields should be initially
1543 displayed in edit/insert mode. Since version 2.10, the user can
1544 toggle this setting from the interface.
1545 </dd>
1548 <dd>Defines which type of editing controls should be used for CHAR and
1549 VARCHAR fields. Possible values are:
1550 <ul><li>input - this allows to limit size of text to size of field in
1551 MySQL, but has problems with newlines in fields</li>
1552 <li>textarea - no problems with newlines in fields, but also no
1553 length limitations</li>
1554 </ul>
1555 Default is old behavior so input.</dd>
1561 <dd>If there are fewer items than this in the set of foreign keys, then a
1562 drop-down box of foreign keys is presented, in the style described by the
1564 setting.</dd>
1567 <dd>For the foreign key drop-down fields, there are several methods of
1568 display, offering both the key and value data. The contents of the
1569 array should be one or both of the following strings:
1575 </dt>
1576 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1577 creating a dump file</dd>
1580 </dt>
1581 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1582 compressed exports. This doesn't affect smaller dumps and allows users to
1583 create larger dumps that won't otherwise fit in memory due to php
1584 memory limit. Produced files contain more GZip/BZip2 headers, but all
1585 normal programs handle this correctly.</dd>
1589 mainframe.</dd>
1593 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1598 <dd>How many columns will be utilized to display the tables on the
1599 database property view? Default is 1 column. When setting this to a
1600 value larger than 1, the type of the database will be omitted for more
1601 display space.</dd>
1605 <dd>Defines the tab displayed by default on server view. Possible
1612 <dd>Defines the tab displayed by default on database view. Possible
1617 <dd>Defines the tab displayed by default on table view. Possible
1624 points to the MySQL documentation (type depends
1625 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1626 generated.<br />
1628 for more information about MySQL manuals and their types.</dd>
1631 <dd>Type of MySQL documentation:
1637 </ul>
1638 </dd>
1641 <dd>Defines the default language to use, if not browser-defined or
1642 user-defined.<br />
1644 this setting.</dd>
1647 <dd>Defines the default connection collation to use, if not
1648 user-defined.<br />
1653 <dd>Force: always use this language (must be defined in the
1657 <dd>Limit list of available languages to those matching the given regular
1658 expression. For example if you want only Czech and English, you should
1662 <dd>Default character set to use for recoding of MySQL queries. This must be
1663 enabled and it's described by
1665 option.<br />
1666 You can give here any character set which is in
1668 array and this is just default choice, user can select any of them.</dd>
1671 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1672 support (compiled in or module) in PHP to allow MySQL queries recoding
1673 and used language file must have it enabled (by default only these
1674 which are in Unicode, just to avoid losing some characters).<br /><br />
1677 in the Export and Import pages, to choose the character set when
1678 exporting a file. The default value in this menu comes from
1680 </dd>
1683 <dd>You can select here which functions will be used for character set
1684 conversion. Possible values are:
1685 <ul><li>auto - automatically use available one (first is tested
1686 iconv, then recode)</li>
1689 </ul>
1690 Default is auto.</dd>
1693 <dd>Specify some parameters for iconv used in charset conversion. See
1696 used, so that invalid characters will be transliterated.</dd>
1699 <dd>Available character sets for MySQL conversion. You can add your own (any of
1700 supported by recode/iconv) or remove these which you don't use.
1701 Character sets will be shown in same order as here listed, so if you
1702 frequently use some of these move them to the top.</dd>
1707 default empty, you need to fill in some trusted proxy servers if you
1708 want to use rules for IP addresses behind proxy.<br /><br />
1710 The following example specifies that phpMyAdmin should trust a
1712 <pre>
1713 $cfg['TrustedProxies'] =
1715 </pre>
1716 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1717 client's IP address as usual.
1718 </dd>
1722 MIME transformations.<br />
1723 Possible values are:
1724 <ul><li>auto - automatically detect, this is a bit expensive
1726 according to your server real possibilities</li>
1729 </ul>
1730 Default is auto.
1731 </dd>
1734 <dd>
1735 We normally check the permissions on the configuration file to ensure
1736 it's not world writable. However, phpMyAdmin could be installed on
1737 a NTFS filesystem mounted on a non-Windows server, in which case the
1738 permissions seems wrong but in fact cannot be detected. In this case
1740 </dd>
1743 <dd>
1744 Limit for length of URL in links. When length would be above this limit, it
1745 is replaced by form with button.
1746 This is required as some web servers (IIS) have problems with long URLs.
1748 </dd>
1752 </dd>
1754 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1755 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1756 </dt>
1757 <dd>The background styles used for both the frames.
1760 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1762 <dd>The style used for the pointer in the navi frame.
1766 </dt>
1767 <dd>The color used for the database name in the navi frame.
1776 </dd>
1780 <dd>The style used for table headers. See
1785 </dd>
1789 </dd>
1791 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1793 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1795 </dt>
1797 The former feature highlights the row over which your mouse is passing
1798 and the latter lets you visually mark/unmark rows by clicking on
1799 them.<br />
1804 <dd>You put here a valid CSS font family value, for example
1809 <dd>You put here a valid CSS font family value, for example
1823 </dt>
1825 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1827 The Char* values are used for CHAR and VARCHAR editing (if configured
1831 </dt>
1835 </dt>
1836 <dd>Defines if the whole textarea of the query box will be selected on
1837 click.</dd>
1840 </dt>
1841 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1842 editing.</dd>
1845 <dd>Maximum number of characters shown in any non-numeric field on browse view.
1846 Can be turned off by a toggle button on the browse page.</dd>
1850 </dt>
1851 <dd>Defines the place where modify and delete links would be put when
1852 tables contents are displayed (you may have them displayed both at the
1853 left and at the right).
1859 </dt>
1861 Define which one is displayed by default. The first mode displays each
1862 row on a horizontal line, the second rotates the headers by 90
1863 degrees, so you can use descriptive headers even though fields only
1864 contain small values and still print them out. The vertical mode sorts
1865 each row on a vertical lineup.<br /><br />
1867 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1868 the rotation of the header for horizontalflipped is done via CSS. If
1869 set to 'fake' PHP does the transformation for you, but of course this
1870 does not look as good as CSS.</dd>
1874 string or integer</dt>
1875 <dd>When editing/creating new columns in a table all fields normally get
1876 lined up one field a line. (default: 'horizontal'). If you set this to
1877 'vertical' you can have each field lined up vertically beneath each
1878 other. You can save up a lot of place on the horizontal direction and
1879 no longer have to scroll. If you set this to integer, editing of fewer
1880 columns will appear in 'vertical' mode, while editing of more fields
1881 still in 'horizontal' mode. This way you can still effectively edit
1882 large number of fields, while having full view on few of them.</dd>
1886 </dt>
1888 display of column comments in Browse or Property display. In browse
1889 mode, the comments are shown inside the header. In property mode,
1890 comments are displayed using a CSS-formatted dashed-line below the
1891 name of the field. The comment is shown as a tool-tip for that field.
1892 </dd>
1904 <dd>Whether to display a link to validate a query in any SQL Query box.
1911 <dd>
1912 The name of the directory where
1914 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1915 are available under a drop-down box when you click the database or
1916 table name, then the Import tab.
1917 <br /><br />
1919 If you want different directory for each user, %u will be replaced
1920 with username.<br /><br />
1924 compressed formats is enabled).<br /><br />
1926 This feature is useful when your file is too big to be uploaded via
1928 uploads are disabled in PHP.<br /><br />
1930 Please note that if PHP is running in safe mode, this directory must
1931 be owned by the same user as the owner of the phpMyAdmin scripts.
1932 <br /><br />
1936 alternatives.
1937 </dd>
1940 <dd>
1941 The name of the directory where dumps can be saved.<br /><br />
1943 If you want different directory for each user, %u will be replaced
1944 with username.<br /><br />
1946 Please note that the directory must exist and has to be writable for
1947 the user running webserver.<br /><br />
1949 Please note that if PHP is running in safe mode, this directory must
1950 be owned by the same user as the owner of the phpMyAdmin scripts.
1951 </dd>
1954 <dd>
1955 The name of the directory where temporary files can be stored.
1956 <br /><br />
1958 This is needed for native MS Excel export, see
1964 <br /><br />
1966 If the directory where phpMyAdmin is installed is subject to an
1968 temporary directory in some directory accessible by the web
1969 server. However for security reasons, this directory should be outside
1970 the tree published by webserver. If you cannot avoid having this
1971 directory published by webserver, place at least an empty
1973 possible.
1974 <br /><br />
1976 This directory should have as strict permissions as possible as the only
1977 user required to access this directory is the one who runs the
1978 webserver. If you have root privileges, simply make this user owner of
1979 this directory and make it accessible only by it:
1980 <br /><br />
1982 <pre>
1983 chown www-data:www-data tmp
1984 chmod 700 tmp
1985 </pre>
1987 If you cannot change owner of the directory, you can achieve a similar
1990 <pre>
1991 chmod 700 tmp
1992 setfacl -m "g:www-data:rwx" tmp
1993 setfacl -d -m "g:www-data:rwx" tmp
1994 </pre>
1996 If neither of above works for you, you can still make the directory
1998 system reading and writing data in this directory.
1999 </dd>
2002 <dd>
2003 In this array are defined default parameters for export, names of
2004 items are similar to texts seen on export page, so you can easily
2005 identify what they mean.
2006 </dd>
2009 <dd>
2010 In this array are defined default parameters for import, names of
2011 items are similar to texts seen on import page, so you can easily
2012 identify what they mean.
2013 </dd>
2016 <dd>
2017 Repeat the headers every X cells, or 0 to deactivate.
2018 </dd>
2026 </dt>
2027 <dd>
2028 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2029 or icon is always displayed on the left panel. If JavaScript is enabled in
2030 your browser, a click on this opens a distinct query window, which is
2031 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2032 changes to display a query box.<br /><br />
2034 The size of this query window can be customized with
2036 - both integers for the size in pixels. Note that normally, those
2038 theme you are using.<br /><br />
2042 opens the query window and puts the current query
2043 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2044 query in the right panel's query box.
2045 <br /><br />
2046 The usage of the JavaScript query window is recommended if you have a
2047 JavaScript enabled browser. Basic functions are used to exchange quite
2048 a few variables, so most 4th generation browsers should be capable to
2049 use that feature. It currently is only tested with Internet Explorer 6
2050 and Mozilla 1.x.
2051 <br /><br />
2053 to a table, which has to be created by you (see <a
2055 all your queries will be appended to the form, but only as long as
2056 your window is opened they remain saved.
2057 <br /><br />
2058 When using the JavaScript based query window, it will always get
2059 updated when you click on a new table/db to browse and will focus if
2060 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2061 the query window by checking the box "Do not overwrite this query from
2062 outside the window" below the query textarea. Then you can browse
2063 tables/databases in the background without losing the contents of the
2064 textarea, so this is especially useful when composing a query with
2065 tables you first have to look in. The checkbox will get automatically
2066 checked whenever you change the contents of the textarea. Please
2067 uncheck the button whenever you definitely want the query window to
2068 get updated even though you have made alterations.
2069 <br /><br />
2072 <br /><br />
2073 The query window also has a custom tabbed look to group the features.
2075 default tab to be used when opening the query window. It can be set to
2076 either 'sql', 'files', 'history' or 'full'.</dd>
2082 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2084 If the approximate row count as returned by
2087 count will be used.
2088 </dd>
2090 <dd>For VIEWs, since obtaining the exact count could have an
2091 impact on performance, this value is the maximum to be displayed, using
2093 any row counting.
2094 </dd>
2098 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
2100 page. By clicking on the button 'toggle scratchboard' on the page
2101 where you edit x/y coordinates of those elements you can activate a
2102 scratchboard where all your elements are placed. By clicking on an
2103 element, you can move them around in the pre-defined area and the x/y
2104 coordinates will get updated dynamically. Likewise, when entering a
2105 new position directly into the input field, the new position in the
2106 scratchboard changes after your cursor leaves the input field.<br />
2107 You have to click on the 'OK'-button below the tables to save the new
2108 positions. If you want to place a new element, first add it to the
2109 table of elements and then you can drag the new element around.<br />
2110 By changing the paper size and the orientation you can change the size
2111 of the scratchboard as well. You can do so by just changing the
2112 dropdown field below, and the scratchboard will resize automatically,
2113 without interfering with the current placement of the elements.<br />
2114 If ever an element gets out of range you can either enlarge the paper
2115 size or click on the 'reset' button to place all elements below each
2116 other.<br />
2118 get this control to work. The basic Drag&Drop script functionality
2119 was kindly borrowed from www.youngpup.net and is underlying so
2120 specific license.</dd>
2123 <dd>Sorts database and table names according to natural order (for example,
2124 t1, t2, t10). Currently implemented in the left panel (Light mode)
2125 and in Database view, for the table list.</dd>
2136 <dd>Allows you to specify window's title bar. Following magic string can
2137 be used to get special values:
2138 <dl>
2144 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
2153 </dl>
2154 </dd>
2164 </dd>
2167 <dd>If theme manager is active, use this as the path of the subdirectory
2168 containing all the themes.</dd>
2182 </dt>
2183 <dd>Default queries that will be displayed in query boxes when user didn't
2184 specify any. Use %d for database name, %t for table name and %f for a
2185 comma separated list of field names. Note that %t and %f are only
2189 <dd>
2190 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
2191 default we use HTML to format the query, but you can disable this by
2193 </dd>
2196 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2197 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2198 query inside a bracket is indented. By changing
2201 specifies the units of the indent amount that you specified. This is
2202 used via stylesheets.</dd>
2205 <dd>This array is used to define the colours for each type of element of
2206 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2208 If you specify an empty string for the color of a class, it is ignored
2209 in creating the stylesheet.
2210 You should not alter the class names, only the colour strings.<br />
2231 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2235 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2236 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2237 </ul>
2238 </dd>
2242 <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,
2243 as originally published on
2245 <br />
2246 For help in setting up your system to use the service, see the
2248 </dd>
2252 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2253 and any password, so we use those by default. Instead, if
2254 you have an account with them, you can put your login details
2255 here, and it will be used in place of the anonymous login.</dd>
2256 </dl>
2257 </dd>
2260 <dd><b>DEVELOPERS ONLY!</b></dd>
2263 <dd><b>DEVELOPERS ONLY!</b><br />
2264 Enable logging queries and execution times to be displayed in the bottom
2265 of main page (right frame).</dd>
2268 <dd><b>DEVELOPERS ONLY!</b><br />
2269 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2270 the code.<br />
2271 For help in setting up your system to this, see the
2275 <dd><b>DEVELOPERS ONLY!</b><br />
2276 Enable profiling support for phpMyAdmin. This will append a chunk of data
2277 to the end of every page displayed in the main window with profiling
2278 statistics for that page.<br />
2279 You may need to increase the maximum execution time for this to
2280 complete successfully.<i>Profiling was removed from the code for
2281 version 2.9.0 due to licensing issues.</i></dd>
2283 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2284 <dd><b>DEVELOPERS ONLY!</b><br />
2285 When profiling data is displayed, this variable controls the threshold of
2286 display for any profiling data, based on the average time each time has
2287 taken. If it is over the threshold it is displayed, otherwise it is not
2288 displayed. This takes a value in milliseconds. In most cases you don't need
2289 to edit this.</dd>
2292 <dd>All possible types of a MySQL column. In most cases you don't need to
2293 edit this.</dd>
2296 <dd>Possible attributes for fields. In most cases you don't need to edit
2297 this.</dd>
2300 <dd>A list of functions MySQL supports. In most cases you don't need to
2301 edit this.</dd>
2304 <dd>Mapping of column types to meta types used for preferring displayed
2305 functions. In most cases you don't need to edit this.</dd>
2308 <dd>Functions preferred for column meta types as defined in
2309 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2310 to edit this.</dd>
2313 <dd>Functions selected by default when inserting/changing row, Functions
2314 are defined for meta types from
2316 <code>first_timestamp</code>, which is used for first timestamp column
2317 in table.</dd>
2320 <dd>Operators available for search operations on numeric and date fields.
2321 </dd>
2324 <dd>Operators available for search operations on character fields.
2325 Note that we put <code>LIKE</code> by default instead of
2326 <code>LIKE %...%</code>, to avoid unintended performance problems
2327 in case of huge tables.</dd>
2330 <dd>Operators available for search operations on enum fields.</dd>
2333 <dd>Additional operators available for search operations when the
2334 field can be null.</dd>
2336 </dl>
2338 <!-- TRANSFORMATIONS -->
2344 </ol>
2348 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2350 section</a> on how to do so.</p>
2352 <p> You can apply different transformations to the contents of each field. The
2353 transformation will take the content of each field and transform it with
2354 certain rules defined in the selected transformation.</p>
2356 <p> Say you have a field 'filename' which contains a filename. Normally you would
2357 see in phpMyAdmin only this filename. Using transformations you can transform
2358 that filename into a HTML link, so you can click inside of the phpMyAdmin
2359 structure on the field's link and will see the file displayed in a new browser
2360 window. Using transformation options you can also specify strings to
2361 append/prepend to a string or the format you want the output stored in.</p>
2363 <p> For a general overview of all available transformations and their options,
2364 you can consult your
2365 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2366 installation.</p>
2368 <p> For a tutorial on how to effectively use transformations, see our
2370 the official phpMyAdmin homepage.</p>
2374 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2375 clicking on the 'Structure' link for a table). There click on
2376 "Change" (or change icon) and there you will see three new fields at
2377 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2378 'Transformation options'.</p>
2380 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2381 that corresponds to the column's contents. Please note that
2382 transformations are inactive as long as no MIME-type is selected.</li>
2384 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2385 hopefully growing amount of pre-defined transformations. See below for information on
2386 how to build your own transformation.<br />
2388 There are global transformations and mimetype-bound transformations. Global transformations
2389 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2390 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2391 transformations which operate on the main mimetype (like 'image'), which will most likely
2392 take the subtype into regard, and those who only operate on a
2393 specific subtype (like 'image/jpeg').<br />
2395 You can use transformations on mimetypes for which the function was not defined for. There
2396 is no security check for you selected the right transformation, so take care of what the
2397 output will be like.</li>
2399 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2400 transform-function specific options here. Usually the transforms can operate with default
2401 options, but it is generally a good idea to look up the overview to see which options are
2402 necessary.<br />
2404 Much like the ENUM/SET-Fields, you have to split up several options using the format
2405 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2406 parsed as an array, leaving the first value the first element in the array, and so
2407 forth.<br />
2409 If you want to specify a MIME character set you can define it in the transformation_options.
2410 You have to put that outside of the pre-defined options of the specific mime-transform,
2412 for which you can specify 2 options and you want to append a character set, enter "'first
2413 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2415 </ul>
2419 <p> All mimetypes and their transformations are defined through single files in
2420 the directory 'libraries/transformations/'.</p>
2422 <p> They are stored in files to ease up customization and easy adding of new
2423 transformations.</p>
2425 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2426 always work. It makes no sense to apply a transformation to a mimetype, the
2427 transform-function doesn't know to handle.</p>
2429 <p> One can, however, use empty mime-types and global transformations which should work
2430 for many mimetypes. You can also use transforms on a different mimetype they where built
2431 for, but pay attention to option usage as well as what the transformation does to your
2432 field.</p>
2434 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2435 any other transform function and provides some basic functions.</p>
2437 <p> There are 5 possible file names:</p>
2439 <ol><li>A mimetype+subtype transform:<br /><br />
2441 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2443 Please not that mimetype and subtype are separated via '_', which shall
2444 not be contained in their names. The transform function/filename may
2445 contain only characters which cause no problems in the file system as
2446 well as the PHP function naming convention.<br /><br />
2448 The transform function will the be called
2449 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2451 <b>Example:</b><br /><br />
2453 <tt>text_html__formatted.inc.php</tt><br />
2454 <tt>PMA_transform_text_html__formatted()</tt></li>
2456 <li>A mimetype (w/o subtype) transform:<br /><br />
2458 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2460 Please note that there are no single '_' characters.
2461 The transform function/filename may contain only characters which cause
2462 no problems in the file system as well as the PHP function naming
2463 convention.<br /><br />
2465 The transform function will the be called
2466 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2468 <b>Example:</b><br /><br />
2470 <tt>text__formatted.inc.php</tt><br />
2471 <tt>PMA_transform_text__formatted()</tt></li>
2473 <li>A mimetype+subtype without specific transform function<br /><br />
2475 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2477 Please note that there are no '__' characters in the filename. Do not
2478 use special characters in the filename causing problems with the file
2479 system.<br /><br />
2481 No transformation function is defined in the file itself.<br /><br />
2483 <b>Example:</b><br /><br />
2485 <tt>text_plain.inc.php</tt><br />
2486 (No function)</li>
2488 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2490 <tt>[mimetype].inc.php</tt><br /><br />
2492 Please note that there are no '_' characters in the filename. Do not use
2493 special characters in the filename causing problems with the file system.
2494 <br /><br />
2496 No transformation function is defined in the file itself.<br /><br />
2498 <b>Example:</b><br /><br />
2500 <tt>text.inc.php</tt><br />
2501 (No function)</li>
2503 <li>A global transform function with no specific mimetype<br /><br />
2505 <tt>global__[transform].inc.php</tt><br /><br />
2507 The transform function will the be called
2508 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2510 <b>Example:</b><br /><br />
2512 <tt>global__formatted</tt><br />
2513 <tt>PMA_transform_global__formatted()</tt></li>
2514 </ol>
2516 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2517 transform function.</p>
2519 <p> All filenames containing no '__' in themselves are not shown as valid transform
2520 functions in the dropdown.</p>
2522 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2523 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2524 without a transform function. Also note the introduction of a function description in
2525 the language files. For each function a $strTransformation_[filename without .inc.php]
2526 has to exist.</p>
2528 <p> You can use the template generator to generate new functions and entries in the
2529 language file.</p>
2531 <p> To create a new transform function please see
2532 <tt>libraries/transformations/template_generator.sh</tt>.
2533 To create a new, empty mimetype please see
2534 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2536 <p> A transform function always gets passed three variables:</p>
2538 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2539 you want to transform.</li>
2540 <li><b>$options</b> - Contains any user-passed options to a transform function
2541 as an array.</li>
2542 <li><b>$meta</b> - Contains an object with field information to your column.
2543 The data is drawn from the output of the
2545 function. This means, all object properties described on the
2547 available in this variable and can be used to transform a field accordingly
2548 to unsigned/zerofill/not_null/... properties.<br />
2549 The $meta->mimetype variable contains the original MIME-type of the
2550 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2551 </ol>
2553 <!-- FAQ -->
2560 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2565 </ol>
2567 <p> Please have a look at our
2569 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2570 features and or interface.</p>
2576 action is required or phpMyAdmin sends a blank page or a page full of
2577 cryptic characters to my browser, what can I do?</a></h4>
2580 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2581 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2582 configuration file.<br /></p>
2587 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2588 See also the
2590 entry about PHP bugs with output buffering.<br />
2591 If your server keeps crashing, please ask for help in the various Apache
2592 support groups.</p>
2601 application misbehaved by not returning a complete set of
2603 </h4>
2605 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2606 Have a look at the last message in this
2608 official PHP bug database.</p>
2613 and/or many error messages with the
2615 mode.</a></h4>
2617 <p> This is a known problem with the PHP
2619 filter: it's not so stable. Please use instead the cookie authentication mode.
2620 </p>
2625 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2626 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2627 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2628 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2629 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2634 work.</a></h4>
2636 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2637 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2638 or not, and so on). So, you must have Zlib/Bzip2
2639 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br /></p>
2643 an error about safe mode being in effect.</a></h4>
2645 <p> Your uploaded file is saved by PHP in the "upload dir", as
2646 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2647 the system default is <i>/tmp</i>).<br />
2648 We recommend the following setup for Apache servers running in safe mode,
2649 to enable uploads of files while being reasonably secure:</p>
2651 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2652 <li>give ownership to the Apache server's user.group:
2653 <tt>chown apache.apache /tmp/php</tt></li>
2654 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2655 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2656 <li>restart Apache</li>
2657 </ul>
2661 general file uploads don't work on my system and uploaded files have a
2662 <tt>Content-Type:</tt> header in the first line.</a></h4>
2664 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2665 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2666 So the problem is that this package has a serious bug that was corrected
2667 ages ago in PHP (2001-01-28: see
2669 for more details). The problem is that the bugged package is still
2670 available though it was corrected (see
2672 for more details).<br />
2673 So please download
2674 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2675 and the problem should go away.<br />
2676 And that fixes the \r\n problem with file uploads!</p>
2680 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2681 I'm using the Apache server.</a></h4>
2683 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2684 your <i>httpd.conf</i>:</p>
2688 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2692 uploading a file from the query box.</a></h4>
2694 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2695 restrictions. However you need to create temporary directory and
2697 The uploaded files will be moved there, and after execution of your
2703 <p> The MySQL manual explains how to
2705 reset the permissions</a>.</p>
2710 execute a bookmark.</a></h4>
2712 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2713 cannot access the uploaded query.</p>
2718 submit a query from the convenient text area.</a></h4>
2720 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2721 and try to increase it.</p>
2725 </h4>
2727 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2728 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2729 names to align with current standards.</p>
2734 </h4>
2736 <p> Starting with version 2.7.0, the import engine has been re–written and these
2737 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2738 to take advantage of the new import features.</p>
2740 <p> The first things to check (or ask your host provider to check) are the
2741 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2742 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2743 All of these three settings limit the maximum size of data that can be
2744 submitted and handled by PHP. One user also said that post_max_size
2745 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2747 There exist several workarounds if your upload is too big or your
2748 hosting provider is unwilling to change the settings:</p>
2751 feature. This allows one to
2752 upload a file to the server via scp, ftp, or your favorite file transfer
2753 method. PhpMyAdmin is then able to import the files from the temporary
2755 section</a> of this document.</li>
2757 BigDump</a>) to split the files before uploading. We cannot support this
2758 or any third party applications, but are aware of users having success
2759 with it.</li>
2760 <li>If you have shell (command line) access, use MySQL to import the files
2761 directly. You can do this by issuing the "source" command from
2762 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2763 </ul>
2767 support?</a></h4>
2769 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2770 older MySQL versions, you need to use 2.8.x branch. phpMyAdmin can
2771 connect to your MySQL server using PHP's classic
2774 is available in php 5.0. The latter one should be used unless you have
2775 good reason not to do so.<br />
2776 When compiling php, we strongly recommend that you manually link the MySQL
2777 extension of your choice to a MySQL client library of at least the same
2778 minor version since the one that is bundled with some PHP distributions is
2781 If your webserver is running on a windows system, you might want to try
2782 MySQL's
2784 instead of the MySQL / MySQLi extensions that are bundled with the official
2785 php Win32 builds.</p>
2789 message, "Client does not support authentication protocol requested
2790 by server; consider upgrading MySQL client"</a></h5>
2792 <p> You tried to access MySQL with an old MySQL client library. The version of
2793 your MySQL client library can be checked in your phpinfo() output.
2794 In general, it should have at least the same minor version as your server
2798 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2799 changed the authentication hash and your PHP is trying to use the old method.
2801 with the proper client library to match your MySQL installation. Your
2802 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2803 More information (and several workarounds) are located in the
2805 </p>
2812 script seems not to know the font face I'm using!</a></h4>
2814 <p> The "FPDF" library we're using for this feature requires some
2815 special files to use font faces.<br />
2817 these files.</p>
2821 check PHP Configuration".</a></h4>
2823 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2824 "MySQL extension". This extension may be part of the PHP
2825 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2826 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2827 to load the extension but failed.<br /><br />
2829 Usually, the problem is solved by installing a software package called
2830 "PHP-MySQL" or something similar.</p>
2835 and I cannot log in using cookie auth.</a></h4>
2837 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2841 so I cannot upload.</a></h4>
2843 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2844 parameter is not set to "on".</p>
2848 a new table the table and field names are changed to lowercase!</a></h4>
2850 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2851 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2852 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2853 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2854 directory and add the following line to the group [mysqld]:</p>
2856 <pre>set-variable = lower_case_table_names=0</pre>
2858 <p> Next, save the file and restart the MySQL service. You can always check the
2859 value of this directive using the query</p>
2861 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2868 and I get problems, such as undefined variables when I run a
2871 <p> A tip from Jose Fandos: put a comment on the following two lines
2872 in httpd.conf, like this:</p>
2874 <pre>
2875 # mod_gzip_item_include file \.php$
2877 </pre>
2879 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2880 PHP scripts. Of course you have to restart Apache.</p>
2885 I get the error "No input file specified" when trying to
2886 run phpMyAdmin.</a></h4>
2888 <p> This is a permission problem. Right-click on the phpmyadmin folder
2889 and choose properties. Under the tab Security, click on "Add"
2890 and select the user "IUSR_machine" from the list. Now set his
2891 permissions and it should work.</p>
2895 db_structure.php with plenty of tables).</a></h4>
2898 GZIP output buffering is enabled. If you turn off it (by
2900 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2901 PHP 5.0.0.</p>
2905 message 'Errorcode: 13'. What does this mean?</a></h4>
2907 <p> This can happen due to a MySQL bug when having database / table names with
2908 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2909 To fix this, turn off this directive, convert all database and table names
2910 to lower case and turn it on again. Alternatively, there's a bug-fix
2911 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2915 and the fields are duplicated.</a></h4>
2917 <p> It is possible to configure Apache in such a way that PHP has problems
2918 interpreting .php files.</p>
2920 <p> The problems occur when two different (and conflicting) set of directives
2921 are used:</p>
2923 <pre>
2924 SetOutputFilter PHP
2925 SetInputFilter PHP
2926 </pre>
2928 <p> and</p>
2930 <pre>AddType application/x-httpd-php .php</pre>
2932 <p> In the case we saw, one set of directives was in
2933 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2934 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2935 The recommended way is with <tt>AddType</tt>, so just comment out
2936 the first set of lines and restart Apache:</p>
2938 <pre>
2939 #SetOutputFilter PHP
2940 #SetInputFilter PHP
2941 </pre>
2946 <p> This problem is known to happen when the server is running Turck MMCache
2947 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2952 <p> Yes.<br />
2953 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2954 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2955 <tt>error_reporting</tt> settings.
2956 </p>
2959 <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>
2961 <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>
2964 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2965 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2966 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2967 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2968 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2969 enabled.) Click <tt>OK</tt>.</li>
2970 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2971 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2972 </ol>
2976 PHP 5.0.4 on 64-bit systems?</a></h4>
2978 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2979 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
2985 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
2986 the order of the server paragraph in <tt>config.inc.php</tt>.
2987 Table and script parts are optional. If you want
2988 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
2989 some configuration. Following lines apply only for <a
2991 that you have enabled some features within global configuration. You need
2992 <code>Options FollowSymLinks</code> and <code>AllowOverride
2993 FileInfo</code> enabled for directory where phpMyAdmin is installed and
2994 you need mod_rewrite to be enabled. Then you just need to create following
2995 <code>.htaccess</code> file in root folder of phpMyAdmin installation
2996 (don't forget to change directory name inside of it):</p>
2998 <pre>
2999 RewriteEngine On
3000 RewriteBase /path_to_phpMyAdmin
3001 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3002 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3003 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3004 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3005 </pre>
3008 <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>
3010 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3011 following rewrite rule:</p>
3013 <pre>
3014 RewriteEngine On
3015 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3016 </pre>
3020 </h4>
3021 <p>
3022 There can be many explanations to this and a look at your server's
3023 error log file might give a clue.
3024 </p>
3028 password encryption in cookie auth doesn't work.</a></h4>
3030 <p> If your cluster consist of different architectures, PHP code used for
3031 encryption/decryption won't work correct. This is caused by use of
3032 pack/unpack functions in code. Only solution is to use mcrypt extension
3033 which works fine in this case.</p>
3038 <p> Yes but the default configuration values of Suhosin are known to cause
3039 problems with some operations, for example editing a table with many
3040 columns and no primary key or with textual primary key.
3041 </p>
3042 <p>
3043 Suhosin configuration might lead to malfunction in some cases and it can
3044 not be fully avoided as phpMyAdmin is kind of application which needs to
3045 transfer big amounts of fields in single HTTP request, what is something
3046 what Suhosin tries to prevent. Generally all
3047 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3048 <code>suhosin.get.*</code> directives can have negative effect on
3049 phpMyAdmin usability. You can always find in your error logs which limit
3050 did cause dropping of variable, so you can diagnose the problem and adjust
3051 matching configuration variable.
3052 </p>
3053 <p>
3054 The default values for most Suhosin configuration options will work in most
3055 scenarios, however you might want to adjust at least following parameters:
3056 </p>
3058 <ul>
3059 <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>
3060 <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>
3061 <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>
3062 <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>
3063 <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>
3064 <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>
3065 <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>
3066 <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>
3067 </ul>
3069 <p>
3071 <tt>SuhosinDisableWarning</tt> directive</a>.
3072 </p>
3076 but then my connection is redirected back to http. What can cause this
3077 behavior?</a></h4>
3079 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3080 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>
3083 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work.</a></h4>
3085 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3086 Example from the Apache 2.2 documentation:</p>
3087 <pre>
3088 ProxyPass /mirror/foo/ http://backend.example.com/
3089 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3090 ProxyPassReverseCookieDomain backend.example.com public.example.com
3091 ProxyPassReverseCookiePath / /mirror/foo/
3092 </pre>
3094 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3095 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3096 This is not specific to phpmyadmin, it's just the behavior of Apache.
3097 </p>
3099 <pre>
3100 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3101 ProxyPassReverse /mirror/foo/
3102 http://backend.example.com/%7Euser/phpmyadmin
3103 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3104 </pre>
3106 <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>
3107 for more details.</p>
3111 privileges, I get an error about an unknown column.</a></h4>
3113 <p> The MySQL server's privilege tables are not up to date, you need to run
3114 the <tt>mysql_upgrade</tt> command on the server.</p>
3121 headers already sent by ..." is displayed, what's the problem?</a></h4>
3123 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3124 (I.E. no blank lines, no spaces, no characters...) neither before the
3125 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3126 tag at the end. We also got a report from a user under IIS, that used
3127 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3128 contained an end-of-line character (hex 0A) at the end; removing this character
3129 cleared his errors.</p>
3134 <p> Either there is an error with your PHP setup or your username/password is
3135 wrong. Try to make a small script which uses mysql_connect and see if it
3136 works. If it doesn't, it may be you haven't even compiled MySQL support
3137 into PHP.</p>
3141 connect to local MySQL server through socket '/tmp/mysql.sock'
3142 (111) ..." is displayed. What can I do?</a></h4>
3144 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3146 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3147 In your <i>php.ini</i> you will find a line</p>
3149 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3151 <p> change it to</p>
3153 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3155 <p> Then restart apache and it will work.</p>
3157 <p> Here is a fix suggested by Brad Ummer:</p>
3159 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3160 To do this, telnet to your server and go to the MySQL bin directory. In
3161 this directory there should be a file named <i>mysqladmin</i>. Type
3162 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3163 info about your MySQL server, including the socket
3164 (<i>/tmp/mysql.sock</i>, for example).</li>
3165 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3166 phpMyAdmin, you need to complete the socket information in the
3167 <i>config.inc.php</i>.<br />
3168 For example:
3170 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3171 <br /><br />
3173 Please also make sure that the permissions of this file allow to be readable
3174 by your webserver (i.e. '0755').</li>
3175 </ul>
3177 <p> Have also a look at the
3179 corresponding section of the MySQL documentation</a>.</p>
3183 what can I do?</a></h4>
3186 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3187 sometime.<br />
3188 Also have a look at your PHP version number: if it contains "4.0b..."
3189 it means you're running a beta version of PHP. That's not a so good idea,
3190 please upgrade to a plain revision.</p>
3194 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3195 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3197 <p> Check the value you set for the
3199 directive in the phpMyAdmin configuration file.</p>
3203 password: YES)"-error when trying to access a MySQL-Server on a
3204 host which is port-forwarded for my localhost.</a></h4>
3206 <p> When you are using a port on your localhost, which you redirect via
3207 port-forwarding to another host, MySQL is not resolving the localhost
3208 as expected.<br />
3209 Erik Wasser explains: The solution is: if your host is "localhost"
3210 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
3211 connection for speeding up things. And that doesn't work in this configuration
3212 with port forwarding.<br />
3218 <p> Themes are configured with
3222 <br />
3224 should not delete the directory "original" or its underlying
3225 structure, because this is the system theme used by phpMyAdmin.
3226 "original" contains all images and styles, for backwards
3227 compatibility and for all themes that would not include images or css-files.
3228 <br /><br />
3231 is enabled, you can select your favorite theme on the main page. Your
3232 selected theme will be stored in a cookie.<br /><br /></p>
3234 <p> To create a theme:</p>
3236 <ul><li>make a new subdirectory (for example "your_theme_name") under
3238 (by default <tt>themes</tt>)</li>
3239 <li>copy the files and directories from "original" to
3240 "your_theme_name"</li>
3241 <li>edit the css-files in "your_theme_name/css"</li>
3242 <li>put your new images in "your_theme_name/img"</li>
3243 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3244 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3245 contain your chosen theme name, that will be visible in user interface</li>
3246 <li>make a new screenshot of your theme and save it under
3247 "your_theme_name/screen.png"</li>
3248 </ul>
3250 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3251 theme verbose name, theme generation and theme version. These versions and
3252 generations are enumerated from 1 and do not have any direct dependence on
3253 phpMyAdmin version. Themes within same generation should be backwards
3254 compatible - theme with version 2 should work in phpMyAdmin requiring
3255 version 1. Themes with different generation are incompatible.</p>
3257 <p> If you do not want to use your own symbols and buttons, remove the
3258 directory "img" in "your_theme_name". phpMyAdmin will
3259 use the default icons and buttons (from the system-theme "original").
3260 </p>
3264 what can I do?</a></h4>
3266 <p> Here are a few points to check:</p>
3268 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3270 directive empty. See also
3272 </li>
3273 <li>Maybe you have a broken PHP installation or you need to upgrade
3274 your Zend Optimizer. See
3276 http://bugs.php.net/bug.php?id=31134</a>.
3277 </li>
3278 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3279 set to the default (200) or another low value, you could get this
3280 error if your table has a high number of columns. Adjust this setting
3281 accordingly. (Thanks to Klaus Dorninger for the hint).
3282 </li>
3283 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3284 of ";" will cause this error. Replace it with "&;".
3285 </li>
3287 you might want to increase
3289 </li>
3290 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3291 </li>
3292 </ul>
3297 <p> To be able to see a progress bar during your uploads, your server must
3300 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3301 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3308 who logged out can not log in again in with the same nick.</a></h4>
3310 <p> This is related to the authentication mechanism (protocol) used by
3311 phpMyAdmin. To bypass this problem: just close all the opened
3312 browser windows and then go back to phpMyAdmin. You should be able to
3313 log in again.</p>
3317 limit error or a time limit error.</a></h4>
3319 <p> Compressed dumps are built in memory and because of this are limited to
3320 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3321 using
3323 (enabled by default). Zip exports can not be handled this way, so if you need
3324 Zip files for larger dump, you have to use another way.</p>
3328 when I rename a table or a column.</a></h4>
3330 <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>
3334 bundled with the MySQL server distribution.</a></h4>
3336 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3338 <pre>
3339 -- MySQL dump 8.22
3340 --
3341 -- Host: localhost Database: database
3342 ---------------------------------------------------------
3343 -- Server version 3.23.54
3344 </pre>
3346 <p> The invalid part of the code is the horizontal line made of dashes that
3347 appears once in every dump created with mysqldump. If you want to run your
3348 dump you have to turn it into valid MySQL. This means, you have to add a
3349 whitespace after the first two dashes of the line or add a # before it:
3350 <br />
3351 <code>
3352 -- -------------------------------------------------------<br />
3353 </code>
3354 or<br />
3355 <code>
3356 #---------------------------------------------------------
3357 </code>
3358 </p>
3365 <p> Please note that you should not use the separating string multiple times
3366 without any characters between them, or at the beginning/end of your table
3367 name. If you have to, think about using another TableSeparator or disabling
3368 that feature</p>
3373 <p> In Relation view, being able to choose a table in another database,
3374 or having more than one index field in the foreign key.<br /><br/>
3375 In Query-by-example (Query), automatic generation of the query
3376 LEFT JOIN from the foreign table.<br /><br/>
3377 </p>
3381 I get series of errors like "Warning: unable to parse url". How
3382 can this be fixed?</a></h4>
3383 <p>
3384 Your table neither have a primary key nor an unique one, so we must use a
3385 long expression to identify this row. This causes problems to parse_url
3386 function. The workaround is to create a primary or unique key.
3387 <br />
3388 </p>
3392 a MIME-Transformation onto!</a></h4>
3394 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3395 nested forms can be put inside the table where phpMyAdmin displays the results.
3396 You can, however, use any form inside of a table if keep the parent
3397 form-container with the target to tbl_row_delete.php and just put your own
3398 input-elements inside. If you use a custom submit input field, the form will
3399 submit itself to the displaying page again, where you can validate the
3400 $HTTP_POST_VARS in a transformation.
3402 For a tutorial on how to effectively use transformations, see our
3404 on the official phpMyAdmin-homepage.</p>
3408 MySQL server</a></h4>
3410 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3413 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3414 the quote-character (") is interpreted as an identifier quote character and
3415 not as a string quote character, which makes many internal phpMyAdmin
3417 statements. There is no workaround to this behaviour. News to this item will
3418 be posted in Bug report
3419 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3420 </p>
3424 more that one column with the same value
3425 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3426 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3428 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3429 can use it for the Edit and Delete links.</p>
3434 <p> phpMyAdmin uses a quick method to get the row count, and this method
3435 only returns an approximate count in the case of InnoDB tables. See
3437 a way to modify those results, but
3438 this could have a serious impact on performance.</p>
3443 <p> The number of records in queries containing COUNT and GROUP BY is
3444 not correctly calculated. Also, sorting results of a query like
3449 containing an hyphen.
3450 </a></h4>
3451 <p>
3452 The tests I have made with current MySQL 4.1.11 API shows that the
3453 API does not accept this syntax for the USE command. Enclosing the
3454 db name with backquotes works. For further confusion, no backquotes
3455 are needed with command-line mysql.
3456 </p>
3459 <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>
3460 <p>
3461 This has been a known limitation of phpMyAdmin since the beginning and
3462 it's not likely to be solved in the future.
3463 </p>
3465 <!-- Begin: Excel import limitations -->
3468 <a href="#faq3_15">3.15 When I import an Excel spreadsheet, some cells with calculations do not display correctly.</a></h4>
3469 <p>
3470 phpMyAdmin uses the <a href="http://www.codeplex.com/PHPExcel/" target="_blank">PHPExcel</a> library to parse Excel XLS and XLSX spreadsheets.
3471 Therefore, any limitations that are listed on their page regarding Excel calculations will also apply here.
3472 <br /><br />
3473 PHPExcel will be kept up to date so as to make all improvements available to phpMyAdmin users.
3474 </p>
3477 <a href="#faq3_16">3.16 When I compress (gzip, bzip2, zip) an Excel workbook and attempt to import it, nothing happens.</a></h4>
3478 <p>
3479 Since Excel XLSX workbooks are already compressed, there is often times only a small benefit from compressing them yet again.
3480 Support for compressed Excel XLSX and XLS workbooks may be added in the future.
3481 </p>
3484 <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>
3485 <p>
3486 Excel's internal representation of custom cell types is rather muddled (especially in Excel 97-2003 binary XLS files). If possible,
3487 consider using a built-in type. These are almost always guarenteed to import correctly.
3488 </p>
3490 <!-- End: Excel import limitations -->
3491 <!-- Begin: CSV import limitations -->
3494 <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>
3495 <p>
3496 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.
3497 </p>
3499 <!-- End: CSV import limitations -->
3500 <!-- Begin: Import type-detection limitations -->
3503 <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>
3504 <p>
3505 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
3506 you will have to edit the structure to your liking post-import.
3507 <br /><br />
3508 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
3509 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.
3510 </p>
3512 <!-- End: Import type-detection limitations -->
3514 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3517 <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
3518 need to install it for each customer.
3519 </a></h4>
3520 <p>
3521 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3522 your users. The development of this feature was kindly sponsored by
3523 NetCologne GmbH.
3524 This requires a properly setup MySQL user management and phpMyAdmin
3525 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3527 </p>
3531 access.
3532 </a></h4>
3533 <p>
3534 This depends on your system.<br />
3535 If you're running a server which cannot be accessed by other people, it's
3536 sufficient to use the directory protection bundled with your webserver
3538 If other people have telnet access to your server, you should use
3539 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3540 <br /><br />
3541 Suggestions:
3542 </p>
3543 <ul>
3544 <li>
3546 </li>
3547 <li>
3548 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3549 is a user whose password is only known to you, and apache is the
3550 group under which Apache runs.
3551 </li>
3552 <li>
3553 You should use PHP safe mode, to protect from other users that try
3555 </li>
3556 </ul>
3561 </a></h4>
3562 <p>
3567 </p>
3570 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3571 authentication.
3572 </a></h4>
3576 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3577 and/or
3579 are wrong.</li>
3581 <li>You have already setup a security mechanism for the
3582 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3583 phpMyAdmin's authentication, so remove it.</li>
3584 </ul>
3591 and put the privileges you want. For example,
3593 would let a user create/manage his/her database(s).</p>
3598 <p> If you have existing rules from an old .htaccess file, you can take them
3601 be a major benefit here if your installation is suited to using it. Then
3602 you can just add those updated lines into the
3606 <p> If you want a pre-made sample, you can try this fragment. It stops the
3607 'root' user from logging in from any networks other than the private
3610 <pre>
3611 //block root from logging in except from the private networks
3612 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3613 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3614 'deny root from all',
3615 'allow root from localhost',
3619 );
3620 </pre>
3625 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3626 different than the one set in your
3628 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3629 while a domain name is defined in the config file.</p>
3634 <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>
3640 when trying to create a table with more than 14 fields.
3641 </a></h4>
3642 <p>
3643 We could reproduce this problem only under Win98/98SE. Testing under
3644 WinNT4 or Win2K, we could easily create more than 60 fields.
3645 <br />
3646 A workaround is to create a smaller number of fields, then come back to
3647 your table properties and add the other fields.
3648 </p>
3652 <p>
3653 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3654 with each script/website that use forms.<br />
3655 Upgrade or downgrade your Xitami server.
3656 </p>
3659 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3660 <p>
3661 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3662 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3663 don't seem to work.<br />
3665 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3666 the user's temporary directory, so they must be moved before closing
3667 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3670 </p>
3674 Explorer never stores the cookies.
3675 </a></h4>
3676 <p>
3677 MS Internet Explorer seems to be really buggy about cookies, at least till
3678 version 6.
3679 </p>
3683 rows.
3684 </a></h4>
3685 <p>
3687 </p>
3690 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3691 when trying to modify a row in a table with many fields, or with a text field
3692 </a></h4>
3693 <p>
3694 Your table neither have a primary key nor an unique one, so we must use a
3695 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
3696 those browsers, and this not happen in Netscape, for example. The
3697 workaround is to create a primary or unique key, or use another browser.
3698 <br />
3699 </p>
3703 page.
3704 </a></h4>
3705 <p>
3706 Some browsers support right-clicking into the frame you want to refresh,
3707 just do this in the right frame.<br />
3708 </p>
3712 query box.
3713 </a></h4>
3714 <p>
3715 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3716 Mozilla versions.<br />
3717 </p>
3721 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3722 </a></h4>
3723 <p>
3724 This is a Mozilla bug (see bug #26882 at
3726 </p>
3731 </a></h4>
3732 <p>
3733 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3734 data in octet-stream mode. Since we can't detect the specific Netscape
3735 version, we cannot workaround this bug.
3736 </p>
3740 wrong.</a></h4>
3742 <p> Please ensure that you have set your browser's character set to the one of the
3743 language file you have selected on phpMyAdmin's start page.
3744 Alternatively, you can try the auto detection mode that is supported by the
3745 recent versions of the most browsers.</p>
3748 <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
3751 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3752 Netscape and Mozilla do not have this problem.</p>
3755 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3756 I cannot manage two servers: I log in to the first one, then the other one,
3757 but if I switch back to the first, I have to log in on each operation.</a></h4>
3763 but nothing happens after that, only a blank screen.</a></h4>
3774 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3779 address and you are starting
3781 containing a domain name, or the reverse situation.</li>
3782 <li>Security settings in IE and/or Microsoft Security Center are
3783 too high, thus blocking scripts execution.</li>
3784 <li>The Windows Firewall is blocking Apache and MySQL. You must
3788 </ul>
3791 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3792 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3793 installed in their Firefox is causing the problem.</p>
3797 clause is generated when I browse a table.</a></h4>
3798 <p> This happens only when both of these conditions are met: using the
3808 </a></h4>
3809 <p>
3810 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3811 specifying a wrong field-type.<br />
3812 Common errors include:
3813 </p>
3814 <ul>
3817 </ul>
3818 <p>
3819 Also, look at the syntax chapter in the MySQL manual to confirm that your
3820 syntax is correct.
3821 </p>
3825 phpMyAdmin generates only one index with those two fields.
3826 </a></h4>
3827 <p>
3828 This is the way to create a multi-fields
3829 index. If you want two indexes, create the first one when creating the
3830 table, save, then display the table properties and click the Index link to
3831 create the other index.
3832 </p>
3836 <p>
3837 Since version 2.2.3, you have a checkbox for each field that can be null.
3839 field's value. Since version 2.5.5, you have to use the checkbox to get
3841 a literal NULL in the field, and not a NULL value (this works in PHP4).
3842 </p>
3847 <p> Click on a database or table name in the left frame, the properties will be
3849 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3850 statements that can be used to recreate your database/table.
3851 <br /><br />
3853 transmit the resulting dump to your station. Depending on your PHP
3854 configuration, you will see options to compress the dump. See also the
3856 configuration variable.<br /><br />
3859 this document.</p>
3864 </a></h4>
3866 <p> Click on a database name in the left frame, the properties will be
3868 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3870 the path to your dump filename, or use the Browse button. Then click Go.
3871 <br /><br />
3873 that you upgrade to take advantage of the new features.
3874 <br /><br />
3876 in this document.
3877 </p>
3882 <p> Here is an example with the tables persons, towns and countries, all
3884 table, create it as explained in the configuration section. Then create the
3885 example tables:</p>
3887 <pre>
3888 CREATE TABLE REL_countries (
3889 country_code char(1) NOT NULL default '',
3890 description varchar(10) NOT NULL default '',
3891 PRIMARY KEY (country_code)
3892 ) TYPE=MyISAM;
3894 INSERT INTO REL_countries VALUES ('C', 'Canada');
3896 CREATE TABLE REL_persons (
3897 id tinyint(4) NOT NULL auto_increment,
3898 person_name varchar(32) NOT NULL default '',
3900 country_code char(1) NOT NULL default '',
3901 PRIMARY KEY (id)
3902 ) TYPE=MyISAM;
3904 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3905 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3907 CREATE TABLE REL_towns (
3909 description varchar(30) NOT NULL default '',
3910 PRIMARY KEY (town_code)
3911 ) TYPE=MyISAM;
3913 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3914 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3915 </pre>
3921 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3925 </ul>
3933 <li>In the fields row, choose persons.person_name and click the
3935 <li>Do the same for towns.description and countries.descriptions in the
3938 the correct joins have been generated</li>
3940 </ul>
3944 <p>
3945 Starting from the previous example, create the pma_table_info as explained
3946 in the configuration section, then browse your persons table,
3947 and move the mouse over a town code or country code.
3948 <br /><br />
3949 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3950 enables: drop-down list of possible values.
3951 </p>
3954 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3955 <p>
3958 <br /><br />
3959 Then you need to think about your schema layout. Which tables will go on
3960 which pages?
3961 </p>
3962 <ul>
3968 page and click Go. If you like, you
3970 linked tables onto the new page.</li>
3971 <li>Select the name of the new page (making sure the Edit radio button
3972 is selected) and click Go.</li>
3974 Coordinates are relative; your diagram will
3975 be automatically scaled to fit the page. When initially placing tables
3976 on the page, just pick any coordinates -- say, 50x50. After clicking
3978 position the element correctly.</li>
3980 first be sure to click the Save
3981 button beneath the list of tables and coordinates, to save any changes
3982 you made there. Then scroll all the way down, select the
3984 you want, and click Go.</li>
3985 <li>Internet Explorer for Windows may suggest an incorrect filename when
3990 browsers on Windows, do not have this problem.</li>
3991 </ul>
3995 columns!</a></h4>
3997 <p> No, it's MySQL that is doing
4003 underscores in the database name?</a></h4>
4005 <p> If you do not put a backslash before the underscore, this is a wildcard
4008 john2db ...<br /><br />
4010 If you put a backslash before the underscore, it means that the database
4011 name will have a real underscore.</p>
4015 statistics pages?</a></h4>
4026 if it already exists during the import. It does NOT drop the table after
4027 your export, it only affects the import file.</li>
4029 Otherwise, you may get an error if the table name exists but has a
4030 different structure.</li>
4032 (if any) will be included in backup.</li>
4034 field and table names formed with special characters are protected.</li>
4036 types set in the pmadb in the dump as
4038 </li>
4039 </ul>
4044 command, for better documentation (but resulting file is bigger).</li>
4046 once the INSERT verb and the table name.</li>
4049 </li>
4051 more info is provided in the
4053 but basically with this selected, invalid values are adjusted and
4054 inserted rather than causing the entire statement to fail.</li>
4055 </ul>
4059 in its name.</a></h4>
4062 is the normal way to reference a database and table name. Worse, MySQL
4063 will usually let you create a database with a dot, but then you cannot
4064 work with it, nor delete it.</p>
4077 for usage.<br />
4078 On a more recent pear version, I had problems with the state of Net_DIME
4079 being beta, so this single command
4081 needed modules.<br />
4082 If you use the Validator, you should be aware that any
4084 submit will be stored anonymously (database/table/column names,
4085 strings, numbers replaced with generic values). The Mimer
4088 We utilize it as free SOAP service.</p>
4092 it, but MySQL says "BLOB column '...' used in key specification without
4095 <p> The right way to do this, is to create the field without any indexes,
4097 dialog. On this page, you will be able to choose your BLOB field, and
4098 set a size to the index, which is the condition to create an index on
4099 a BLOB field.</p>
4103 editing fields?</a></h4>
4105 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4106 with many editing fields (table structure changes, row editing, etc.)
4107 (must be enabled in configuration - see.
4109 You can also have a look at the directive
4111 ('vertical') and see if this eases up editing for you.</p>
4115 WTF is this feature then useful for?</a></h4>
4117 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4118 on them. Otherwise you could just put a comment on the field. Because entering
4119 your own mimetype will cause serious syntax checking issues and validation,
4120 this introduces a high-risk false-user-input situation. Instead you have to
4121 initialize mimetypes using functions or empty mimetype definitions.<br />
4122 Plus, you have a whole overview of available mimetypes. Who knows all those
4123 mimetypes by heart so he/she can enter it at will?</p>
4127 can't I see any bookmarks below the query box? What is this variable for?
4128 </a></h4>
4130 <p> Any query you have executed can be stored as a bookmark on the page where the
4131 results are displayed. You will find a button labeled 'Bookmark this query'
4132 just at the end of the page.<br />
4133 As soon as you have stored a bookmark, it is related to the database you run
4134 the query on. You can now access a bookmark dropdown on each page, the query
4135 box appears on for that database.<br /><br />
4137 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4141 aware of that you HAVE to create a valid query, otherwise your query won't be
4142 even able to be stored in the database.<br />
4144 for your query will remain the way it is, but will be stripped of the /**/
4145 chars. So you can use:<br /><br />
4149 which will be expanded to<br /><br />
4153 in your query, where VARIABLE is the string you entered in the input box. If
4154 an empty string is provided, no replacements are made.<br /><br />
4156 A more complex example. Say you have stored this query:<br /><br />
4158 <br /><br />
4161 the full query will be:<br /><br />
4164 <br /><br />
4168 spaces inserted there
4169 will be later also inserted as spaces in your query and may lead to unexpected
4170 results especially when
4172 Your initial query which is going to be stored as a bookmark has to yield at
4173 least one result row so
4174 you can store the bookmark. You may have that to work around using well
4178 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4179 include exported table?</a></h4>
4181 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4182 document should look like following one (assuming you have table
4185 <pre>
4186 \documentclass{article} % or any class you want
4187 \usepackage{longtable} % for displaying table
4188 \begin{document} % start of document
4189 \include{table} % including exported table
4190 \end{document} % end of document
4191 </pre>
4195 access them.
4196 </a></h4>
4198 <p> You have one of these global privileges: CREATE
4199 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4200 enable users to see all the database names.
4203 So if your users do not need those privileges, you can remove them and their
4204 databases list will shorten.</p>
4208 possible values for a field, based on some foreign table?</a></h4>
4210 <p> You have to setup appropriate links between the tables, and also
4214 foreign table, a drop-down list of values will be available.
4215 You will see two lists of values, the first list containing the key
4216 and the display field, the second list containing the display field
4217 and the key. The reason for this is to be able to type the first
4218 letter of either the key or the display field.<br /><br />
4220 For 100 values or more, a distinct window will appear, to browse foreign
4221 key values and choose one. To change the default limit of 100, see
4222 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4226 automatically when entering Browse mode for a table?</a></h4>
4228 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4229 </p>
4233 Excel files, how can I enable that?</a></h4>
4235 <p> You can use
4237 which works out of the box, but phpMyAdmin supports direct export
4238 to Microsoft Excel version 97 and newer. For this to work, you need to set
4243 <pre>
4244 cd phpMyAdmin
4245 mkdir tmp
4246 chmod o+rwx tmp
4247 </pre>
4251 what happens to my column comments stored in pmadb?</a></h4>
4253 <p> Automatic migration of a table's pmadb-style column comments to the native
4254 ones is done whenever you enter Structure page for this table.</p>
4259 <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>
4261 <ol>
4262 <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>
4263 <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>
4264 <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>
4265 <li>Ensure that your target table is under the PBXT storage engine and has a LONGBLOB column.</li>
4266 <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>
4267 <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>
4268 </ol>
4273 <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>
4281 <p> Our Bug Tracker is located at
4283 under the Bugs section.<br /><br />
4285 But please first discuss your bug with other users:<br />
4291 existing language, where do I start?</a></h4>
4293 <p> Always use the current SVN version of your language file.
4295 don't know how to get the SVN version, please ask one of the developers.
4296 <br />
4297 Please note that we try not to use HTML entities like &eacute; in
4298 the translations, since we define the right character set in the file.
4299 With HTML entities, the text on JavaScript messages would not
4300 display correctly.
4301 However there are some entities that need to be there, for quotes
4302 ,non-breakable spaces, ampersands, less than, greater than.<br />
4303 You can then put your translations, as a zip file to avoid losing special
4304 characters, on the sourceforge.net translation tracker.<br />
4305 It would be a good idea to subscribe to the phpmyadmin-translators mailing
4306 list, because this is where we ask for translations of new messages.</p>
4310 phpMyAdmin. How should I proceed?</a></h4>
4315 <tt>git clone
4316 git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin</tt><br />
4317 </li>
4319 <li>generate patch with your changes:
4321 </li>
4324 tracker of the phpMyAdmin project</a>.
4325 </li>
4326 </ol>
4328 <p>More details on git are available on <a href="http://wiki.phpmyadmin.net/pma/Devel:Git">our wiki</a>.</p>
4330 <p> Write access to the repository is granted only to experienced developers who
4331 have already contributed something useful to phpMyAdmin.<br />
4337 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4339 <p> Please refer to
4340 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4341 </p>
4346 <p> If you use Apache web server, phpMyAdmin exports information about
4347 authentication to Apache environment and it can be used in Apache logs.
4348 Currently there are two variables available:
4349 </p>
4350 <dl>
4352 <dd>User name of currently active user (he does not have to be logged
4353 in).</dd>
4360 </dl>
4361 <p>
4363 </p>
4364 <pre>
4367 </pre>
4368 <p>
4369 You can then use any log analyzing tools to detect possible break-in
4370 attempts.
4371 </p>
4377 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4378 It allows you to connect to local as well as remote servers.This requires you to enter
4379 server host name, username, password, port and the name of the database. Therefore you can
4380 now synchronize your databases placed on the same server or some remote server.
4381 </p>
4383 <p>For more details see <a href="./documentation-gsoc/Synchronization_User_Manual.htm">How to synchronize</a>
4384 </p>
4386 <!-- DEVELOPERS -->
4389 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4390 great features have been written by other people and you too can help to
4391 make phpMyAdmin a useful tool.</p>
4393 <p> If you're planning to contribute source, please read the following
4394 information:</p>
4400 it free from other code.<br />
4401 Commonly used functions should be added to
4404 <li>Obviously, you're free to use whatever coding style you want. But
4405 please try to keep your code as simple as possible: beginners are
4406 using phpMyAdmin as an example application.<br />
4407 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4408 compliant on one hand, they fit the
4411 coding standards</a>
4412 on the other hand. Please pay attention to this.</li>
4413 <li>Please enable showing PHP errors and warnings by the
4415 configuration directive.</li>
4416 <li>Please try to keep up the file-naming conventions. Table-related stuff
4419 <li>Please don't put message strings in your code, instead add the string
4424 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4425 better debug and profile their code.<br />
4426 Please see the
4428 options for more information.<br />
4429 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4430 lost during its re-entry into Earth's atmosphere and in memory of the
4431 brave men and women who gave their lives for the people of Earth.</li>
4432 </ul>
4436 <pre>
4447 </pre>
4449 <p>
4450 This program is free software; you can redistribute it and/or modify
4451 it under the terms of the GNU General Public License version 2,
4452 as published by the Free Software Foundation.
4453 </p>
4455 <p>
4456 This program is distributed in the hope that it will be useful,
4457 but WITHOUT ANY WARRANTY; without even the implied warranty of
4458 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4459 GNU General Public License for more details.
4460 </p>
4462 <p>
4463 You should have received a copy of the GNU General Public License
4464 along with this program; if not, write to the Free Software
4466 </p>
4468 <!-- CREDITS -->
4473 <ul>
4476 <ul>
4479 </ul></li>
4482 <ul>
4487 </ul></li>
4490 <ul>
4496 </ul></li>
4499 <ul>
4501 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4502 generate XHTML1.0 and CSS2 compliant codes</li>
4505 </ul></li>
4508 <ul>
4516 </ul></li>
4519 <ul>
4524 </ul></li>
4527 <ul>
4530 </ul></li>
4533 <ul>
4535 </ul></li>
4538 <ul>
4541 </ul></li>
4544 <ul>
4548 </ul></li>
4551 <ul>
4554 </ul></li>
4557 <ul>
4564 </ul></li>
4567 <ul>
4571 </ul></li>
4574 <ul>
4580 </ul></li>
4583 (http://sf.net/projects/phpmysqlformgen/)
4584 <ul>
4586 </ul></li>
4589 <ul>
4591 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4596 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4600 </ul></li>
4603 <ul>
4605 </ul></li>
4608 <ul>
4610 </ul></li>
4613 <ul>
4615 </ul></li>
4618 <ul>
4619 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4620 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4621 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4622 </ul></li>
4625 <ul>
4627 </ul></li>
4630 <ul>
4632 </ul></li>
4635 <ul>
4637 </ul></li>
4640 <ul>
4643 </ul></li>
4646 <ul>
4649 </ul></li>
4652 <ul>
4654 </ul></li>
4657 <ul>
4660 </ul></li>
4662 <li>Ivan A Kirillov
4663 <ul>
4665 </ul></li>
4668 <ul>
4670 </ul></li>
4673 <ul>
4675 </ul></li>
4678 <ul>
4680 </ul></li>
4683 <ul>
4685 </ul></li>
4688 <ul>
4690 </ul></li>
4693 <ul>
4695 </ul></li>
4697 </ul>
4699 <p>
4700 And also to the following people who have contributed minor changes,
4701 enhancements, bugfixes or support for a new language since version 2.1.0:
4702 </p>
4704 <p>
4705 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4706 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4707 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4708 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4710 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4711 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4712 Luís V., Martijn W. van der Lee,
4713 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4715 </p>
4720 <p>
4721 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4722 to create a web-based interface to MySQL using PHP3. Although I have not
4723 used any of his source-code, there are some concepts I've borrowed from
4724 him. phpMyAdmin was created because Peter told me he wasn't going to
4725 further develop his (great) tool.
4726 </p>
4727 <p>
4728 Thanks go to
4729 </p>
4730 <ul>
4732 code for the check when dropping a table or database. He also suggested
4733 that you should be able to specify the primary key on tbl_create.php3. To
4734 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4735 well as a bug-report. Plus many smaller improvements.
4736 </li>
4738 were introduced in 1.3.0 (including quite significant ones like the
4739 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4740 bug-fixes and help.
4741 </li>
4743 language-independent by outsourcing the strings to a separate file. He
4744 also contributed the French translation.
4745 </li>
4747 tbl_select.php3, a feature to display only some fields from a table.
4748 </li>
4750 functions in tbl_change.php3. He also added the
4752 </li>
4754 servers and is a regular contributor for bug-fixes.
4755 </li>
4757 features for 2.0.6.
4758 </li>
4759 </ul>
4760 <p>
4761 The following people have contributed minor changes, enhancements, bugfixes
4762 or support for a new language:
4763 </p>
4764 <p>
4765 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4766 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4767 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4768 G. Wieggers.
4769 </p>
4770 <p>
4771 And thanks to everyone else who sent me email with suggestions, bug-reports
4772 and or just some feedback.
4773 </p>
4779 <ul>
4781 - the default name of Apache's directory-level configuration file.</li>
4785 - a software application that enables a user to display and interact with
4786 text, images, and other information typically located on a web page at a
4787 website on the World Wide Web.</li>
4789 - a free software/open source data compression algorithm and program
4790 developed by Julian Seward.</li>
4792 - an important World Wide Web technology that enables a client web browser
4793 to request data from a program executed on the Web server.</li>
4795 - a log or record of changes made to a project.</li>
4797 - a computer system that accesses a (remote) service on another computer
4798 by some kind of network.</li>
4800 - a set of data values of a particular simple type, one for each row of
4801 the table.</li>
4803 - a packet of information sent by a server to a World Wide Web browser
4804 and then sent back by the browser each time it accesses that server.</li>
4806 - Comma-separated values</li>
4809 - an organized collection of data.</li>
4812 - a PHP module that extends PHP with additional functionality.</li>
4814 - a list of commonly asked question and there answers.</li>
4816 - one part of divided data/columns.</li>
4818 - a field or group of fields in a database record that point to a key
4819 field or group of fields forming a key of another database record in some
4820 (usually different) table.</li>
4822 - the free PDF library</li>
4824 GD Graphics Library</a> - a library by Thomas Boutell and others for
4825 dynamically manipulating images.</li>
4828 - gzip is short for GNU zip, a GNU free software file compression
4829 program.</li>
4831 - any machine connected to a computer network, a node that has a hostname.</li>
4833 - the unique name by which a network attached device is known on a network.</li>
4835 (HyperText Transfer Protocol)</a>
4836 - the primary method used to transfer or convey information on the World
4837 Wide Web.</li>
4840 additional security measures.</li>
4841 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4842 - a set of Internet-based services for servers using Microsoft Windows.</li>
4844 - a feature that allows quick access to the rows in a table.</li>
4846 - a data-oriented protocol used by source and destination hosts for
4847 communicating data across a packet-switched internetwork.</li>
4849 - a unique number that devices use in order to identify and communicate
4850 with each other on a network utilizing the Internet Protocol standard.</li>
4852 (Internet Server Application Programming Interface)</a>
4853 - the API of Internet Information Services (IIS).</li>
4855 - a business or organization that offers users access to the Internet and related services.</li>
4857 - a most commonly used standard method of lossy compression for
4858 photographic images.</li>
4864 - line of personal computers is designed, developed, manufactured, and
4865 marketed by Apple Computer.</li>
4866 <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>
4867 - the operating system which is included with all currently shipping Apple
4868 Macintosh computers in the consumer and professional markets.</li>
4870 - a cryptographic library.</li>
4872 - the MCrypt PHP extension.</li>
4873 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4874 - an Internet Standard for the format of e-mail.</li>
4876 - some sort of extension for the Apache Webserver.</li>
4878 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4879 Management System (DBMS).</li>
4881 - the improved MySQL client PHP extension.</li>
4883 - the MySQL client PHP extension.</li>
4885 - open standard for office documents.</li>
4886 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4887 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4889 (Portable Document Format)</a>
4890 - a file format developed by Adobe Systems for representing two
4891 dimensional documents in a device independent and resolution independent
4892 format.</li>
4894 - the PHP Extension and Application Repository.</li>
4896 - the perl-compatible regular expression functions for PHP</li>
4898 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4899 programming language used mainly for developing server-side applications
4900 and dynamic web content, and more recently, a broader range of software
4901 applications.</li>
4903 - a connection through which data is sent and received.</li>
4905 - Request for Comments (RFC) documents are a series of memoranda
4906 encompassing new research, innovations, and methodologies applicable to
4907 Internet technologies.</li>
4911 - represents a single, implicitly structured data item in a table.</li>
4913 - a computer system that provides services to other computing
4914 systems over a network.</li>
4915 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4916 - handlers for different table types</li>
4918 - a form of inter-process communication.</li>
4920 Sockets Layer)</a>
4921 - a cryptographic protocol which provides secure communication on the Internet.</li>
4923 - Structured Query Language</li>
4925 - a set of data elements (cells) that is organized, defined and stored as
4926 horizontal rows and vertical columns where each item can be uniquely
4927 identified by a label or key or by it?s position in relation to other items.</li>
4930 - a type of archive file format: the Tape ARchive format.</li>
4932 - one of the core protocols of the Internet protocol suite.</li>
4936 - a sequence of characters, conforming to a standardized format, that is
4937 used for referring to resources, such as documents and images on the
4938 Internet, by their location.</li>
4940 - A computer (program) that is responsible for accepting HTTP requests
4941 from clients and serving them Web pages.</li>
4943 - a W3C-recommended general-purpose markup language for creating
4944 special-purpose markup languages, capable of describing many different
4945 kinds of data.</li>
4947 - a popular data compression and archival format.</li>
4949 - an open-source, cross-platform data compression library by Jean-loup
4950 Gailly and Mark Adler.</li>
4951 </ul>
4952 </div>
4955 <li>Copyright © 2003 - 2010 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
4958 <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>
4959 </ul>
4961 </body>
4962 </html>