| blob | 34f1bbd594ec7af8806b3087df589e8374adda78 |
3 <!--
4 vim: expandtab ts=4 sw=4 sts=4 tw=78
5 -->
8 <!-- $Id$ -->
9 <head>
15 </head>
19 <h1>
21 3.3.2-dev
22 Documentation
23 </h1>
24 </div>
26 <!-- TOP MENU -->
35 <li><a href="Documentation.html#faq"><abbr title="Frequently Asked Questions"> FAQ</abbr></a></li>
41 </ul>
46 phpMyAdmin homepage</a></li>
48 SourceForge phpMyAdmin project page</a></li>
50 Official phpMyAdmin wiki</a></li>
51 <li>Local documents:
54 </ul>
55 </li>
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 4.1.2 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
384 in this area!<br />
387 that your user/password pair are not in clear in the configuration file.
388 </li>
391 authentication modes are more secure: the MySQL login information does
392 not need to be set in the phpMyAdmin configuration file (except possibly
394 However, keep in mind that the password travels in plain text, unless
395 you are using the HTTPS protocol.<br />
396 In cookie mode, the password is stored, encrypted with the blowfish
397 algorithm, in a temporary cookie.</li>
409 file under the
411 $cfg['Servers'][$i]['controluser']</a></tt> and
416 only an example: use something else in your file!</b> Input these
417 statements from the phpMyAdmin SQL Query window or mysql command–line
418 client.<br />
420 if it's not the same as the MySQL server's one.
422 <pre>
423 GRANT USAGE ON mysql.* TO 'pma'@'localhost' IDENTIFIED BY 'pmapass';
424 GRANT SELECT (
425 Host, User, Select_priv, Insert_priv, Update_priv, Delete_priv,
426 Create_priv, Drop_priv, Reload_priv, Shutdown_priv, Process_priv,
427 File_priv, Grant_priv, References_priv, Index_priv, Alter_priv,
428 Show_db_priv, Super_priv, Create_tmp_table_priv, Lock_tables_priv,
429 Execute_priv, Repl_slave_priv, Repl_client_priv
430 ) ON mysql.user TO 'pma'@'localhost';
431 GRANT SELECT ON mysql.db TO 'pma'@'localhost';
432 GRANT SELECT ON mysql.host TO 'pma'@'localhost';
433 GRANT SELECT (Host, Db, User, Table_name, Table_priv, Column_priv)
434 ON mysql.tables_priv TO 'pma'@'localhost';</pre>
436 If you want to use the many new relation and bookmark features:
438 <pre>
440 </pre>
446 on a set of particular databases. Normally you shouldn't give global
447 privileges to an ordinary user, unless you understand the impact of those
448 privileges (for example, you are creating a superuser).<br />
452 <pre>
453 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
454 </pre>
456 What the user may now do is controlled entirely by the MySQL user
457 management system.<br />
459 authentication mode, you don't need to fill the user/password fields
461 array.</li>
462 </ul>
467 method and allows you to log in as any valid MySQL user.</li>
468 <li>Is supported with most PHP configurations. For
481 mode.</li>
482 </ul>
486 <ul><li>You can use this method as a replacement for the
488 (for example, if you're running
490 <li>Obviously, the user must enable cookies in the browser, but this is
491 now a requirement for all authentication modes.</li>
492 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
493 with the same username.</li>
494 <li>If you want to log in to arbitrary server see
499 not required.</li>
500 </ul>
504 <ul><li>This mode is a convenient way of using credentials from another
505 application to authenticate to phpMyAdmin.</li>
506 <li>The other application has to store login information into
507 session data.</li>
509 section.</li>
510 </ul>
513 <ul><li>This mode is the less secure one because it requires you to fill the
515 $cfg['Servers'][$i]['user']</a> and
517 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
518 can read your config.inc.php can discover your username and password).
519 <br />
526 is an entry explaining how to protect your configuration file.</li>
527 <li>For additional security in this mode, you may wish to consider the Host
528 authentication
530 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
532 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
533 directives.</li>
534 <li>Unlike cookie and http, does not require a user to log in when first
535 loading the phpMyAdmin site. This is by design but could allow any
536 user to access your installation. Use of some restriction method is
538 HTTP-AUTH directive or disallowing incoming HTTP requests at
539 one’s router or firewall will suffice (both of which
540 are beyond the scope of this manual but easily searchable with Google).</li>
541 </ul>
543 <p>
544 The Swekey is a low cost authentication USB key that can be used in
545 web applications.<br /><br />
546 When Swekey authentication is activated, phpMyAdmin requires the
547 users's Swekey to be plugged before entering the login page (currently
548 supported for cookie authentication mode only). Swekey Authentication is
549 disabled by default.<br /><br />
551 </p>
552 <pre>
553 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
554 </pre>
555 <p>
557 each user with their Swekey Id. It is important to place this file outside
558 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
560 users' information.<br /><br />
561 If you want to purchase a Swekey please visit
563 since this link provides funding for phpMyAdmin.
564 </p>
565 <!-- CONFIGURATION -->
569 users:</span> PHP does not seem to like
573 before saving a script you have modified.</p>
578 section to create one. This file only needs to contain the parameters you want to
579 change from their corresponding default value in
582 <p> The parameters which relate to design (like colors) are placed in
585 your site specific code to be included on start and end of each page.</p>
589 (with full path) to your phpMyAdmin installation's directory.
592 some web servers are case–sensitive.
595 Starting with version 2.3.0, it is advisable to try leaving this
596 blank. In most cases phpMyAdmin automatically detects the proper
597 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
598 href="https://sourceforge.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
599 A good test is to browse a table, edit a row and save it. There should
600 be an error message if phpMyAdmin is having trouble auto–detecting
601 the correct value. If you get an error that this must be set or if
602 the autodetect code fails to detect your path, please post a bug
603 report on our bug tracker so we can improve the code.</dd>
607 with master / foreign – tables (see
609 <br />
610 If you tried to set this up and it does not work for you, have a look on
612 use it. You will find a link that will analyze why those features have
613 been disabled.<br />
614 If you do not want to use those features set this variable to
618 <dd>A warning is displayed on the main page if Suhosin is detected.
620 from appearing.</dd>
623 <dd>Disable the default warning that is displayed if mcrypt is missing for
624 cookie authentication.
626 from appearing.</dd>
630 domain to call phpMyAdmin inside a frame, and is a potential security
631 hole allowing cross-frame scripting attacks.</dd>
635 algorithm to encrypt the password.<br />
637 passphrase of your choice. It will be used internally by the blowfish
638 algorithm: you won’t be prompted for this passphrase. There is
639 no maximum length for this secret.<br /><br />
641 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
642 makes a bit weaker security as this generated secret is stored in
643 session and furthermore it makes impossible to recall user name from
644 cookie.</dd>
648 MySQL servers. Therefore, a
650 been added which contains the login information for the different servers.
651 The first
653 contains the hostname of the first server, the second
655 the hostname of the second server, etc. In
657 server definition, however you can put as many as you need in
659 have to define all settings, just those you need to change).</dd>
663 $i-th MySQL-server. E.g. localhost.</dd>
668 ignores this port number and connects with the socket, so if you want
669 to connect to a port different from the default port, use
672 </dd>
676 To determine the correct socket, check your MySQL configuration or, using the
678 Among the resulting information displayed will be the socket used.</dd>
681 <dd>Whether to enable SSL for connection to MySQL server.
682 </dd>
685 <dd>What type connection to use with the MySQL server. Your options are
687 is nearly guaranteed to be available on all MySQL servers, while
688 sockets are not supported on some platforms.<br /><br />
690 To use the socket mode, your MySQL server must be on the same machine
691 as the Web server.</dd>
694 <dd>What php MySQL extension to use for the connection. Valid options are:
695 <br /><br />
698 The classic MySQL extension. This is the recommended and default
699 method at this time.<br /><br />
702 The improved MySQL extension. This extension became available
703 with php 5.0.0 and is the recommended way to connect to a server
707 <dd>Whether to use a compressed protocol for the MySQL server connection
708 or not (experimental).<br />
714 </dt>
716 all relational features (see
718 and, for a MySQL server previous to 4.1.2 or running with
721 authentication mode).<br /><br />
724 cookie authentication modes (or 'config'
725 authentication mode since phpMyAdmin 2.2.1), you need to supply the
730 This account is used to check what databases the user will see at
731 login.<br />
735 In phpMyAdmin versions before 2.2.5, those were called
739 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
740 <dd>Whether config or cookie or
742 should be used for this server.
744 is the plain old way: username and password are stored in
746 <li>'cookie' authentication mode
748 2.2.3 allows you to log in as any valid MySQL user with the
749 help of cookies. Username and password are stored in
750 cookies during the session and password is deleted when it
751 ends. This can also allow you to log in in arbitrary server if
752 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
753 </li>
754 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
755 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
756 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
757 <li>'signon' authentication mode
759 as introduced in 2.10.0 allows you to log in from prepared PHP
760 session data. This is useful for implementing single signon
761 from another application. Sample way how to seed session is in
767 </ul>
770 for more information.
771 </dd>
773 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
774 </dt>
775 <dd>
777 names for hardware authentication. Leave empty to deactivate this feature.
778 </dd>
782 </dt>
783 <dd>
784 When using auth_type = 'config', this is the user/password-pair
785 which phpMyAdmin will use to connect to the
786 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
787 cookie authentication is used and should be empty.</dd>
789 <span
791 </dt>
792 <dd>
793 Allow attempt to log in without password when a login with password
794 fails. This can be used together with http authentication, when
795 authentication is done some other way and phpMyAdmin gets user name
796 from auth and uses empty password for connecting to MySQL. Password
797 login is still tried first, but as fallback, no password method is
798 tried.</dd>
801 </dt>
802 <dd>
803 If set to a (an array of) database name(s), only this (these) database(s)
804 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
805 database(s) name(s) may contain MySQL wildcards characters
809 This setting is an efficient way to lower the server load since the
810 latter does not need to send MySQL requests to build the available
812 privileges rules of the MySQL database server</span>. If set, it just
813 means only these databases will be displayed but
815 <br /><br />
817 An example of using more that one database:
819 <br /><br />
821 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
822 databases in the left frame, so that you can individually arrange your databases.<br />
823 If you want to have certain databases at the top, but don't care about the others, you do not
824 need to specify all other databases. Use:
826 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
827 order.</dd>
830 </dt>
831 <dd>Regular expression for hiding some databases. This only hides them
832 from listing, but a user is still able to access them (using, for example,
833 the SQL query area). To limit access, use the MySQL privilege system.
834 <br /><br />
839 More information on regular expressions can be found in the
841 PCRE pattern syntax</a> portion of the PHP reference manual.
842 </dd>
845 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
846 this string will be displayed instead of the hostname in the pull-down
847 menu on the main page. This can be useful if you want to show only
848 certain databases on your system, for example. For HTTP auth, all
849 non-US-ASCII characters will be stripped.</dd>
853 </dt>
854 <dd>The name of the database containing the linked-tables infrastructure.
855 <br /><br />
858 section in this document to see the benefits of this infrastructure,
859 and for a quick way of creating this database and the needed tables.
860 <br /><br />
862 If you are the only user of this phpMyAdmin installation, you can
863 use your current database to store those special tables; in this
864 case, just put your current database name in
866 set this parameter to the name of your central database containing
867 the linked-tables infrastructure.</dd>
871 </dt>
873 useful for queries you often run.<br /><br />
875 To allow the usage of this functionality:
877 <li>enter the table name in
879 </ul>
880 </dd>
884 </dt>
886 which field is a key in another table (a foreign key). phpMyAdmin
887 currently uses this to
888 <ul><li>make clickable, when you browse the master table, the data values
889 that point to the foreign table;</li>
891 when browsing the master table, if you move the mouse to a column
892 containing a foreign key (use also the 'table_info' table);<br />
895 <li>in edit/insert mode, display a drop-down list of possible foreign
899 <li>display links on the table properties page, to check referential
900 integrity (display missing foreign keys) for each described key;
901 </li>
905 schema of your database (also uses the table_coords table).</li>
906 </ul>
908 The keys can be numeric or character.<br /><br />
910 To allow the usage of this functionality:
913 infrastructure</li>
914 <li>put the relation table name in
916 <li>now as normal user open phpMyAdmin and for each one of your
917 tables where you want to use this feature, click
919 </li>
920 </ul>
924 future development of the cross-db relations.
925 </dd>
929 </dt>
930 <dd>
931 Since release 2.3.0 you can describe, in a special 'table_info'
932 table, which field is to be displayed as a tool-tip when moving the
933 cursor over the corresponding key.<br />
934 This configuration variable will hold the name of this special
935 table. To allow the usage of this functionality:
937 <li>put the table name in
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
1000 <pre>
1001 ALTER TABLE `pma_column_comments`
1002 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1003 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1004 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1005 </pre>
1008 renamed from<br />
1011 </ul>
1012 </dd>
1016 </dt>
1019 all queries you entered manually into the phpMyAdmin interface. If you
1020 don't want to use a table-based history, you can use the JavaScript-based
1021 history. Using that, all your history items are deleted when closing the
1022 window.<br /><br />
1024 Using
1026 you can specify an amount of history items you want to have on hold. On
1027 every login, this list gets cut to the maximum amount.<br /><br />
1029 The query history is only available if JavaScript is enabled in your
1030 browser.<br /><br />
1032 To allow the usage of this functionality:
1035 infrastructure</li>
1037 </li>
1038 </ul>
1039 </dd>
1043 </dt>
1044 <dd>
1045 Since release 3.3.x a tracking mechanism is available.
1047 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1048 and data definition statements. After enabling it you can create versions of tables.
1049 <br/><br/>
1050 The creation of a version has two effects:
1052 <ul>
1054 <li>phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1055 </ul>
1057 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1058 For the report you can use filters, for example you can get a list of statements within a date range.
1059 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1060 In addition you can export the (filtered) report to a file or to a temporary database.
1061 <br/><br/>
1063 To allow the usage of this functionality:
1065 <ul>
1068 </ul>
1069 </dd>
1072 <span id="cfg_Servers_tracking_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1073 </dt>
1074 <dd>
1075 Whether the tracking mechanism creates versions for tables and views automatically. Default value is false.
1076 <br/><br/>
1077 If this is set to true and you create a table or view with
1079 <ul>
1082 </ul>
1084 and no version exists for it, the mechanism will
1085 create a version for you automatically.
1086 </dd>
1089 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1090 </dt>
1091 <dd>
1092 Defines the list of statements the auto-creation uses for new versions. Default value is
1093 <br/>
1095 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1096 CREATE INDEX,DROP INDEX,
1097 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1098 CREATE VIEW,ALTER VIEW,DROP VIEW,
1099 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1100 </dd>
1103 <span id="cfg_Servers_tracking_drop_view">$cfg['Servers'][$i]['tracking_version_drop_view']</span> boolean
1104 </dt>
1105 <dd>
1106 Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view. Default value is true.
1107 <br/><br/>
1108 </dd>
1112 <span id="cfg_Servers_tracking_drop_table">$cfg['Servers'][$i]['tracking_version_drop_table']</span> boolean
1113 </dt>
1114 <dd>
1115 Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table. Default value is true.
1116 <br/><br/>
1117 </dd>
1120 <span id="cfg_Servers_tracking_drop_database">$cfg['Servers'][$i]['tracking_version_drop_database']</span> boolean
1121 </dt>
1122 <dd>
1123 Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database. Default value is true.
1124 <br/><br/>
1125 </dd>
1130 </dt>
1132 to visually manage the relations.
1133 <br /><br />
1135 To allow the usage of this functionality:
1138 infrastructure</li>
1140 </li>
1141 </ul>
1142 </dd>
1145 </dt>
1147 column_info table got enhanced with three new fields. If the above variable
1149 latest table structure available. If not, it will emit a warning to the
1150 superuser.<br /><br />
1152 You can disable this checking behavior by setting the variable to false,
1153 which should offer a performance increase.<br /><br />
1155 Recommended to set to FALSE, when you are sure, your table structure is
1156 up to date.</dd>
1158 boolean</dt>
1159 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1160 </dd>
1162 boolean</dt>
1163 <dd>Whether to allow logins without a password. The default
1165 to a MySQL server with was left with an empty password for root or
1166 on which an anonymous (blank) user is defined.
1167 </dd>
1170 </dt>
1172 authentication is disabled.<br /><br />
1175 all deny rules followed by allow rules. Access is allowed by default. Any
1176 client which does not match a Deny command or does match an Allow command
1177 will be allowed access to the server. <br /><br />
1180 applies all allow rules followed by deny rules. Access is denied by
1181 default. Any client which does not match an Allow directive or does
1182 match a Deny directive will be denied access to the server.<br /><br />
1184 If your rule order is set to 'explicit', the authentication is
1185 performed in a similar fashion to rule order 'deny,allow', with the
1189 and was available in Apache by specifying allow and deny rules without
1190 setting any order.<br /><br />
1192 Please also see <a
1194 address behind proxies.
1195 </dd>
1197 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1198 </dt>
1199 <dd>The general format for the rules is as such:
1201 <pre>
1203 </pre>
1208 well (please note that those containing SERVER_ADDRESS might not be
1209 available on all webservers):
1210 <pre>
1216 </pre>
1218 Having an empty rule list is equivalent to either using
1224 following work:<br />
1226 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1227 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1228 But the following does not work:<br />
1231 Also IPv6 addresses are not supported.
1232 </dd>
1234 <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.
1235 </dd>
1236 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1238 DATABASES</tt> command used to fetch the name of available databases will
1239 probably be too slow, so it can be replaced by faster commands (see
1241 </dd>
1243 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1244 </dd>
1245 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1246 <dd>Name of session which will be used for signon authentication method.
1247 </dd>
1249 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1250 </dd>
1252 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1253 </dd>
1256 <dd>If you have more than one server configured, you can set
1258 that server when phpMyAdmin is started, or set it to 0 to be given a
1259 list of servers without logging in.<br />
1261 MUST be set to that server.</dd>
1264 <dd>The maximum number of database names to be displayed in the
1265 navigation frame and the database list.</dd>
1268 <dd>The maximum number of table names to be displayed in the
1269 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1270 when in Light mode.</dd>
1273 <dd>The maximum number of characters when a SQL query is displayed. The
1274 default limit of 1000 should be correct to avoid the display of tons
1275 of hexadecimal codes that represent BLOBs, but some users have real
1276 SQL queries that are longer than 1000 characters. Also, if a query's
1277 length exceeds this limit, this query is not saved in the history.</dd>
1280 <dd>Defines whether to use GZip output buffering for increased
1282 Set to true/false for enabling/disabling. When set to 'auto' (string),
1283 phpMyAdmin tries to enable output buffering and will automatically disable
1284 it if your browser has some problems with buffering. IE6 with a certain patch
1285 is known to cause data corruption when having enabled buffering.</dd>
1288 <dd>Whether persistent connections should be used or not (mysql_connect or
1289 mysql_pconnect).</dd>
1295 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1296 to zero, no time limit is imposed.<br />
1297 This setting is used while importing/exporting dump files and in the
1298 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1301 <dd>Set the number of bytes a script is allowed to allocate. If set
1302 to zero, no limit is imposed.<br />
1303 This setting is used while importing/exporting dump files and at some
1304 other places in phpMyAdmin so you definitely don't want to put here
1305 a too low value. It has no effect when PHP is running in safe mode.<br />
1306 You can also use any string as in php.ini, eg. '16M'. Ensure
1310 <dd>Mark used tables and make it possible to show databases with locked
1315 generated by phpMyAdmin should be displayed or not.</dd>
1318 <dd>Defines whether normal users (non-administrator) are allowed to
1319 delete their own database or not. If set as FALSE, the link "Drop
1321 mydatabase" will be rejected. Quite practical for
1323 customers.<br />
1324 Please note that this limitation of SQL queries is not as strict as
1325 when using MySQL privileges. This is due to nature of SQL queries
1326 which might be quite complicated. So this choice should be viewed as
1327 help to avoid accidental dropping rather than strict privilege
1328 limitation.</dd>
1332 displayed when you're about to lose data.</dd>
1335 <dd>Define whether the previous login should be recalled or not in cookie
1336 authentication mode.<br /><br />
1338 This is automatically disabled if you do not have configured
1340 </dd>
1343 <dd>Define how long is login cookie valid. Please note that php
1344 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1345 might limit session validity and if session is lost, login cookie is
1347 at least as high is $cfg['LoginCookieValidity'] is set.</dd>
1351 means that it will be kept for existing session. This is recommended
1352 for not trusted environments.</dd>
1355 <dd>If enabled (default), logout deletes cookies for all servers,
1356 otherwise only for current one. Setting this to false makes it easy to
1357 forget to log out from other server, when you are using more of
1358 them.</dd>
1364 <dd>Define whether phpMyAdmin will continue executing a multi-query
1365 statement if one of the queries fails. Default is to abort execution.</dd>
1368 <dd>Define whether phpMyAdmin will output the results of each query of a
1369 multi-query statement embedded into the
1374 <dd>If enabled allows you to log in to arbitrary servers using cookie auth.
1375 <br /><br />
1378 MySQL servers behind the firewall where your
1380 </dd>
1383 <dd>Defines whether to use a select-based menu and display only the current
1384 tables in the left frame (smaller page). Only in Non-Lightmode you can
1385 use the feature to display nested folders using
1387 </dd>
1390 <dd>In light mode, defines whether to display the names of databases (in the
1391 selector) using a tree, see also
1393 </dd>
1396 string or array</dt>
1397 <dd>The string used to separate the parts of the database name when showing
1398 them in a tree. Alternatively you can specify more strings in an array
1399 and all of them will be used as a separator.</dd>
1402 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1403 This means if you have tables like 'first__second__third' this will be
1405 If set to FALSE or empty, the feature is disabled. NOTE: You should
1406 not use this separator at the beginning or end of a
1407 table name or multiple times after another without any other
1408 characters in between.</dd>
1411 <dd>Defines how many sublevels should be displayed when splitting
1412 up tables by the above separator.</dd>
1415 <dd>Defines whether to display table comment as tool-tip in left frame or
1416 not.</dd>
1419 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1420 comment and the real name. That means that if you have a table called
1421 'user0001' and add the comment 'MyName' on it, you will see the name
1422 'MyName' used consequently in the left frame and the tool-tip shows
1423 the real name of the DB.</dd>
1426 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1428 When setting this to 'nested', the Alias of the Tablename is only used
1429 to split/nest the tables according to the
1431 directive. So only the folder is called like the Alias, the tablename itself
1432 stays the real tablename.</dd>
1435 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1438 <dd>Enter URL where logo in the navigation frame will point to.
1439 For use especially with self made theme which changes this.
1448 <dd>Defines whether or not to display a server choice at the top of the left frame.
1449 Defaults to FALSE.</dd>
1451 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1452 Defaults to FALSE (drop-down).</dd>
1454 <dd>Defines whether to display database choice in light navigation frame as links
1455 instead of in a drop-down. Defaults to 'auto' - on main page list is
1456 shown, when database is selected, only drop down is displayed.</dd>
1459 <dd>Defines the tab displayed by default when clicking the small
1460 icon next to each table name in the navigation panel. Possible
1466 <dd>Defines whether or not to display space usage and statistics about databases
1467 and tables.<br />
1468 Note that statistics requires at least MySQL 3.23.3 and that, at this
1469 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1472 <dd>Defines whether to display detailed server information on main page.
1473 You can additionally hide more information by using
1475 </dd>
1480 </dt>
1483 not at the starting main (right) frame. This setting
1484 does not check MySQL commands entered directly.<br /><br />
1486 Please note that to block the usage of phpinfo() in scripts, you
1493 hard coded password value in the configuration file, end users can't
1494 be allowed to change their passwords.</dd>
1497 <dd>Defines whether to suggest a database name on the
1501 <dd>Defines whether navigation bar buttons and the right panel top menu
1502 contain text or symbols only. A value of TRUE displays icons, FALSE
1503 displays text and 'both' displays both icons and text.</dd>
1506 <dd>Defines whether a user should be displayed a
1510 <dd>Number of rows displayed when browsing a result set. If the result set
1517 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1521 option is ticked by default.</dd>
1525 from editing when browsing a table's content. Valid values are:
1530 </ul>
1531 </dd>
1534 <dd>Defines whether or not MySQL functions fields should be initially
1535 displayed in edit/insert mode. Since version 2.10, the user can
1536 toggle this setting from the interface.
1537 </dd>
1540 <dd>Defines which type of editing controls should be used for CHAR and
1541 VARCHAR fields. Possible values are:
1542 <ul><li>input - this allows to limit size of text to size of field in
1543 MySQL, but has problems with newlines in fields</li>
1544 <li>textarea - no problems with newlines in fields, but also no
1545 length limitations</li>
1546 </ul>
1547 Default is old behavior so input.</dd>
1553 <dd>If there are fewer items than this in the set of foreign keys, then a
1554 drop-down box of foreign keys is presented, in the style described by the
1556 setting.</dd>
1559 <dd>For the foreign key drop-down fields, there are several methods of
1560 display, offering both the key and value data. The contents of the
1561 array should be one or both of the following strings:
1567 </dt>
1568 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1569 creating a dump file</dd>
1572 </dt>
1573 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1574 compressed exports. This doesn't affect smaller dumps and allows users to
1575 create larger dumps that won't otherwise fit in memory due to php
1576 memory limit. Produced files contain more GZip/BZip2 headers, but all
1577 normal programs handle this correctly.</dd>
1581 mainframe.</dd>
1585 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1590 <dd>How many columns will be utilized to display the tables on the
1591 database property view? Default is 1 column. When setting this to a
1592 value larger than 1, the type of the database will be omitted for more
1593 display space.</dd>
1597 <dd>Defines the tab displayed by default on server view. Possible
1604 <dd>Defines the tab displayed by default on database view. Possible
1609 <dd>Defines the tab displayed by default on table view. Possible
1616 points to the MySQL documentation (type depends
1617 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1618 generated.<br />
1620 for more information about MySQL manuals and their types.</dd>
1623 <dd>Type of MySQL documentation:
1629 </ul>
1630 </dd>
1633 <dd>Defines the default language to use, if not browser-defined or
1634 user-defined.<br />
1636 this setting.</dd>
1639 <dd>Defines the default connection collation to use, if not
1640 user-defined.<br />
1645 <dd>Force: always use this language (must be defined in the
1649 <dd>Limit list of available languages to those matching the given regular
1650 expression. For example if you want only Czech and English, you should
1654 <dd>Default character set to use for recoding of MySQL queries. This must be
1655 enabled and it's described by
1657 option.<br />
1658 You can give here any character set which is in
1660 array and this is just default choice, user can select any of them.</dd>
1663 <dd>Allow character set recoding of MySQL queries. You need recode or iconv
1664 support (compiled in or module) in PHP to allow MySQL queries recoding
1665 and used language file must have it enabled (by default only these
1666 which are in Unicode, just to avoid losing some characters).<br /><br />
1669 in the Export and Import pages, to choose the character set when
1670 exporting a file. The default value in this menu comes from
1672 </dd>
1675 <dd>You can select here which functions will be used for character set
1676 conversion. Possible values are:
1677 <ul><li>auto - automatically use available one (first is tested
1678 iconv, then recode)</li>
1681 </ul>
1682 Default is auto.</dd>
1685 <dd>Specify some parameters for iconv used in charset conversion. See
1688 used, so that invalid characters will be transliterated.</dd>
1691 <dd>Available character sets for MySQL conversion. You can add your own (any of
1692 supported by recode/iconv) or remove these which you don't use.
1693 Character sets will be shown in same order as here listed, so if you
1694 frequently use some of these move them to the top.</dd>
1699 default empty, you need to fill in some trusted proxy servers if you
1700 want to use rules for IP addresses behind proxy.<br /><br />
1702 The following example specifies that phpMyAdmin should trust a
1704 <pre>
1705 $cfg['TrustedProxies'] =
1707 </pre>
1708 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1709 client's IP address as usual.
1710 </dd>
1714 MIME transformations.<br />
1715 Possible values are:
1716 <ul><li>auto - automatically detect, this is a bit expensive
1718 according to your server real possibilities</li>
1721 </ul>
1722 Default is auto.
1723 </dd>
1726 <dd>
1727 We normally check the permissions on the configuration file to ensure
1728 it's not world writable. However, phpMyAdmin could be installed on
1729 a NTFS filesystem mounted on a non-Windows server, in which case the
1730 permissions seems wrong but in fact cannot be detected. In this case
1732 </dd>
1735 <dd>
1736 Limit for length of URL in links. When length would be above this limit, it
1737 is replaced by form with button.
1738 This is required as some web servers (IIS) have problems with long URLs.
1740 </dd>
1744 </dd>
1746 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [valid css code for background]<br />
1747 <span id="cfg_MainBackground">$cfg['MainBackground']</span> string [valid css code for background]
1748 </dt>
1749 <dd>The background styles used for both the frames.
1752 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [valid css code for background]<br />
1754 <dd>The style used for the pointer in the navi frame.
1758 </dt>
1759 <dd>The color used for the database name in the navi frame.
1768 </dd>
1772 <dd>The style used for table headers. See
1777 </dd>
1781 </dd>
1783 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [HTML color]<br />
1785 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [HTML color]<br />
1787 </dt>
1789 The former feature highlights the row over which your mouse is passing
1790 and the latter lets you visually mark/unmark rows by clicking on
1791 them.<br />
1796 <dd>You put here a valid CSS font family value, for example
1801 <dd>You put here a valid CSS font family value, for example
1815 </dt>
1817 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1819 The Char* values are used for CHAR and VARCHAR editing (if configured
1823 </dt>
1827 </dt>
1828 <dd>Defines if the whole textarea of the query box will be selected on
1829 click.</dd>
1832 </dt>
1833 <dd>Enable Ctrl+Arrows (Option+Arrows in Safari) moving between fields when
1834 editing.</dd>
1837 <dd>Maximum number of characters showen in any non-numeric field on browse view.
1838 Can be turned off by a toggle button on the browse page.</dd>
1842 </dt>
1843 <dd>Defines the place where modify and delete links would be put when
1844 tables contents are displayed (you may have them displayed both at the
1845 left and at the right).
1851 </dt>
1853 Define which one is displayed by default. The first mode displays each
1854 row on a horizontal line, the second rotates the headers by 90
1855 degrees, so you can use descriptive headers even though fields only
1856 contain small values and still print them out. The vertical mode sorts
1857 each row on a vertical lineup.<br /><br />
1859 The HeaderFlipType can be set to 'css' or 'fake'. When using 'css'
1860 the rotation of the header for horizontalflipped is done via CSS. If
1861 set to 'fake' PHP does the transformation for you, but of course this
1862 does not look as good as CSS.</dd>
1866 string or integer</dt>
1867 <dd>When editing/creating new columns in a table all fields normally get
1868 lined up one field a line. (default: 'horizontal'). If you set this to
1869 'vertical' you can have each field lined up vertically beneath each
1870 other. You can save up a lot of place on the horizontal direction and
1871 no longer have to scroll. If you set this to integer, editing of fewer
1872 columns will appear in 'vertical' mode, while editing of more fields
1873 still in 'horizontal' mode. This way you can still effectively edit
1874 large number of fields, while having full view on few of them.</dd>
1878 </dt>
1880 display of column comments in Browse or Property display. In browse
1881 mode, the comments are shown inside the header. In property mode,
1882 comments are displayed using a CSS-formatted dashed-line below the
1883 name of the field. The comment is shown as a tool-tip for that field.
1884 </dd>
1896 <dd>Whether to display a link to validate a query in any SQL Query box.
1903 <dd>
1904 The name of the directory where
1906 uploaded by other means than phpMyAdmin (for example, ftp). Those files
1907 are available under a drop-down box when you click the database or
1908 table name, then the Import tab.
1909 <br /><br />
1911 If you want different directory for each user, %u will be replaced
1912 with username.<br /><br />
1916 compressed formats is enabled).<br /><br />
1918 This feature is useful when your file is too big to be uploaded via
1920 uploads are disabled in PHP.<br /><br />
1922 Please note that if PHP is running in safe mode, this directory must
1923 be owned by the same user as the owner of the phpMyAdmin scripts.
1924 <br /><br />
1928 alternatives.
1929 </dd>
1932 <dd>
1933 The name of the directory where dumps can be saved.<br /><br />
1935 If you want different directory for each user, %u will be replaced
1936 with username.<br /><br />
1938 Please note that the directory must exist and has to be writable for
1939 the user running webserver.<br /><br />
1941 Please note that if PHP is running in safe mode, this directory must
1942 be owned by the same user as the owner of the phpMyAdmin scripts.
1943 </dd>
1946 <dd>
1947 The name of the directory where temporary files can be stored.
1948 <br /><br />
1950 This is needed for native MS Excel export, see
1956 <br /><br />
1958 If the directory where phpMyAdmin is installed is subject to an
1960 temporary directory in some directory accessible by the web
1961 server. However for security reasons, this directory should be outside
1962 the tree published by webserver. If you cannot avoid having this
1963 directory published by webserver, place at least an empty
1965 possible.
1966 <br /><br />
1968 This directory should have as strict permissions as possible as the only
1969 user required to access this directory is the one who runs the
1970 webserver. If you have root privileges, simply make this user owner of
1971 this directory and make it accessible only by it:
1972 <br /><br />
1974 <pre>
1975 chown www-data:www-data tmp
1976 chmod 700 tmp
1977 </pre>
1979 If you cannot change owner of the directory, you can achieve a similar
1982 <pre>
1983 chmod 700 tmp
1984 setfacl -m "g:www-data:rwx" tmp
1985 setfacl -d -m "g:www-data:rwx" tmp
1986 </pre>
1988 If neither of above works for you, you can still make the directory
1990 system reading and writing data in this directory.
1991 </dd>
1994 <dd>
1995 In this array are defined default parameters for export, names of
1996 items are similar to texts seen on export page, so you can easily
1997 identify what they mean.
1998 </dd>
2001 <dd>
2002 In this array are defined default parameters for import, names of
2003 items are similar to texts seen on import page, so you can easily
2004 identify what they mean.
2005 </dd>
2008 <dd>
2009 Repeat the headers every X cells, or 0 to deactivate.
2010 </dd>
2018 </dt>
2019 <dd>
2020 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2021 or icon is always displayed on the left panel. If JavaScript is enabled in
2022 your browser, a click on this opens a distinct query window, which is
2023 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2024 changes to display a query box.<br /><br />
2026 The size of this query window can be customized with
2028 - both integers for the size in pixels. Note that normally, those
2030 theme you are using.<br /><br />
2034 opens the query window and puts the current query
2035 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2036 query in the right panel's query box.
2037 <br /><br />
2038 The usage of the JavaScript query window is recommended if you have a
2039 JavaScript enabled browser. Basic functions are used to exchange quite
2040 a few variables, so most 4th generation browsers should be capable to
2041 use that feature. It currently is only tested with Internet Explorer 6
2042 and Mozilla 1.x.
2043 <br /><br />
2045 to a table, which has to be created by you (see <a
2047 all your queries will be appended to the form, but only as long as
2048 your window is opened they remain saved.
2049 <br /><br />
2050 When using the JavaScript based query window, it will always get
2051 updated when you click on a new table/db to browse and will focus if
2052 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2053 the query window by checking the box "Do not overwrite this query from
2054 outside the window" below the query textarea. Then you can browse
2055 tables/databases in the background without losing the contents of the
2056 textarea, so this is especially useful when composing a query with
2057 tables you first have to look in. The checkbox will get automatically
2058 checked whenever you change the contents of the textarea. Please
2059 uncheck the button whenever you definitely want the query window to
2060 get updated even though you have made alterations.
2061 <br /><br />
2064 <br /><br />
2065 The query window also has a custom tabbed look to group the features.
2067 default tab to be used when opening the query window. It can be set to
2068 either 'sql', 'files', 'history' or 'full'.</dd>
2074 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2076 If the approximate row count as returned by
2079 count will be used.
2080 </dd>
2082 <dd>For VIEWs, since obtaining the exact count could have an
2083 impact on performance, this value is the maximum to be displayed, using
2085 any row counting.
2086 </dd>
2090 <dd>Utilizes a WYSIWYG editing control to easily place elements of a
2092 page. By clicking on the button 'toggle scratchboard' on the page
2093 where you edit x/y coordinates of those elements you can activate a
2094 scratchboard where all your elements are placed. By clicking on an
2095 element, you can move them around in the pre-defined area and the x/y
2096 coordinates will get updated dynamically. Likewise, when entering a
2097 new position directly into the input field, the new position in the
2098 scratchboard changes after your cursor leaves the input field.<br />
2099 You have to click on the 'OK'-button below the tables to save the new
2100 positions. If you want to place a new element, first add it to the
2101 table of elements and then you can drag the new element around.<br />
2102 By changing the paper size and the orientation you can change the size
2103 of the scratchboard as well. You can do so by just changing the
2104 dropdown field below, and the scratchboard will resize automatically,
2105 without interfering with the current placement of the elements.<br />
2106 If ever an element gets out of range you can either enlarge the paper
2107 size or click on the 'reset' button to place all elements below each
2108 other.<br />
2110 get this control to work. The basic Drag&Drop script functionality
2111 was kindly borrowed from www.youngpup.net and is underlying so
2112 specific license.</dd>
2115 <dd>Sorts database and table names according to natural order (for example,
2116 t1, t2, t10). Currently implemented in the left panel (Light mode)
2117 and in Database view, for the table list.</dd>
2128 <dd>Allows you to specify window's title bar. Following magic string can
2129 be used to get special values:
2130 <dl>
2136 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
2145 </dl>
2146 </dd>
2156 </dd>
2159 <dd>If theme manager is active, use this as the path of the subdirectory
2160 containing all the themes.</dd>
2174 </dt>
2175 <dd>Default queries that will be displayed in query boxes when user didn't
2176 specify any. Use %d for database name, %t for table name and %f for a
2177 comma separated list of field names. Note that %t and %f are only
2181 <dd>
2182 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
2183 default we use HTML to format the query, but you can disable this by
2185 </dd>
2188 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2189 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2190 query inside a bracket is indented. By changing
2193 specifies the units of the indent amount that you specified. This is
2194 used via stylesheets.</dd>
2197 <dd>This array is used to define the colours for each type of element of
2198 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2200 If you specify an empty string for the color of a class, it is ignored
2201 in creating the stylesheet.
2202 You should not alter the class names, only the colour strings.<br />
2223 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2227 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2228 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2229 </ul>
2230 </dd>
2234 <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,
2235 as originally published on
2237 <br />
2238 For help in setting up your system to use the service, see the
2240 </dd>
2244 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2245 and any password, so we use those by default. Instead, if
2246 you have an account with them, you can put your login details
2247 here, and it will be used in place of the anonymous login.</dd>
2248 </dl>
2249 </dd>
2252 <dd><b>DEVELOPERS ONLY!</b></dd>
2255 <dd><b>DEVELOPERS ONLY!</b><br />
2256 Enable logging queries and execution times to be displayed in the bottom
2257 of main page (right frame).</dd>
2260 <dd><b>DEVELOPERS ONLY!</b><br />
2261 Enable the DBG extension for debugging phpMyAdmin. Required for profiling
2262 the code.<br />
2263 For help in setting up your system to this, see the
2267 <dd><b>DEVELOPERS ONLY!</b><br />
2268 Enable profiling support for phpMyAdmin. This will append a chunk of data
2269 to the end of every page displayed in the main window with profiling
2270 statistics for that page.<br />
2271 You may need to increase the maximum execution time for this to
2272 complete successfully.<i>Profiling was removed from the code for
2273 version 2.9.0 due to licensing issues.</i></dd>
2275 <dt id="cfg_DBG_profile_threshold">$cfg['DBG']['profile']['threshold'] float (units in milliseconds)</dt>
2276 <dd><b>DEVELOPERS ONLY!</b><br />
2277 When profiling data is displayed, this variable controls the threshold of
2278 display for any profiling data, based on the average time each time has
2279 taken. If it is over the threshold it is displayed, otherwise it is not
2280 displayed. This takes a value in milliseconds. In most cases you don't need
2281 to edit this.</dd>
2284 <dd>All possible types of a MySQL column. In most cases you don't need to
2285 edit this.</dd>
2288 <dd>Possible attributes for fields. In most cases you don't need to edit
2289 this.</dd>
2292 <dd>A list of functions MySQL supports. In most cases you don't need to
2293 edit this.</dd>
2296 <dd>Mapping of column types to meta types used for preferring displayed
2297 functions. In most cases you don't need to edit this.</dd>
2300 <dd>Functions preferred for column meta types as defined in
2301 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2302 to edit this.</dd>
2305 <dd>Functions selected by default when inserting/changing row, Functions
2306 are defined for meta types from
2308 <code>first_timestamp</code>, which is used for first timestamp column
2309 in table.</dd>
2312 <dd>Operators available for search operations on numeric and date fields.
2313 </dd>
2316 <dd>Operators available for search operations on character fields.
2317 Note that we put <code>LIKE</code> by default instead of
2318 <code>LIKE %...%</code>, to avoid unintended performance problems
2319 in case of huge tables.</dd>
2322 <dd>Operators available for search operations on enum fields.</dd>
2325 <dd>Additional operators available for search operations when the
2326 field can be null.</dd>
2328 </dl>
2330 <!-- TRANSFORMATIONS -->
2336 </ol>
2340 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2342 section</a> on how to do so.</p>
2344 <p> You can apply different transformations to the contents of each field. The
2345 transformation will take the content of each field and transform it with
2346 certain rules defined in the selected transformation.</p>
2348 <p> Say you have a field 'filename' which contains a filename. Normally you would
2349 see in phpMyAdmin only this filename. Using transformations you can transform
2350 that filename into a HTML link, so you can click inside of the phpMyAdmin
2351 structure on the field's link and will see the file displayed in a new browser
2352 window. Using transformation options you can also specify strings to
2353 append/prepend to a string or the format you want the output stored in.</p>
2355 <p> For a general overview of all available transformations and their options,
2356 you can consult your
2357 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2358 installation.</p>
2360 <p> For a tutorial on how to effectively use transformations, see our
2362 the official phpMyAdmin homepage.</p>
2366 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2367 clicking on the 'Structure' link for a table). There click on
2368 "Change" (or change icon) and there you will see three new fields at
2369 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2370 'Transformation options'.</p>
2372 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2373 that corresponds to the column's contents. Please note that
2374 transformations are inactive as long as no MIME-type is selected.</li>
2376 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2377 hopefully growing amount of pre-defined transformations. See below for information on
2378 how to build your own transformation.<br />
2380 There are global transformations and mimetype-bound transformations. Global transformations
2381 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2382 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2383 transformations which operate on the main mimetype (like 'image'), which will most likely
2384 take the subtype into regard, and those who only operate on a
2385 specific subtype (like 'image/jpeg').<br />
2387 You can use transformations on mimetypes for which the function was not defined for. There
2388 is no security check for you selected the right transformation, so take care of what the
2389 output will be like.</li>
2391 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2392 transform-function specific options here. Usually the transforms can operate with default
2393 options, but it is generally a good idea to look up the overview to see which options are
2394 necessary.<br />
2396 Much like the ENUM/SET-Fields, you have to split up several options using the format
2397 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2398 parsed as an array, leaving the first value the first element in the array, and so
2399 forth.<br />
2401 If you want to specify a MIME character set you can define it in the transformation_options.
2402 You have to put that outside of the pre-defined options of the specific mime-transform,
2404 for which you can specify 2 options and you want to append a character set, enter "'first
2405 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2407 </ul>
2411 <p> All mimetypes and their transformations are defined through single files in
2412 the directory 'libraries/transformations/'.</p>
2414 <p> They are stored in files to ease up customization and easy adding of new
2415 transformations.</p>
2417 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2418 always work. It makes no sense to apply a transformation to a mimetype, the
2419 transform-function doesn't know to handle.</p>
2421 <p> One can, however, use empty mime-types and global transformations which should work
2422 for many mimetypes. You can also use transforms on a different mimetype they where built
2423 for, but pay attention to option usage as well as what the transformation does to your
2424 field.</p>
2426 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2427 any other transform function and provides some basic functions.</p>
2429 <p> There are 5 possible file names:</p>
2431 <ol><li>A mimetype+subtype transform:<br /><br />
2433 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2435 Please not that mimetype and subtype are separated via '_', which shall
2436 not be contained in their names. The transform function/filename may
2437 contain only characters which cause no problems in the file system as
2438 well as the PHP function naming convention.<br /><br />
2440 The transform function will the be called
2441 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2443 <b>Example:</b><br /><br />
2445 <tt>text_html__formatted.inc.php</tt><br />
2446 <tt>PMA_transform_text_html__formatted()</tt></li>
2448 <li>A mimetype (w/o subtype) transform:<br /><br />
2450 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2452 Please note that there are no single '_' characters.
2453 The transform function/filename may contain only characters which cause
2454 no problems in the file system as well as the PHP function naming
2455 convention.<br /><br />
2457 The transform function will the be called
2458 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2460 <b>Example:</b><br /><br />
2462 <tt>text__formatted.inc.php</tt><br />
2463 <tt>PMA_transform_text__formatted()</tt></li>
2465 <li>A mimetype+subtype without specific transform function<br /><br />
2467 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2469 Please note that there are no '__' characters in the filename. Do not
2470 use special characters in the filename causing problems with the file
2471 system.<br /><br />
2473 No transformation function is defined in the file itself.<br /><br />
2475 <b>Example:</b><br /><br />
2477 <tt>text_plain.inc.php</tt><br />
2478 (No function)</li>
2480 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2482 <tt>[mimetype].inc.php</tt><br /><br />
2484 Please note that there are no '_' characters in the filename. Do not use
2485 special characters in the filename causing problems with the file system.
2486 <br /><br />
2488 No transformation function is defined in the file itself.<br /><br />
2490 <b>Example:</b><br /><br />
2492 <tt>text.inc.php</tt><br />
2493 (No function)</li>
2495 <li>A global transform function with no specific mimetype<br /><br />
2497 <tt>global__[transform].inc.php</tt><br /><br />
2499 The transform function will the be called
2500 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2502 <b>Example:</b><br /><br />
2504 <tt>global__formatted</tt><br />
2505 <tt>PMA_transform_global__formatted()</tt></li>
2506 </ol>
2508 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2509 transform function.</p>
2511 <p> All filenames containing no '__' in themselves are not shown as valid transform
2512 functions in the dropdown.</p>
2514 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2515 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2516 without a transform function. Also note the introduction of a function description in
2517 the language files. For each function a $strTransformation_[filename without .inc.php]
2518 has to exist.</p>
2520 <p> You can use the template generator to generate new functions and entries in the
2521 language file.</p>
2523 <p> To create a new transform function please see
2524 <tt>libraries/transformations/template_generator.sh</tt>.
2525 To create a new, empty mimetype please see
2526 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2528 <p> A transform function always gets passed three variables:</p>
2530 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2531 you want to transform.</li>
2532 <li><b>$options</b> - Contains any user-passed options to a transform function
2533 as an array.</li>
2534 <li><b>$meta</b> - Contains an object with field information to your column.
2535 The data is drawn from the output of the
2537 function. This means, all object properties described on the
2539 available in this variable and can be used to transform a field accordingly
2540 to unsigned/zerofill/not_null/... properties.<br />
2541 The $meta->mimetype variable contains the original MIME-type of the
2542 field (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2543 </ol>
2545 <!-- FAQ -->
2552 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2557 </ol>
2559 <p> Please have a look at our
2561 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2562 features and or interface.</p>
2568 action is required or phpMyAdmin sends a blank page or a page full of
2569 cryptic characters to my browser, what can I do?</a></h4>
2571 <p> There are some known PHP bugs with output buffering and compression.<br />
2573 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2574 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2575 configuration file.<br />
2576 Furthermore, we know about such problems connected to the release
2577 candidates of PHP 4.2.0 (tested with PHP 4.2.0 RC1 to RC4) together with
2578 MS Internet Explorer. Please upgrade to the release version PHP 4.2.0.</p>
2583 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2584 See also the
2586 entry about PHP bugs with output buffering.<br />
2587 If your server keeps crashing, please ask for help in the various Apache
2588 support groups.</p>
2592 mode under PHP 4.2.0 or 4.2.1 loaded as an Apache 2 module but can't enter the
2593 script: I'm always displayed the login screen.</a></h4>
2595 <p> This is a known PHP bug (see this
2597 official PHP bug database. It means there is and won't be any phpMyAdmin
2598 fix against it because there is no way to code a fix.</p>
2604 application misbehaved by not returning a complete set of
2606 </h4>
2608 <p> You just forgot to read the <i>install.txt</i> file from the php distribution.
2609 Have a look at the last message in this
2611 official PHP bug database.</p>
2616 and/or many error messages with the
2618 mode.</a></h4>
2620 <p> This is a known problem with the PHP
2622 filter: it's not so stable. Please use instead the cookie authentication mode.
2623 </p>
2628 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2629 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2630 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2631 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2632 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2637 work.</a></h4>
2639 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2640 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2641 or not, and so on). So, you must have PHP4 >= 4.0.4 and Zlib/Bzip2
2642 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br />
2643 We faced PHP crashes when trying to download a dump with MS Internet
2644 Explorer when phpMyAdmin is run with a release candidate of PHP 4.2.0. In
2645 this case you should switch to the release version of PHP 4.2.0.</p>
2649 an error about safe mode being in effect.</a></h4>
2651 <p> Your uploaded file is saved by PHP in the "upload dir", as
2652 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2653 the system default is <i>/tmp</i>).<br />
2654 We recommend the following setup for Apache servers running in safe mode,
2655 to enable uploads of files while being reasonably secure:</p>
2657 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2658 <li>give ownership to the Apache server's user.group:
2659 <tt>chown apache.apache /tmp/php</tt></li>
2660 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2661 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2662 <li>restart Apache</li>
2663 </ul>
2667 general file uploads don't work on my system and uploaded files have a
2668 <tt>Content-Type:</tt> header in the first line.</a></h4>
2670 <p> It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0
2671 and you updated your PHP RPM to php-4.0.4pl1-3.i386.rpm, didn't you?<br />
2672 So the problem is that this package has a serious bug that was corrected
2673 ages ago in PHP (2001-01-28: see
2675 for more details). The problem is that the bugged package is still
2676 available though it was corrected (see
2678 for more details).<br />
2679 So please download
2680 <a href="http://www.redhat.com/swr/i386/php-4.0.4pl1-9.i386.html">the fixed package (4.0.4pl1-9)</a>
2681 and the problem should go away.<br />
2682 And that fixes the \r\n problem with file uploads!</p>
2686 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2687 I'm using the Apache server.</a></h4>
2689 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2690 your <i>httpd.conf</i>:</p>
2694 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2698 uploading a file from the query box.</a></h4>
2700 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2701 restrictions. However you need to create temporary directory and
2703 The uploaded files will be moved there, and after execution of your
2709 <p> The MySQL manual explains how to
2711 reset the permissions</a>.</p>
2716 execute a bookmark.</a></h4>
2718 <p> If PHP does not have read/write access to its <tt>upload_tmp_dir</tt>, it
2719 cannot access the uploaded query.</p>
2724 submit a query from the convenient text area.</a></h4>
2726 <p> Check the <tt>post_max_size</tt> directive from your PHP configuration file
2727 and try to increase it.</p>
2731 </h4>
2733 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt> fields
2734 were named <tt>user</tt> and <tt>password</tt>. Please modify your field
2735 names to align with current standards.</p>
2740 </h4>
2742 <p> Starting with version 2.7.0, the import engine has been re–written and these
2743 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2744 to take advantage of the new import features.</p>
2746 <p> The first things to check (or ask your host provider to check) are the
2747 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2748 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2749 All of these three settings limit the maximum size of data that can be
2750 submitted and handled by PHP. One user also said that post_max_size
2751 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2753 There exist several workarounds if your upload is too big or your
2754 hosting provider is unwilling to change the settings:</p>
2757 feature. This allows one to
2758 upload a file to the server via scp, ftp, or your favorite file transfer
2759 method. PhpMyAdmin is then able to import the files from the temporary
2761 section</a> of this document.</li>
2763 BigDump</a>) to split the files before uploading. We cannot support this
2764 or any third party applications, but are aware of users having success
2765 with it.</li>
2766 <li>If you have shell (command line) access, use MySQL to import the files
2767 directly. You can do this by issuing the "source" command from
2768 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2769 </ul>
2773 support?</a></h4>
2775 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2776 older MySQL versions, you need to use 2.8.x branch. phpMyAdmin can
2777 connect to your MySQL server using PHP's classic
2780 is available in php 5.0. The latter one should be used unless you have
2781 good reason not to do so.<br />
2782 When compiling php, we strongly recommend that you manually link the MySQL
2783 extension of your choice to a MySQL client library of at least the same
2784 minor version since the one that is bundled with some PHP distributions is
2787 If your webserver is running on a windows system, you might want to try
2788 MySQL's
2790 instead of the MySQL / MySQLi extensions that are bundled with the official
2791 php Win32 builds.</p>
2795 message, "Client does not support authentication protocol requested
2796 by server; consider upgrading MySQL client"</a></h5>
2798 <p> You tried to access MySQL with an old MySQL client library. The version of
2799 your MySQL client library can be checked in your phpinfo() output.
2800 In general, it should have at least the same minor version as your server
2804 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2805 changed the authentication hash and your PHP is trying to use the old method.
2807 with the proper client library to match your MySQL installation. Your
2808 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2809 More information (and several workarounds) are located in the
2811 </p>
2815 <tt>lower_case_table_names</tt> set to 1. If I create a new table with a
2816 capital letter in its name it is changed to lowercase as it should. But
2817 if I try to DROP this table MySQL is unable to find the corresponding
2818 file.</a></h4>
2820 <p> This is a bug of MySQL <= 4.0.1. Please upgrade to at least
2821 MySQL 4.0.2 or turn off your <tt>lower_case_table_names</tt>
2822 directive.</p>
2826 script seems not to know the font face I'm using!</a></h4>
2828 <p> The "FPDF" library we're using for this feature requires some
2829 special files to use font faces.<br />
2831 these files.</p>
2835 check PHP Configuration".</a></h4>
2837 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2838 "MySQL extension". This extension may be part of the PHP
2839 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2840 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2841 to load the extension but failed.<br /><br />
2843 Usually, the problem is solved by installing a software package called
2844 "PHP-MySQL" or something similar.</p>
2849 and I cannot log in using cookie auth.</a></h4>
2851 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2855 so I cannot upload.</a></h4>
2857 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2858 parameter is not set to "on".</p>
2862 a new table the table and field names are changed to lowercase!</a></h4>
2864 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2865 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2866 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2867 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2868 directory and add the following line to the group [mysqld]:</p>
2870 <pre>set-variable = lower_case_table_names=0</pre>
2872 <p> Next, save the file and restart the MySQL service. You can always check the
2873 value of this directive using the query</p>
2875 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2879 get characters randomly added. I am running PHP 4.2.3.</a></h4>
2882 </p>
2886 and I get problems, such as undefined variables when I run a
2889 <p> A tip from Jose Fandos: put a comment on the following two lines
2890 in httpd.conf, like this:</p>
2892 <pre>
2893 # mod_gzip_item_include file \.php$
2895 </pre>
2897 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2898 PHP scripts. Of course you have to restart Apache.</p>
2903 I get the error "No input file specified" when trying to
2904 run phpMyAdmin.</a></h4>
2906 <p> This is a permission problem. Right-click on the phpmyadmin folder
2907 and choose properties. Under the tab Security, click on "Add"
2908 and select the user "IUSR_machine" from the list. Now set his
2909 permissions and it should work.</p>
2913 db_structure.php with plenty of tables).</a></h4>
2916 GZIP output buffering is enabled. If you turn off it (by
2918 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2919 PHP 5.0.0.</p>
2923 message 'Errorcode: 13'. What does this mean?</a></h4>
2925 <p> This can happen due to a MySQL bug when having database / table names with
2926 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2927 To fix this, turn off this directive, convert all database and table names
2928 to lower case and turn it on again. Alternatively, there's a bug-fix
2929 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2933 and the fields are duplicated.</a></h4>
2935 <p> It is possible to configure Apache in such a way that PHP has problems
2936 interpreting .php files.</p>
2938 <p> The problems occur when two different (and conflicting) set of directives
2939 are used:</p>
2941 <pre>
2942 SetOutputFilter PHP
2943 SetInputFilter PHP
2944 </pre>
2946 <p> and</p>
2948 <pre>AddType application/x-httpd-php .php</pre>
2950 <p> In the case we saw, one set of directives was in
2951 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2952 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2953 The recommended way is with <tt>AddType</tt>, so just comment out
2954 the first set of lines and restart Apache:</p>
2956 <pre>
2957 #SetOutputFilter PHP
2958 #SetInputFilter PHP
2959 </pre>
2964 <p> This problem is known to happen when the server is running Turck MMCache
2965 but upgrading MMCache to version 2.3.21 solves the problem.</p>
2970 <p> Yes.<br />
2971 However, phpMyAdmin needs to be backwards compatible to php4. This is why
2972 phpMyAdmin disables the <tt>E_STRICT</tt> error_level in
2973 <tt>error_reporting</tt> settings.
2974 </p>
2977 <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>
2979 <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>
2982 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
2983 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
2984 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
2985 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
2986 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
2987 enabled.) Click <tt>OK</tt>.</li>
2988 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
2989 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
2990 </ol>
2994 PHP 5.0.4 on 64-bit systems?</a></h4>
2996 <p> Yes. This problem affects phpMyAdmin ("Call to undefined function
2997 pma_reloadnavigation"), so upgrade your PHP to the next version.</p>
3003 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
3004 the order of the server paragraph in <tt>config.inc.php</tt>.
3005 Table and script parts are optional. If you want
3006 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
3007 some configuration. Following lines apply only for <a
3009 that you have enabled some features within global configuration. You need
3010 <code>Options FollowSymLinks</code> and <code>AllowOverride
3011 FileInfo</code> enabled for directory where phpMyAdmin is installed and
3012 you need mod_rewrite to be enabled. Then you just need to create following
3013 <code>.htaccess</code> file in root folder of phpMyAdmin installation
3014 (don't forget to change directory name inside of it):</p>
3016 <pre>
3017 RewriteEngine On
3018 RewriteBase /path_to_phpMyAdmin
3019 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3020 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3021 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3022 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3023 </pre>
3026 <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>
3028 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3029 following rewrite rule:</p>
3031 <pre>
3032 RewriteEngine On
3033 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3034 </pre>
3038 </h4>
3039 <p>
3040 There can be many explanations to this and a look at your server's
3041 error log file might give a clue.
3042 </p>
3046 password encryption in cookie auth doesn't work.</a></h4>
3048 <p> If your cluster consist of different architectures, PHP code used for
3049 encryption/decryption won't work correct. This is caused by use of
3050 pack/unpack functions in code. Only solution is to use mcrypt extension
3051 which works fine in this case.</p>
3056 <p> Yes but the default configuration values of Suhosin are known to cause
3057 problems with some operations, for example editing a table with many
3058 columns and no primary key. Tuning information is available at
3060 http://www.hardened-php.net/hphp/troubleshooting.html</a>,
3061 although the parameter names have changed (<tt>suhosin</tt> instead
3063 <tt>SuhosinDisableWarning</tt> directive</a>.
3064 </p>
3068 but then my connection is redirected back to http. What can cause this
3069 behavior?</a></h4>
3071 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3072 in your Apache configuration. See <a href="http://httpd.apache.org/docs/2.0/mod/mod_ssl.html#ssloptions">http://httpd.apache.org/docs/2.0/mod/mod_ssl.html#ssloptions</a>.</p>
3075 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work,</a></h4>
3077 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3078 Example from the Apache 2.2 documentation:</p>
3079 <pre>
3080 ProxyPass /mirror/foo/ http://backend.example.com/
3081 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3082 ProxyPassReverseCookieDomain backend.example.com public.example.com
3083 ProxyPassReverseCookiePath / /mirror/foo/
3084 </pre>
3086 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3087 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3088 This is not specific to phpmyadmin, it's just the behavior of Apache.
3089 </p>
3091 <pre>
3092 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3093 ProxyPassReverse /mirror/foo/
3094 http://backend.example.com/%7Euser/phpmyadmin
3095 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3096 </pre>
3098 <p>See <a href="http://httpd.apache.org/docs/2.2/mod/mod_proxy.html">http://httpd.apache.org/docs/2.2/mod/mod_proxy.html</a>
3099 for more details.</p>
3103 privileges, I get an error about an unknown column.</a></h4>
3105 <p> The MySQL server's privilege tables are not up to date, you need to run
3106 the <tt>mysql_upgrade</tt> command on the server.</p>
3113 headers already sent by ..." is displayed, what's the problem?</a></h4>
3115 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3116 (I.E. no blank lines, no spaces, no characters...) neither before the
3117 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3118 tag at the end. We also got a report from a user under IIS, that used
3119 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3120 contained an end-of-line character (hex 0A) at the end; removing this character
3121 cleared his errors.</p>
3126 <p> Either there is an error with your PHP setup or your username/password is
3127 wrong. Try to make a small script which uses mysql_connect and see if it
3128 works. If it doesn't, it may be you haven't even compiled MySQL support
3129 into PHP.</p>
3133 connect to local MySQL server through socket '/tmp/mysql.sock'
3134 (111) ..." is displayed. What can I do?</a></h4>
3136 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3138 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3139 In your <i>php.ini</i> you will find a line</p>
3141 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3143 <p> change it to</p>
3145 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3147 <p> Then restart apache and it will work.</p>
3149 <p> Here is a fix suggested by Brad Ummer:</p>
3151 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3152 To do this, telnet to your server and go to the MySQL bin directory. In
3153 this directory there should be a file named <i>mysqladmin</i>. Type
3154 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3155 info about your MySQL server, including the socket
3156 (<i>/tmp/mysql.sock</i>, for example).</li>
3157 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3158 phpMyAdmin, you need to complete the socket information in the
3159 <i>config.inc.php</i>.<br />
3160 For example:
3162 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3163 <br /><br />
3165 Please also make sure that the permissions of this file allow to be readable
3166 by your webserver (i.e. '0755').</li>
3167 </ul>
3169 <p> Have also a look at the
3171 corresponding section of the MySQL documentation</a>.</p>
3175 what can I do?</a></h4>
3178 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3179 sometime.<br />
3180 Also have a look at your PHP version number: if it contains "4.0b..."
3181 it means you're running a beta version of PHP. That's not a so good idea,
3182 please upgrade to a plain revision.</p>
3186 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3187 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3189 <p> Check the value you set for the
3191 directive in the phpMyAdmin configuration file.</p>
3195 password: YES)"-error when trying to access a MySQL-Server on a
3196 host which is port-forwarded for my localhost.</a></h4>
3198 <p> When you are using a port on your localhost, which you redirect via
3199 port-forwarding to another host, MySQL is not resolving the localhost
3200 as expected.<br />
3201 Erik Wasser explains: The solution is: if your host is "localhost"
3202 MySQL (the commandline tool 'mysql' as well) always tries to use the socket
3203 connection for speeding up things. And that doesn't work in this configuration
3204 with port forwarding.<br />
3210 <p> Themes are configured with
3214 <br />
3216 should not delete the directory "original" or its underlying
3217 structure, because this is the system theme used by phpMyAdmin.
3218 "original" contains all images and styles, for backwards
3219 compatibility and for all themes that would not include images or css-files.
3220 <br /><br />
3223 is enabled, you can select your favorite theme on the main page. Your
3224 selected theme will be stored in a cookie.<br /><br /></p>
3226 <p> To create a theme:</p>
3228 <ul><li>make a new subdirectory (for example "your_theme_name") under
3230 (by default <tt>themes</tt>)</li>
3231 <li>copy the files and directories from "original" to
3232 "your_theme_name"</li>
3233 <li>edit the css-files in "your_theme_name/css"</li>
3234 <li>put your new images in "your_theme_name/img"</li>
3235 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3236 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3237 contain your chosen theme name, that will be visible in user interface</li>
3238 <li>make a new screenshot of your theme and save it under
3239 "your_theme_name/screen.png"</li>
3240 </ul>
3242 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3243 theme verbose name, theme generation and theme version. These versions and
3244 generations are enumerated from 1 and do not have any direct dependence on
3245 phpMyAdmin version. Themes within same generation should be backwards
3246 compatible - theme with version 2 should work in phpMyAdmin requiring
3247 version 1. Themes with different generation are incompatible.</p>
3249 <p> If you do not want to use your own symbols and buttons, remove the
3250 directory "img" in "your_theme_name". phpMyAdmin will
3251 use the default icons and buttons (from the system-theme "original").
3252 </p>
3256 what can I do?</a></h4>
3258 <p> Here are a few points to check:</p>
3260 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3262 directive empty. See also
3264 </li>
3265 <li>Maybe you have a broken PHP installation or you need to upgrade
3266 your Zend Optimizer. See
3268 http://bugs.php.net/bug.php?id=31134</a>.
3269 </li>
3270 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3271 set to the default (200) or another low value, you could get this
3272 error if your table has a high number of columns. Adjust this setting
3273 accordingly. (Thanks to Klaus Dorninger for the hint).
3274 </li>
3275 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3276 of ";" will cause this error. Replace it with "&;".
3277 </li>
3279 you might want to increase
3281 </li>
3282 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3283 </li>
3284 </ul>
3289 <p> To be able to see a progress bar during your uploads, your server must
3292 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3293 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3300 who logged out can not log in again in with the same nick.</a></h4>
3302 <p> This is related to the authentication mechanism (protocol) used by
3303 phpMyAdmin. To bypass this problem: just close all the opened
3304 browser windows and then go back to phpMyAdmin. You should be able to
3305 log in again.</p>
3309 limit error or a time limit error.</a></h4>
3311 <p> Compressed dumps are built in memory and because of this are limited to
3312 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3313 using
3315 (enabled by default). Zip exports can not be handled this way, so if you need
3316 Zip files for larger dump, you have to use another way.</p>
3320 when I rename a table or a column.</a></h4>
3322 <p> This is an InnoDB bug, see <a href="http://bugs.mysql.com/bug.php?id=21704">http://bugs.mysql.com/bug.php?id=21704</a>.</p>
3326 bundled with the MySQL server distribution.</a></h4>
3328 <p> The problem is that older versions of mysqldump created invalid comments like this:</p>
3330 <pre>
3331 -- MySQL dump 8.22
3332 --
3333 -- Host: localhost Database: database
3334 ---------------------------------------------------------
3335 -- Server version 3.23.54
3336 </pre>
3338 <p> The invalid part of the code is the horizontal line made of dashes that
3339 appears once in every dump created with mysqldump. If you want to run your
3340 dump you have to turn it into valid MySQL. This means, you have to add a
3341 whitespace after the first two dashes of the line or add a # before it:
3342 <br />
3343 <code>
3344 -- -------------------------------------------------------<br />
3345 </code>
3346 or<br />
3347 <code>
3348 #---------------------------------------------------------
3349 </code>
3350 </p>
3357 <p> Please note that you should not use the separating string multiple times
3358 without any characters between them, or at the beginning/end of your table
3359 name. If you have to, think about using another TableSeparator or disabling
3360 that feature</p>
3365 <p> In Relation view, being able to choose a table in another database,
3366 or having more than one index field in the foreign key.<br /><br/>
3367 In Query-by-example (Query), automatic generation of the query
3368 LEFT JOIN from the foreign table.<br /><br/>
3369 </p>
3373 I get series of errors like "Warning: unable to parse url". How
3374 can this be fixed?</a></h4>
3375 <p>
3376 Your table neither have a primary key nor an unique one, so we must use a
3377 long expression to identify this row. This causes problems to parse_url
3378 function. The workaround is to create a primary or unique key.
3379 <br />
3380 </p>
3384 a MIME-Transformation onto!</a></h4>
3386 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3387 nested forms can be put inside the table where phpMyAdmin displays the results.
3388 You can, however, use any form inside of a table if keep the parent
3389 form-container with the target to tbl_row_delete.php and just put your own
3390 input-elements inside. If you use a custom submit input field, the form will
3391 submit itself to the displaying page again, where you can validate the
3392 $HTTP_POST_VARS in a transformation.
3394 For a tutorial on how to effectively use transformations, see our
3396 on the official phpMyAdmin-homepage.</p>
3400 MySQL server</a></h4>
3402 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3405 http://dev.mysql.com/doc/mysql/en/ANSI_mode.html</a>). Most important of all,
3406 the quote-character (") is interpreted as an identifier quote character and
3407 not as a string quote character, which makes many internal phpMyAdmin
3409 statements. There is no workaround to this behaviour. News to this item will
3410 be posted in Bug report
3411 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3412 </p>
3416 more that one column with the same value
3417 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3418 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3420 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3421 can use it for the Edit and Delete links.</p>
3426 <p> phpMyAdmin uses a quick method to get the row count, and this method
3427 only returns an approximate count in the case of InnoDB tables. See
3429 a way to modify those results, but
3430 this could have a serious impact on performance.</p>
3435 <p> The number of records in queries containing COUNT and GROUP BY is
3436 not correctly calculated. Also, sorting results of a query like
3441 containing an hyphen.
3442 </a></h4>
3443 <p>
3444 The tests I have made with current MySQL 4.1.11 API shows that the
3445 API does not accept this syntax for the USE command. Enclosing the
3446 db name with backquotes works. For further confusion, no backquotes
3447 are needed with command-line mysql.
3448 </p>
3451 <a href="#faq3_14">3.14 I am not able to browse a table when I don't have the right to SELECT one of the columns.</a></h4>
3452 <p>
3453 This has been a known limitation of phpMyAdmin since the beginning and
3454 it's not likely to be solved in the future.
3455 </p>
3457 <!-- Begin: Excel import limitations -->
3460 <a href="#faq3_15">3.15 When I import an Excel spreadsheet, some cells with calculations do not display correctly.</a></h4>
3461 <p>
3462 phpMyAdmin uses the <a href="http://www.codeplex.com/PHPExcel/" target="_blank">PHPExcel</a> library to parse Excel XLS and XLSX spreadsheets.
3463 Therefore, any limitations that are listed on their page regarding Excel calculations will also apply here.
3464 <br /><br />
3465 PHPExcel will be kept up to date so as to make all improvements available to phpMyAdmin users.
3466 </p>
3469 <a href="#faq3_16">3.16 When I compress (gzip, bzip2, zip) an Excel workbook and attempt to import it, nothing happens.</a></h4>
3470 <p>
3471 Since Excel XLSX workbooks are already compressed, there is often times only a small benefit from compressing them yet again.
3472 Support for compressed Excel XLSX and XLS workbooks may be added in the future.
3473 </p>
3476 <a href="#faq3_17">3.17 When I import an Excel spreadsheet, my custom cell types are not represented as they are in Excel.</a></h4>
3477 <p>
3478 Excel's internal representation of custom cell types is rather muddled (especially in Excel 97-2003 binary XLS files). If possible,
3479 consider using a built-in type. These are almost always guarenteed to import correctly.
3480 </p>
3482 <!-- End: Excel import limitations -->
3483 <!-- Begin: CSV import limitations -->
3486 <a href="#faq3_18">3.18 When I import a CSV file that contains multiple tables, they are lumped together into a single table.</a></h4>
3487 <p>
3488 There is no reliable way to differetiate tables in CSV format. For the time being, you will have to break apart CSV files containing multiple tables.
3489 </p>
3491 <!-- End: CSV import limitations -->
3492 <!-- Begin: Import type-detection limitations -->
3495 <a href="#faq3_19">3.19 When I import a file and have phpMyAdmin determine the appropriate data structure it only uses int, decimal, and varchar types.</a></h4>
3496 <p>
3497 Currently, the import type-detection system can only assign these MySQL types to columns. In future, more will likely be added but for the time being
3498 you will have to edit the structure to your liking post-import.
3499 <br /><br />
3500 Also, you should note the fact that phpMyAdmin will use the size of the largest item in any given column as the column size for the appropriate type. If you
3501 know you will be adding larger items to that column then you should manually adjust the column sizes accordingly. This is done for the sake of efficiency.
3502 </p>
3504 <!-- End: Import type-detection limitations -->
3506 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3509 <a href="#faq4_1">4.1 I'm an <abbr title="Internet service provider">ISP</abbr>. Can I setup one central copy of phpMyAdmin or do I
3510 need to install it for each customer.
3511 </a></h4>
3512 <p>
3513 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3514 your users. The development of this feature was kindly sponsored by
3515 NetCologne GmbH.
3516 This requires a properly setup MySQL user management and phpMyAdmin
3517 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3519 </p>
3523 access.
3524 </a></h4>
3525 <p>
3526 This depends on your system.<br />
3527 If you're running a server which cannot be accessed by other people, it's
3528 sufficient to use the directory protection bundled with your webserver
3530 If other people have telnet access to your server, you should use
3531 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3532 <br /><br />
3533 Suggestions:
3534 </p>
3535 <ul>
3536 <li>
3538 </li>
3539 <li>
3540 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3541 is a user whose password is only known to you, and apache is the
3542 group under which Apache runs.
3543 </li>
3544 <li>
3545 You should use PHP safe mode, to protect from other users that try
3547 </li>
3548 </ul>
3553 </a></h4>
3554 <p>
3559 </p>
3562 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3563 authentication.
3564 </a></h4>
3568 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3569 and/or
3571 are wrong.</li>
3573 <li>You have already setup a security mechanism for the
3574 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3575 phpMyAdmin's authentication, so remove it.</li>
3576 </ul>
3583 and put the privileges you want. For example,
3585 would let a user create/manage his/her database(s).</p>
3590 <p> If you have existing rules from an old .htaccess file, you can take them
3593 be a major benefit here if your installation is suited to using it. Then
3594 you can just add those updated lines into the
3598 <p> If you want a pre-made sample, you can try this fragment. It stops the
3599 'root' user from logging in from any networks other than the private
3602 <pre>
3603 //block root from logging in except from the private networks
3604 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3605 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3606 'deny root from all',
3607 'allow root from localhost',
3611 );
3612 </pre>
3617 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3618 different than the one set in your
3620 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3621 while a domain name is defined in the config file.</p>
3626 <p>When starting phpMyAdmin, you can use the <tt>db</tt>, <tt>pma_username</tt>, <tt>pma_password</tt> and <tt>server</tt> parameters. This last one can contain either the numeric host index (from <tt>$i</tt> of the configuration file) or one of the host names present in the configuration file. Using <tt>pma_username</tt> and <tt>pma_password</tt> has been tested along with the usage of 'cookie' <tt>auth_type</tt>.</p>
3632 when trying to create a table with more than 14 fields.
3633 </a></h4>
3634 <p>
3635 We could reproduce this problem only under Win98/98SE. Testing under
3636 WinNT4 or Win2K, we could easily create more than 60 fields.
3637 <br />
3638 A workaround is to create a smaller number of fields, then come back to
3639 your table properties and add the other fields.
3640 </p>
3644 <p>
3645 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3646 with each script/website that use forms.<br />
3647 Upgrade or downgrade your Xitami server.
3648 </p>
3651 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3652 <p>
3653 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3654 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3655 don't seem to work.<br />
3657 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3658 the user's temporary directory, so they must be moved before closing
3659 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3662 </p>
3666 Explorer never stores the cookies.
3667 </a></h4>
3668 <p>
3669 MS Internet Explorer seems to be really buggy about cookies, at least till
3671 in this area!
3672 <br />
3673 Then, if you're running PHP 4.1.1, try to upgrade or downgrade... it may
3674 work!
3675 </p>
3679 rows.
3680 </a></h4>
3681 <p>
3683 </p>
3686 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3687 when trying to modify a row in a table with many fields, or with a text field
3688 </a></h4>
3689 <p>
3690 Your table neither have a primary key nor an unique one, so we must use a
3691 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
3692 those browsers, and this not happen in Netscape, for example. The
3693 workaround is to create a primary or unique key, or use another browser.
3694 <br />
3695 </p>
3699 page.
3700 </a></h4>
3701 <p>
3702 Some browsers support right-clicking into the frame you want to refresh,
3703 just do this in the right frame.<br />
3704 </p>
3708 query box.
3709 </a></h4>
3710 <p>
3711 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3712 Mozilla versions.<br />
3713 </p>
3717 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3718 </a></h4>
3719 <p>
3720 This is a Mozilla bug (see bug #26882 at
3722 </p>
3727 </a></h4>
3728 <p>
3729 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3730 data in octet-stream mode. Since we can't detect the specific Netscape
3731 version, we cannot workaround this bug.
3732 </p>
3736 wrong.</a></h4>
3738 <p> Please ensure that you have set your browser's character set to the one of the
3739 language file you have selected on phpMyAdmin's start page.
3740 Alternatively, you can try the auto detection mode that is supported by the
3741 recent versions of the most browsers.</p>
3744 <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
3747 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3748 Netscape and Mozilla do not have this problem.</p>
3751 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3752 I cannot manage two servers: I log in to the first one, then the other one,
3753 but if I switch back to the first, I have to log in on each operation.</a></h4>
3759 but nothing happens after that, only a blank screen.</a></h4>
3770 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3775 address and you are starting
3777 containing a domain name, or the reverse situation.</li>
3778 <li>Security settings in IE and/or Microsoft Security Center are
3779 too high, thus blocking scripts execution.</li>
3780 <li>The Windows Firewall is blocking Apache and MySQL. You must
3784 </ul>
3787 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3788 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3789 installed in their Firefox is causing the problem.</p>
3793 clause is generated when I browse a table.</a></h4>
3794 <p> This happens only when both of these conditions are met: using the
3804 </a></h4>
3805 <p>
3806 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3807 specifying a wrong field-type.<br />
3808 Common errors include:
3809 </p>
3810 <ul>
3813 </ul>
3814 <p>
3815 Also, look at the syntax chapter in the MySQL manual to confirm that your
3816 syntax is correct.
3817 </p>
3821 phpMyAdmin generates only one index with those two fields.
3822 </a></h4>
3823 <p>
3824 This is the way to create a multi-fields
3825 index. If you want two indexes, create the first one when creating the
3826 table, save, then display the table properties and click the Index link to
3827 create the other index.
3828 </p>
3832 <p>
3833 Since version 2.2.3, you have a checkbox for each field that can be null.
3835 field's value. Since version 2.5.5, you have to use the checkbox to get
3837 a literal NULL in the field, and not a NULL value (this works in PHP4).
3838 </p>
3843 <p> Click on a database or table name in the left frame, the properties will be
3845 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3846 statements that can be used to recreate your database/table.
3847 <br /><br />
3849 transmit the resulting dump to your station. Depending on your PHP
3850 configuration, you will see options to compress the dump. See also the
3852 configuration variable.<br /><br />
3855 this document.</p>
3860 </a></h4>
3862 <p> Click on a database name in the left frame, the properties will be
3864 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3866 the path to your dump filename, or use the Browse button. Then click Go.
3867 <br /><br />
3869 that you upgrade to take advantage of the new features.
3870 <br /><br />
3872 in this document.
3873 </p>
3878 <p> Here is an example with the tables persons, towns and countries, all
3880 table, create it as explained in the configuration section. Then create the
3881 example tables:</p>
3883 <pre>
3884 CREATE TABLE REL_countries (
3885 country_code char(1) NOT NULL default '',
3886 description varchar(10) NOT NULL default '',
3887 PRIMARY KEY (country_code)
3888 ) TYPE=MyISAM;
3890 INSERT INTO REL_countries VALUES ('C', 'Canada');
3892 CREATE TABLE REL_persons (
3893 id tinyint(4) NOT NULL auto_increment,
3894 person_name varchar(32) NOT NULL default '',
3896 country_code char(1) NOT NULL default '',
3897 PRIMARY KEY (id)
3898 ) TYPE=MyISAM;
3900 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3901 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3903 CREATE TABLE REL_towns (
3905 description varchar(30) NOT NULL default '',
3906 PRIMARY KEY (town_code)
3907 ) TYPE=MyISAM;
3909 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3910 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3911 </pre>
3917 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3921 </ul>
3929 <li>In the fields row, choose persons.person_name and click the
3931 <li>Do the same for towns.description and countries.descriptions in the
3934 the correct joins have been generated</li>
3936 </ul>
3940 <p>
3941 Starting from the previous example, create the pma_table_info as explained
3942 in the configuration section, then browse your persons table,
3943 and move the mouse over a town code or country code.
3944 <br /><br />
3945 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display field"
3946 enables: drop-down list of possible values.
3947 </p>
3950 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3951 <p>
3954 <br /><br />
3955 Then you need to think about your schema layout. Which tables will go on
3956 which pages?
3957 </p>
3958 <ul>
3964 page and click Go. If you like, you
3966 linked tables onto the new page.</li>
3967 <li>Select the name of the new page (making sure the Edit radio button
3968 is selected) and click Go.</li>
3970 Coordinates are relative; your diagram will
3971 be automatically scaled to fit the page. When initially placing tables
3972 on the page, just pick any coordinates -- say, 50x50. After clicking
3974 position the element correctly.</li>
3976 first be sure to click the Save
3977 button beneath the list of tables and coordinates, to save any changes
3978 you made there. Then scroll all the way down, select the
3980 you want, and click Go.</li>
3981 <li>Internet Explorer for Windows may suggest an incorrect filename when
3986 browsers on Windows, do not have this problem.</li>
3987 </ul>
3991 columns!</a></h4>
3993 <p> No, it's MySQL that is doing
3999 underscores in the database name?</a></h4>
4001 <p> If you do not put a backslash before the underscore, this is a wildcard
4004 john2db ...<br /><br />
4006 If you put a backslash before the underscore, it means that the database
4007 name will have a real underscore.</p>
4011 statistics pages?</a></h4>
4022 if it already exists during the import. It does NOT drop the table after
4023 your export, it only affects the import file.</li>
4025 Otherwise, you may get an error if the table name exists but has a
4026 different structure.</li>
4028 (if any) will be included in backup.</li>
4030 field and table names formed with special characters are protected.</li>
4032 types set in the pmadb in the dump as
4034 </li>
4035 </ul>
4040 command, for better documentation (but resulting file is bigger).</li>
4042 once the INSERT verb and the table name.</li>
4045 </li>
4047 more info is provided in the
4049 but basically with this selected, invalid values are adjusted and
4050 inserted rather than causing the entire statement to fail.</li>
4051 </ul>
4055 in its name.</a></h4>
4058 is the normal way to reference a database and table name. Worse, MySQL
4059 will usually let you create a database with a dot, but then you cannot
4060 work with it, nor delete it.</p>
4073 for usage.<br />
4074 On a more recent pear version, I had problems with the state of Net_DIME
4075 being beta, so this single command
4077 needed modules.<br />
4078 If you use the Validator, you should be aware that any
4080 submit will be stored anonymously (database/table/column names,
4081 strings, numbers replaced with generic values). The Mimer
4084 We utilize it as free SOAP service.</p>
4088 it, but MySQL says "BLOB column '...' used in key specification without
4091 <p> The right way to do this, is to create the field without any indexes,
4093 dialog. On this page, you will be able to choose your BLOB field, and
4094 set a size to the index, which is the condition to create an index on
4095 a BLOB field.</p>
4099 editing fields?</a></h4>
4101 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4102 with many editing fields (table structure changes, row editing, etc.)
4103 (must be enabled in configuration - see.
4105 You can also have a look at the directive
4107 ('vertical') and see if this eases up editing for you.</p>
4111 WTF is this feature then useful for?</a></h4>
4113 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4114 on them. Otherwise you could just put a comment on the field. Because entering
4115 your own mimetype will cause serious syntax checking issues and validation,
4116 this introduces a high-risk false-user-input situation. Instead you have to
4117 initialize mimetypes using functions or empty mimetype definitions.<br />
4118 Plus, you have a whole overview of available mimetypes. Who knows all those
4119 mimetypes by heart so he/she can enter it at will?</p>
4123 can't I see any bookmarks below the query box? What is this variable for?
4124 </a></h4>
4126 <p> Any query you have executed can be stored as a bookmark on the page where the
4127 results are displayed. You will find a button labeled 'Bookmark this query'
4128 just at the end of the page.<br />
4129 As soon as you have stored a bookmark, it is related to the database you run
4130 the query on. You can now access a bookmark dropdown on each page, the query
4131 box appears on for that database.<br /><br />
4133 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4137 aware of that you HAVE to create a valid query, otherwise your query won't be
4138 even able to be stored in the database.<br />
4140 for your query will remain the way it is, but will be stripped of the /**/
4141 chars. So you can use:<br /><br />
4145 which will be expanded to<br /><br />
4149 in your query, where VARIABLE is the string you entered in the input box. If
4150 an empty string is provided, no replacements are made.<br /><br />
4152 A more complex example. Say you have stored this query:<br /><br />
4154 <br /><br />
4157 the full query will be:<br /><br />
4160 <br /><br />
4164 spaces inserted there
4165 will be later also inserted as spaces in your query and may lead to unexpected
4166 results especially when
4168 Your initial query which is going to be stored as a bookmark has to yield at
4169 least one result row so
4170 you can store the bookmark. You may have that to work around using well
4174 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4175 include exported table?</a></h4>
4177 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4178 document should look like following one (assuming you have table
4181 <pre>
4182 \documentclass{article} % or any class you want
4183 \usepackage{longtable} % for displaying table
4184 \begin{document} % start of document
4185 \include{table} % including exported table
4186 \end{document} % end of document
4187 </pre>
4191 access them.
4192 </a></h4>
4195 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4196 enable users to see all the database names.
4199 So if your users do not need those privileges, you can remove them and their
4200 databases list will shorten.</p>
4204 possible values for a field, based on some foreign table?</a></h4>
4206 <p> You have to setup appropriate links between the tables, and also
4210 foreign table, a drop-down list of values will be available.
4211 You will see two lists of values, the first list containing the key
4212 and the display field, the second list containing the display field
4213 and the key. The reason for this is to be able to type the first
4214 letter of either the key or the display field.<br /><br />
4216 For 100 values or more, a distinct window will appear, to browse foreign
4217 key values and choose one. To change the default limit of 100, see
4218 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4222 automatically when entering Browse mode for a table?</a></h4>
4224 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4225 </p>
4229 Excel files, how can I enable that?</a></h4>
4231 <p> Current version does support direct export to Microsoft Excel and Word
4232 versions 2000 and newer. If you need export older versions, you can use
4234 which works out of the box or you can
4236 several problems, most important are limitation of cell content to 255
4237 chars and no support for charsets, so think carefully whether you want to
4238 enable this.</b>. For enabling this you need to set
4242 module Spreadsheet_Excel_Writer into php include path. The
4243 installation can be done by following command:</p>
4245 <pre>
4246 pear -d preferred_state=beta install -a Spreadsheet_Excel_Writer
4247 </pre>
4249 <p> First part of switches set we want to install beta version of that module
4250 (no stable version available yet) and then we tell pear we want to satisfy
4251 dependencies.</p>
4253 <p> If you are running in PHP safe mode, you will have to set
4256 modules are located, for example:</p>
4258 <pre>
4259 safe_mode_include_dir = /usr/local/lib/php
4260 </pre>
4264 <pre>
4265 cd phpMyAdmin
4266 mkdir tmp
4267 chmod o+rwx tmp
4268 </pre>
4272 what happens to my column comments stored in pmadb?</a></h4>
4274 <p> Automatic migration of a table's pmadb-style column comments to the native
4275 ones is done whenever you enter Structure page for this table.</p>
4280 <p> First, for general information about BLOB streaming on MySQL, visit <a href="http://blobstreaming.org">blobstreaming.org</a>. We currently support streaming if you are running MySQL 5.1 with the PBXT and PBMS storage engines.</p>
4282 <ol>
4283 <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>
4284 <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>
4285 <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>
4286 <li>Ensure that your target table is under the PBXT storage engine and has a LONGBLOB column.</li>
4287 <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>
4288 <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>
4289 </ol>
4296 <p> Our Bug Tracker is located at
4298 under the Bugs section.<br /><br />
4300 But please first discuss your bug with other users:<br />
4306 existing language, where do I start?</a></h4>
4308 <p> Always use the current SVN version of your language file.
4310 don't know how to get the SVN version, please ask one of the developers.
4311 <br />
4312 Please note that we try not to use HTML entities like &eacute; in
4313 the translations, since we define the right character set in the file.
4314 With HTML entities, the text on JavaScript messages would not
4315 display correctly.
4316 However there are some entities that need to be there, for quotes
4317 ,non-breakable spaces, ampersands, less than, greater than.<br />
4318 You can then put your translations, as a zip file to avoid losing special
4319 characters, on the sourceforge.net translation tracker.<br />
4320 It would be a good idea to subscribe to the phpmyadmin-translators mailing
4321 list, because this is where we ask for translations of new messages.</p>
4325 phpMyAdmin. How should I proceed?</a></h4>
4330 <tt>git clone
4331 git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin</tt><br />
4332 </li>
4334 <li>generate patch with your changes:
4336 </li>
4339 tracker of the phpMyAdmin project</a>.
4340 </li>
4341 </ol>
4343 <p>More details on git are available on <a href="http://wiki.phpmyadmin.net/pma/Devel:Git">our wiki</a>.</p>
4345 <p> Write access to the repository is granted only to experienced developers who
4346 have already contributed something useful to phpMyAdmin.<br />
4352 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4354 <p> Please refer to
4355 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4356 </p>
4361 <p> If you use Apache web server, phpMyAdmin exports information about
4362 authentication to Apache environment and it can be used in Apache logs.
4363 Currently there are two variables available:
4364 </p>
4365 <dl>
4367 <dd>User name of currently active user (he does not have to be logged
4368 in).</dd>
4375 </dl>
4376 <p>
4378 </p>
4379 <pre>
4382 </pre>
4383 <p>
4384 You can then use any log analyzing tools to detect possible break-in
4385 attempts.
4386 </p>
4392 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4393 It allows you to connect to local as well as remote servers.This requires you to enter
4394 server host name, username, password, port and the name of the database. Therefore you can
4395 now synchronize your databases placed on the same server or some remote server.
4396 </p>
4398 <p>For more details see <a href="./documentation-gsoc/Synchronization_User_Manual.htm">How to synchronize</a>
4399 </p>
4401 <!-- DEVELOPERS -->
4404 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4405 great features have been written by other people and you too can help to
4406 make phpMyAdmin a useful tool.</p>
4408 <p> If you're planning to contribute source, please read the following
4409 information:</p>
4415 it free from other code.<br />
4416 Commonly used functions should be added to
4419 <li>Obviously, you're free to use whatever coding style you want. But
4420 please try to keep your code as simple as possible: beginners are
4421 using phpMyAdmin as an example application.<br />
4422 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4423 compliant on one hand, they fit the
4426 coding standards</a>
4427 on the other hand. Please pay attention to this.</li>
4428 <li>Please try to keep up the file-naming conventions. Table-related stuff
4431 <li>Please don't put message strings in your code, instead add the string
4436 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4437 better debug and profile their code.<br />
4438 Please see the
4440 options for more information.<br />
4441 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4442 lost during its re-entry into Earth's atmosphere and in memory of the
4443 brave men and women who gave their lives for the people of Earth.</li>
4444 </ul>
4448 <pre>
4459 </pre>
4461 <p>
4462 This program is free software; you can redistribute it and/or modify
4463 it under the terms of the GNU General Public License version 2,
4464 as published by the Free Software Foundation.
4465 </p>
4467 <p>
4468 This program is distributed in the hope that it will be useful,
4469 but WITHOUT ANY WARRANTY; without even the implied warranty of
4470 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4471 GNU General Public License for more details.
4472 </p>
4474 <p>
4475 You should have received a copy of the GNU General Public License
4476 along with this program; if not, write to the Free Software
4478 </p>
4480 <!-- CREDITS -->
4485 <ul>
4488 <ul>
4491 </ul></li>
4494 <ul>
4499 </ul></li>
4502 <ul>
4508 </ul></li>
4511 <ul>
4513 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4514 generate XHTML1.0 and CSS2 compliant codes</li>
4517 </ul></li>
4520 <ul>
4528 </ul></li>
4531 <ul>
4536 </ul></li>
4539 <ul>
4542 </ul></li>
4545 <ul>
4547 </ul></li>
4550 <ul>
4553 </ul></li>
4556 <ul>
4560 </ul></li>
4563 <ul>
4566 </ul></li>
4569 <ul>
4576 </ul></li>
4579 <ul>
4583 </ul></li>
4586 <ul>
4592 </ul></li>
4595 (http://sf.net/projects/phpmysqlformgen/)
4596 <ul>
4598 </ul></li>
4601 <ul>
4603 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4608 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4612 </ul></li>
4615 <ul>
4617 </ul></li>
4620 <ul>
4622 </ul></li>
4625 <ul>
4627 </ul></li>
4630 <ul>
4631 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4632 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4633 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4634 </ul></li>
4637 <ul>
4639 </ul></li>
4642 <ul>
4644 </ul></li>
4647 <ul>
4649 </ul></li>
4652 <ul>
4655 </ul></li>
4658 <ul>
4661 </ul></li>
4664 <ul>
4666 </ul></li>
4669 <ul>
4672 </ul></li>
4674 <li>Ivan A Kirillov
4675 <ul>
4677 </ul></li>
4680 <ul>
4682 </ul></li>
4685 <ul>
4687 </ul></li>
4690 <ul>
4692 </ul></li>
4695 <ul>
4697 </ul></li>
4700 <ul>
4702 </ul></li>
4705 <ul>
4707 </ul></li>
4709 </ul>
4711 <p>
4712 And also to the following people who have contributed minor changes,
4713 enhancements, bugfixes or support for a new language since version 2.1.0:
4714 </p>
4716 <p>
4717 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
4718 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
4719 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
4720 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
4722 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
4723 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
4724 Luís V., Martijn W. van der Lee,
4725 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
4727 </p>
4732 <p>
4733 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
4734 to create a web-based interface to MySQL using PHP3. Although I have not
4735 used any of his source-code, there are some concepts I've borrowed from
4736 him. phpMyAdmin was created because Peter told me he wasn't going to
4737 further develop his (great) tool.
4738 </p>
4739 <p>
4740 Thanks go to
4741 </p>
4742 <ul>
4744 code for the check when dropping a table or database. He also suggested
4745 that you should be able to specify the primary key on tbl_create.php3. To
4746 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
4747 well as a bug-report. Plus many smaller improvements.
4748 </li>
4750 were introduced in 1.3.0 (including quite significant ones like the
4751 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
4752 bug-fixes and help.
4753 </li>
4755 language-independent by outsourcing the strings to a separate file. He
4756 also contributed the French translation.
4757 </li>
4759 tbl_select.php3, a feature to display only some fields from a table.
4760 </li>
4762 functions in tbl_change.php3. He also added the
4764 </li>
4766 servers and is a regular contributor for bug-fixes.
4767 </li>
4769 features for 2.0.6.
4770 </li>
4771 </ul>
4772 <p>
4773 The following people have contributed minor changes, enhancements, bugfixes
4774 or support for a new language:
4775 </p>
4776 <p>
4777 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
4778 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
4779 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
4780 G. Wieggers.
4781 </p>
4782 <p>
4783 And thanks to everyone else who sent me email with suggestions, bug-reports
4784 and or just some feedback.
4785 </p>
4791 <ul>
4793 - the default name of Apache's directory-level configuration file.</li>
4797 - a software application that enables a user to display and interact with
4798 text, images, and other information typically located on a web page at a
4799 website on the World Wide Web.</li>
4801 - a free software/open source data compression algorithm and program
4802 developed by Julian Seward.</li>
4804 - an important World Wide Web technology that enables a client web browser
4805 to request data from a program executed on the Web server.</li>
4807 - a log or record of changes made to a project.</li>
4809 - a computer system that accesses a (remote) service on another computer
4810 by some kind of network.</li>
4812 - a set of data values of a particular simple type, one for each row of
4813 the table.</li>
4815 - a packet of information sent by a server to a World Wide Web browser
4816 and then sent back by the browser each time it accesses that server.</li>
4818 - Comma-separated values</li>
4821 - an organized collection of data.</li>
4824 - a PHP module that extends PHP with additional functionality.</li>
4826 - a list of commonly asked question and there answers.</li>
4828 - one part of divided data/columns.</li>
4830 - a field or group of fields in a database record that point to a key
4831 field or group of fields forming a key of another database record in some
4832 (usually different) table.</li>
4834 - the free PDF library</li>
4836 GD Graphics Library</a> - a library by Thomas Boutell and others for
4837 dynamically manipulating images.</li>
4840 - gzip is short for GNU zip, a GNU free software file compression
4841 program.</li>
4843 - any machine connected to a computer network, a node that has a hostname.</li>
4845 - the unique name by which a network attached device is known on a network.</li>
4847 (HyperText Transfer Protocol)</a>
4848 - the primary method used to transfer or convey information on the World
4849 Wide Web.</li>
4852 additional security measures.</li>
4853 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
4854 - a set of Internet-based services for servers using Microsoft Windows.</li>
4856 - a feature that allows quick access to the rows in a table.</li>
4858 - a data-oriented protocol used by source and destination hosts for
4859 communicating data across a packet-switched internetwork.</li>
4861 - a unique number that devices use in order to identify and communicate
4862 with each other on a network utilizing the Internet Protocol standard.</li>
4864 (Internet Server Application Programming Interface)</a>
4865 - the API of Internet Information Services (IIS).</li>
4867 - a business or organization that offers users access to the Internet and related services.</li>
4869 - a most commonly used standard method of lossy compression for
4870 photographic images.</li>
4876 - line of personal computers is designed, developed, manufactured, and
4877 marketed by Apple Computer.</li>
4878 <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>
4879 - the operating system which is included with all currently shipping Apple
4880 Macintosh computers in the consumer and professional markets.</li>
4882 - a cryptographic library.</li>
4884 - the MCrypt PHP extension.</li>
4885 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
4886 - an Internet Standard for the format of e-mail.</li>
4888 - some sort of extension for the Apache Webserver.</li>
4890 - a multithreaded, multi-user, SQL (Structured Query Language) Database
4891 Management System (DBMS).</li>
4893 - the improved MySQL client PHP extension.</li>
4895 - the MySQL client PHP extension.</li>
4897 - open standard for office documents.</li>
4898 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
4899 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
4901 (Portable Document Format)</a>
4902 - a file format developed by Adobe Systems for representing two
4903 dimensional documents in a device independent and resolution independent
4904 format.</li>
4906 - the PHP Extension and Application Repository.</li>
4908 - the perl-compatible regular expression functions for PHP</li>
4910 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
4911 programming language used mainly for developing server-side applications
4912 and dynamic web content, and more recently, a broader range of software
4913 applications.</li>
4915 - a connection through which data is sent and received.</li>
4917 - Request for Comments (RFC) documents are a series of memoranda
4918 encompassing new research, innovations, and methodologies applicable to
4919 Internet technologies.</li>
4923 - represents a single, implicitly structured data item in a table.</li>
4925 - a computer system that provides services to other computing
4926 systems over a network.</li>
4927 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/refman/5.0/en/storage-engines.html">Storage Engines</a>
4928 - handlers for different table types</li>
4930 - a form of inter-process communication.</li>
4932 Sockets Layer)</a>
4933 - a cryptographic protocol which provides secure communication on the Internet.</li>
4935 - Structured Query Language</li>
4937 - a set of data elements (cells) that is organized, defined and stored as
4938 horizontal rows and vertical columns where each item can be uniquely
4939 identified by a label or key or by it?s position in relation to other items.</li>
4942 - a type of archive file format: the Tape ARchive format.</li>
4944 - one of the core protocols of the Internet protocol suite.</li>
4948 - a sequence of characters, conforming to a standardized format, that is
4949 used for referring to resources, such as documents and images on the
4950 Internet, by their location.</li>
4952 - A computer (program) that is responsible for accepting HTTP requests
4953 from clients and serving them Web pages.</li>
4955 - a W3C-recommended general-purpose markup language for creating
4956 special-purpose markup languages, capable of describing many different
4957 kinds of data.</li>
4959 - a popular data compression and archival format.</li>
4961 - an open-source, cross-platform data compression library by Jean-loup
4962 Gailly and Mark Adler.</li>
4963 </ul>
4964 </div>
4967 <li>Copyright © 2003 - 2009 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
4970 <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>
4971 </ul>
4973 </body>
4974 </html>