| blob | f530db8f07d2678afb144c98b5f1233436e20286 |
3 <!--
4 vim: expandtab ts=4 sw=4 sts=4 tw=78
5 -->
8 <head>
14 </head>
18 <h1>
20 3.5.0-dev
21 Documentation
22 </h1>
23 </div>
25 <!-- TOP MENU -->
34 <li><a href="Documentation.html#faq"><abbr title="Frequently Asked Questions"> FAQ</abbr></a></li>
39 </ul>
44 phpMyAdmin homepage</a></li>
46 SourceForge phpMyAdmin project page</a></li>
48 Official phpMyAdmin wiki</a></li>
49 <li>Local documents:
52 </ul>
53 </li>
54 </ul>
56 <!-- REQUIREMENTS -->
63 , the Standard PHP Library (SPL) extension and JSON support.
64 </li>
67 currently the default), you should install the mbstring and ctype
68 extensions.
69 </li>
70 <li>You need GD2 support in PHP to display inline
72 original aspect ratio</li>
78 load pages significantly slower.
79 </li>
82 <li>To support BLOB streaming, see PHP and MySQL requirements
85 </ul>
86 </li>
89 </ul>
91 <!-- INTRODUCTION -->
94 <p> phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
95 a single database. To accomplish the latter you'll need a properly set up
96 MySQL user who can read/write only the desired database. It's up to you to
97 look up the appropriate part in the MySQL manual.
98 </p>
103 <li>create, copy, drop, rename and alter databases, tables, columns and
104 indexes</li>
105 <li>maintenance server, databases and tables, with proposals on server
106 configuration</li>
107 <li>execute, edit and bookmark any
109 batch-queries</li>
112 </li>
119 OpenDocument Text and Spreadsheet,
122 </li>
123 <li>import data and MySQL structures from 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>
127 <li>using Query-by-example (QBE), create complex queries automatically
128 connecting required tables</li>
130 your Database layout</li>
132 <li>transform stored data into any format using a set of predefined
133 functions, like displaying BLOB-data as image or download-link
134 </li>
142 <li>communicate in <a href="http://www.phpmyadmin.net/home_page/translations.php">62 different languages</a>
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>
346 <p> You can use your phpMyAdmin to create the tables for you. Please be aware
347 that you may need special (administrator) privileges to create the database
348 and tables, and that the script may need some tuning, depending on the
349 database name.</p>
354 section</a>. You will also need to have a controluser with the proper rights
361 unpacked one. Configuration files from old versions may
362 require some tweaking as some options have been changed or removed; in
364 so you better remove it from your file and just use the default one.
366 statement that you might find near the end of your configuration file.</p>
370 is version-specific.</p>
373 version 5.x or newer and if you use the phpMyAdmin configuration storage,
374 you should run the SQL script found in
381 where you want to give users access to their own database and don't want
382 them to play around with others.<br />
383 Nevertheless be aware that MS Internet Explorer seems to be really buggy
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>
443 configuration storage</a> be set up).
444 <br /></li>
447 on a set of particular databases. Normally you shouldn't give global
448 privileges to an ordinary user, unless you understand the impact of those
449 privileges (for example, you are creating a superuser).<br />
453 <pre>
454 GRANT ALL PRIVILEGES ON user_base.* TO 'real_user'@localhost IDENTIFIED BY 'real_password';
455 </pre>
457 What the user may now do is controlled entirely by the MySQL user
458 management system.<br />
460 authentication mode, you don't need to fill the user/password fields
462 array.</li>
463 </ul>
468 method and allows you to log in as any valid MySQL user.</li>
469 <li>Is supported with most PHP configurations. For
482 mode.</li>
483 </ul>
487 <ul><li>You can use this method as a replacement for the
489 (for example, if you're running
491 <li>Obviously, the user must enable cookies in the browser, but this is
492 now a requirement for all authentication modes.</li>
493 <li>With this mode, the user can truly log out of phpMyAdmin and log in back
494 with the same username.</li>
495 <li>If you want to log in to arbitrary server see
500 not required.</li>
501 </ul>
505 <ul><li>This mode is a convenient way of using credentials from another
506 application to authenticate to phpMyAdmin.</li>
507 <li>The other application has to store login information into
508 session data.</li>
510 section.</li>
511 </ul>
514 <ul><li>This mode is the less secure one because it requires you to fill the
516 $cfg['Servers'][$i]['user']</a> and
518 $cfg['Servers'][$i]['password']</a> fields (and as a result, anyone who
519 can read your config.inc.php can discover your username and password).
520 <br />
527 is an entry explaining how to protect your configuration file.</li>
528 <li>For additional security in this mode, you may wish to consider the Host
529 authentication
531 $cfg['Servers'][$i]['AllowDeny']['order']</a> and
533 $cfg['Servers'][$i]['AllowDeny']['rules']</a> configuration
534 directives.</li>
535 <li>Unlike cookie and http, does not require a user to log in when first
536 loading the phpMyAdmin site. This is by design but could allow any
537 user to access your installation. Use of some restriction method is
539 HTTP-AUTH directive or disallowing incoming HTTP requests at
540 one’s router or firewall will suffice (both of which
541 are beyond the scope of this manual but easily searchable with Google).</li>
542 </ul>
544 <p>
545 The Swekey is a low cost authentication USB key that can be used in
546 web applications.<br /><br />
547 When Swekey authentication is activated, phpMyAdmin requires the
548 users's Swekey to be plugged before entering the login page (currently
549 supported for cookie authentication mode only). Swekey Authentication is
550 disabled by default.<br /><br />
552 </p>
553 <pre>
554 $cfg['Servers'][$i]['auth_swekey_config'] = '/etc/swekey.conf';
555 </pre>
556 <p>
558 each user with their Swekey Id. It is important to place this file outside
559 of your web server's document root (in the example, it is located in <tt>/etc</tt>). A self documented sample file is provided
561 users' information.<br /><br />
562 If you want to purchase a Swekey please visit
564 since this link provides funding for phpMyAdmin.
565 </p>
566 <!-- CONFIGURATION -->
570 users:</span> PHP does not seem to like
574 before saving a script you have modified.</p>
579 section to create one. This file only needs to contain the parameters you want to
580 change from their corresponding default value in
583 <p> The parameters which relate to design (like colors) are placed in
586 your site specific code to be included on start and end of each page.</p>
590 (with full path) to your phpMyAdmin installation's directory.
593 some web servers are case–sensitive.
596 Starting with version 2.3.0, it is advisable to try leaving this
597 blank. In most cases phpMyAdmin automatically detects the proper
598 setting. Users of port forwarding will need to set PmaAbsoluteUri (<a
599 href="https://sourceforge.net/tracker/index.php?func=detail&aid=1340187&group_id=23067&atid=377409">more info</a>).
600 A good test is to browse a table, edit a row and save it. There should
601 be an error message if phpMyAdmin is having trouble auto–detecting
602 the correct value. If you get an error that this must be set or if
603 the autodetect code fails to detect your path, please post a bug
604 report on our bug tracker so we can improve the code.</dd>
608 with master / foreign – tables (see
610 <br />
611 If you tried to set this up and it does not work for you, have a look on
613 use it. You will find a link that will analyze why those features have
614 been disabled.<br />
615 If you do not want to use those features set this variable to
619 <dd>A warning is displayed on the main page if Suhosin is detected.
621 from appearing.</dd>
624 <dd>Disable the default warning that is displayed if mcrypt is missing for
625 cookie authentication.
627 from appearing.</dd>
634 domain to call phpMyAdmin inside a frame, and is a potential security
635 hole allowing cross-frame scripting attacks.</dd>
639 algorithm to encrypt the password.<br />
641 passphrase of your choice. It will be used internally by the blowfish
642 algorithm: you won’t be prompted for this passphrase. There is
643 no maximum length for this secret.<br /><br />
645 Since version 3.1.0 phpMyAdmin can generate this on the fly, but it
646 makes a bit weaker security as this generated secret is stored in
647 session and furthermore it makes impossible to recall user name from
648 cookie.</dd>
652 MySQL servers. Therefore, a
654 been added which contains the login information for the different servers.
655 The first
657 contains the hostname of the first server, the second
659 the hostname of the second server, etc. In
661 server definition, however you can put as many as you need in
663 have to define all settings, just those you need to change).</dd>
667 $i-th MySQL-server. E.g. localhost.</dd>
672 ignores this port number and connects with the socket, so if you want
673 to connect to a port different from the default port, use
676 </dd>
680 To determine the correct socket, check your MySQL configuration or, using the
682 Among the resulting information displayed will be the socket used.</dd>
685 <dd>Whether to enable SSL for connection to MySQL server.
686 </dd>
689 <dd>What type connection to use with the MySQL server. Your options are
691 is nearly guaranteed to be available on all MySQL servers, while
692 sockets are not supported on some platforms.<br /><br />
694 To use the socket mode, your MySQL server must be on the same machine
695 as the Web server.</dd>
698 <dd>What php MySQL extension to use for the connection. Valid options are:
699 <br /><br />
702 The classic MySQL extension.<br /><br />
705 The improved MySQL extension. This extension became available
706 with PHP 5.0.0 and is the recommended way to connect to a server
710 <dd>Whether to use a compressed protocol for the MySQL server connection
711 or not (experimental).</dd>
716 </dt>
718 all relational features (see
720 and, for a MySQL server running with
723 authentication mode).<br /><br />
726 cookie authentication modes (or 'config'
727 authentication mode since phpMyAdmin 2.2.1), you need to supply the
732 This account is used to check what databases the user will see at
733 login.<br />
737 In phpMyAdmin versions before 2.2.5, those were called
741 <tt>['<abbr title="HyperText Transfer Protocol">HTTP</abbr>'|'http'|'cookie'|'config'|'signon']</tt></dt>
742 <dd>Whether config or cookie or
744 should be used for this server.
746 is the plain old way: username and password are stored in
748 <li>'cookie' authentication mode
750 2.2.3 allows you to log in as any valid MySQL user with the
751 help of cookies. Username and password are stored in
752 cookies during the session and password is deleted when it
753 ends. This can also allow you to log in in arbitrary server if
754 <tt><a href="#AllowArbitraryServer" class="configrule">$cfg['AllowArbitraryServer']</a></tt> enabled.
755 </li>
756 <li>'<abbr title="HyperText Transfer Protocol">HTTP</abbr>' authentication (was called 'advanced' in previous versions and can be written also as 'http')
757 (<tt>$auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>'</tt>) as introduced in 1.3.0
758 allows you to log in as any valid MySQL user via HTTP-Auth.</li>
759 <li>'signon' authentication mode
761 as introduced in 2.10.0 allows you to log in from prepared PHP
762 session data or using supplied PHP script. This is useful for implementing single signon
763 from another application.
769 You need to
775 </ul>
778 for more information.
779 </dd>
781 <span id="cfg_Servers_auth_http_realm">$cfg['Servers'][$i]['auth_http_realm']</span> string<br />
782 </dt>
783 <dd>
784 When using auth_type = '<abbr title="HyperText Transfer Protocol">HTTP</abbr>', this field allows to define a custom
785 <abbr title="HyperText Transfer Protocol">HTTP</abbr> Basic Auth Realm which will be displayed to the user. If not explicitly
786 specified in your configuration, a string combined of "phpMyAdmin " and either
789 </dd>
791 <span id="cfg_Servers_auth_swekey_config">$cfg['Servers'][$i]['auth_swekey_config']</span> string<br />
792 </dt>
793 <dd>
795 names for hardware authentication. Leave empty to deactivate this feature.
796 </dd>
800 </dt>
801 <dd>
802 When using auth_type = 'config', this is the user/password-pair
803 which phpMyAdmin will use to connect to the
804 MySQL server. This user/password pair is not needed when <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
805 cookie authentication is used and should be empty.</dd>
807 <span
809 </dt>
810 <dd>
811 Allow attempt to log in without password when a login with password
812 fails. This can be used together with http authentication, when
813 authentication is done some other way and phpMyAdmin gets user name
814 from auth and uses empty password for connecting to MySQL. Password
815 login is still tried first, but as fallback, no password method is
816 tried.</dd>
819 </dt>
820 <dd>
821 If set to a (an array of) database name(s), only this (these) database(s)
822 will be shown to the user. Since phpMyAdmin 2.2.1, this/these
823 database(s) name(s) may contain MySQL wildcards characters
827 This setting is an efficient way to lower the server load since the
828 latter does not need to send MySQL requests to build the available
830 privileges rules of the MySQL database server</span>. If set, it just
831 means only these databases will be displayed but
833 <br /><br />
835 An example of using more that one database:
837 <br /><br />
839 As of phpMyAdmin 2.5.5 the order inside the array is used for sorting the
840 databases in the left frame, so that you can individually arrange your databases.<br />
841 If you want to have certain databases at the top, but don't care about the others, you do not
842 need to specify all other databases. Use:
844 instead to tell phpMyAdmin that it should display db3 and db4 on top, and the rest in alphabetic
845 order.</dd>
848 </dt>
849 <dd>Regular expression for hiding some databases from unprivileged users.
850 This only hides them
851 from listing, but a user is still able to access them (using, for example,
852 the SQL query area). To limit access, use the MySQL privilege system.
853 <br /><br />
858 More information on regular expressions can be found in the
860 PCRE pattern syntax</a> portion of the PHP reference manual.
861 </dd>
864 <dd>Only useful when using phpMyAdmin with multiple server entries. If set,
865 this string will be displayed instead of the hostname in the pull-down
866 menu on the main page. This can be useful if you want to show only
867 certain databases on your system, for example. For HTTP auth, all
868 non-US-ASCII characters will be stripped.</dd>
872 </dt>
873 <dd>The name of the database containing the phpMyAdmin configuration storage.
874 <br /><br />
877 section in this document to see the benefits of this feature,
878 and for a quick way of creating this database and the needed tables.
879 <br /><br />
881 If you are the only user of this phpMyAdmin installation, you can
882 use your current database to store those special tables; in this
883 case, just put your current database name in
885 set this parameter to the name of your central database containing
886 the phpMyAdmin configuration storage.</dd>
890 </dt>
892 useful for queries you often run.<br /><br />
894 To allow the usage of this functionality:
896 <li>enter the table name in
898 </ul>
899 </dd>
903 </dt>
905 which column is a key in another table (a foreign key). phpMyAdmin
906 currently uses this to
907 <ul><li>make clickable, when you browse the master table, the data values
908 that point to the foreign table;</li>
910 when browsing the master table, if you move the mouse to a column
911 containing a foreign key (use also the 'table_info' table);<br />
914 <li>in edit/insert mode, display a drop-down list of possible foreign
918 <li>display links on the table properties page, to check referential
919 integrity (display missing foreign keys) for each described key;
920 </li>
924 schema of your database (also uses the table_coords table).</li>
925 </ul>
927 The keys can be numeric or character.<br /><br />
929 To allow the usage of this functionality:
932 configuration storage</li>
933 <li>put the relation table name in
935 <li>now as normal user open phpMyAdmin and for each one of your
936 tables where you want to use this feature, click
938 columns.
939 </li>
940 </ul>
944 future development of the cross-db relations.
945 </dd>
949 </dt>
950 <dd>
951 Since release 2.3.0 you can describe, in a special 'table_info'
952 table, which column is to be displayed as a tool-tip when moving the
953 cursor over the corresponding key.<br />
954 This configuration variable will hold the name of this special
955 table. To allow the usage of this functionality:
957 <li>put the table name in
959 'pma_table_info')</li>
960 <li>then for each table where you want to use this feature,
962 to choose the column.</li>
963 </ul>
965 </dd>
969 </dt>
972 the relations between your tables. To do this it needs two tables
977 schema output).<br /><br />
981 To allow the usage of this functionality:
984 <li>put the correct table names in
987 </ul>
990 </dd>
994 </dt>
996 Since release 2.3.0 you can store comments to describe each column for
998 <br /><br />
1000 Starting with release 2.5.0, comments are consequently used on the table
1001 property pages and table browse view, showing up as tool-tips above the
1002 column name (properties page) or embedded within the header of table in
1003 browse view. They can also be shown in a table dump. Please see the
1004 relevant configuration directives later on.<br /><br />
1006 Also new in release 2.5.0 is a MIME-transformation system which is also
1008 Transformations</a> for further information. To use the
1009 MIME-transformation system, your column_info table has to have the three
1010 new columns 'mimetype', 'transformation', 'transformation_options'.
1011 <br /><br />
1013 To allow the usage of this functionality:
1015 <li>put the table name in
1017 'pma_column_info')</li>
1020 <pre>
1021 ALTER TABLE `pma_column_comments`
1022 ADD `mimetype` VARCHAR( 255 ) NOT NULL,
1023 ADD `transformation` VARCHAR( 255 ) NOT NULL,
1024 ADD `transformation_options` VARCHAR( 255 ) NOT NULL;
1025 </pre>
1028 renamed from<br />
1031 </ul>
1032 </dd>
1036 </dt>
1039 all queries you entered manually into the phpMyAdmin interface. If you
1040 don't want to use a table-based history, you can use the JavaScript-based
1041 history. Using that, all your history items are deleted when closing the
1042 window.<br /><br />
1044 Using
1046 you can specify an amount of history items you want to have on hold. On
1047 every login, this list gets cut to the maximum amount.<br /><br />
1049 The query history is only available if JavaScript is enabled in your
1050 browser.<br /><br />
1052 To allow the usage of this functionality:
1056 (e.g. 'pma_history')
1057 </li>
1058 </ul>
1059 </dd>
1063 </dt>
1064 <dd>
1065 Since release 3.5.0 you can show recently used tables in the left navigation frame.
1066 It helps you to jump across table directly, without the need to select the database,
1067 and then select the table. Using
1069 you can configure the maximum number of recent tables shown. When you select a table
1070 from the list, it will jump to the page specified in
1071 <a href="#cfg_LeftDefaultTabTable" class="configrule">$cfg['LeftDefaultTabTable']</a>.<br/><br/>
1073 Without configuring the storage, you can still access the recently used tables,
1074 but it will disappear after you logout.<br/><br/>
1076 To allow the usage of this functionality persistently:
1078 <ul>
1081 </ul>
1082 </dd>
1086 </dt>
1087 <dd>
1088 Since release 3.5.0 phpMyAdmin can be configured to remember several things
1089 (sorted column
1091 , column order, and column visibility from a database table) for browsing tables.
1092 Without configuring the storage, these features still can be used,
1093 but the values will disappear after you logout.<br/><br/>
1095 To allow the usage of these functionality persistently:
1097 <ul>
1099 <li>put the table name in <tt>$cfg['Servers'][$i]['table_uiprefs']</tt> (e.g. 'pma_table_uiprefs')</li>
1100 </ul>
1101 </dd>
1105 </dt>
1106 <dd>
1107 Since release 3.3.x a tracking mechanism is available.
1109 is executed by phpMyAdmin. The mechanism supports logging of data manipulation
1110 and data definition statements. After enabling it you can create versions of tables.
1111 <br/><br/>
1112 The creation of a version has two effects:
1114 <ul>
1116 <li>phpMyAdmin logs all commands which change the structure and/or data of the table and links these commands with the version number.</li>
1117 </ul>
1119 Of course you can view the tracked changes. On the "Tracking" page a complete report is available for every version.
1120 For the report you can use filters, for example you can get a list of statements within a date range.
1121 When you want to filter usernames you can enter * for all names or you enter a list of names separated by ','.
1122 In addition you can export the (filtered) report to a file or to a temporary database.
1123 <br/><br/>
1125 To allow the usage of this functionality:
1127 <ul>
1130 </ul>
1131 </dd>
1134 <span id="cfg_Servers_tracking_version_auto_create">$cfg['Servers'][$i]['tracking_version_auto_create']</span> boolean
1135 </dt>
1136 <dd>
1137 Whether the tracking mechanism creates versions for tables and views automatically. Default value is false.
1138 <br/><br/>
1139 If this is set to true and you create a table or view with
1141 <ul>
1144 </ul>
1146 and no version exists for it, the mechanism will
1147 create a version for you automatically.
1148 </dd>
1151 <span id="cfg_Servers_tracking_default_statements">$cfg['Servers'][$i]['tracking_default_statements']</span> string
1152 </dt>
1153 <dd>
1154 Defines the list of statements the auto-creation uses for new versions. Default value is
1155 <br/>
1157 <pre>CREATE TABLE,ALTER TABLE,DROP TABLE,RENAME TABLE,
1158 CREATE INDEX,DROP INDEX,
1159 INSERT,UPDATE,DELETE,TRUNCATE,REPLACE,
1160 CREATE VIEW,ALTER VIEW,DROP VIEW,
1161 CREATE DATABASE,ALTER DATABASE,DROP DATABASE</pre>
1162 </dd>
1165 <span id="cfg_Servers_tracking_add_drop_view">$cfg['Servers'][$i]['tracking_add_drop_view']</span> boolean
1166 </dt>
1167 <dd>
1168 Whether a DROP VIEW IF EXISTS statement will be added as first line to the log when creating a view. Default value is true.
1169 <br/><br/>
1170 </dd>
1174 <span id="cfg_Servers_tracking_add_drop_table">$cfg['Servers'][$i]['tracking_add_drop_table']</span> boolean
1175 </dt>
1176 <dd>
1177 Whether a DROP TABLE IF EXISTS statement will be added as first line to the log when creating a table. Default value is true.
1178 <br/><br/>
1179 </dd>
1182 <span id="cfg_Servers_tracking_add_drop_database">$cfg['Servers'][$i]['tracking_add_drop_database']</span> boolean
1183 </dt>
1184 <dd>
1185 Whether a DROP DATABASE IF EXISTS statement will be added as first line to the log when creating a database. Default value is true.
1186 <br/><br/>
1187 </dd>
1191 </dt>
1192 <dd>
1193 Since release 3.4.x phpMyAdmin allows users to set most preferences by themselves
1194 and store them in the database.
1195 <br /><br />
1198 still personalize phpMyAdmin, but settings will be saved in browser's local storage,
1199 or, it is is unavailable, until the end of session.
1200 <br /><br />
1202 To allow the usage of this functionality:
1204 <ul>
1206 configuration storage</li>
1208 </ul>
1209 </dd>
1213 </dt>
1215 to visually manage the relations.
1216 <br /><br />
1218 To allow the usage of this functionality:
1221 <li>put the table name in <tt>$cfg['Servers'][$i]['designer_coords']</tt> (e.g. 'pma_designer_coords')
1222 </li>
1223 </ul>
1224 </dd>
1226 <dt><span id="cfg_Servers_MaxTableUiprefs">$cfg['Servers'][$i]['MaxTableUiprefs']</span> integer
1227 </dt>
1231 When tables are dropped or renamed, table_uiprefs may contain invalid
1232 data (referring to tables which no longer exist).<br />
1233 We only keep this number of newest rows in table_uiprefs and automatically delete older rows.</dd>
1236 </dt>
1238 column_info table got enhanced with three new columns. If the above variable
1240 latest table structure available. If not, it will emit a warning to the
1241 superuser.<br /><br />
1243 You can disable this checking behavior by setting the variable to false,
1244 which should offer a performance increase.<br /><br />
1246 Recommended to set to FALSE, when you are sure, your table structure is
1247 up to date.</dd>
1249 boolean</dt>
1250 <dd>Whether to allow root access. This is just a shortcut for the AllowDeny rules below.
1251 </dd>
1253 boolean</dt>
1254 <dd>Whether to allow logins without a password. The default
1256 to a MySQL server with was left with an empty password for root or
1257 on which an anonymous (blank) user is defined.
1258 </dd>
1261 </dt>
1263 authorization is disabled.<br /><br />
1266 all deny rules followed by allow rules. Access is allowed by default. Any
1267 client which does not match a Deny command or does match an Allow command
1268 will be allowed access to the server. <br /><br />
1271 applies all allow rules followed by deny rules. Access is denied by
1272 default. Any client which does not match an Allow directive or does
1273 match a Deny directive will be denied access to the server.<br /><br />
1275 If your rule order is set to 'explicit', authorization is
1276 performed in a similar fashion to rule order 'deny,allow', with the
1280 and was available in Apache by specifying allow and deny rules without
1281 setting any order.<br /><br />
1283 Please also see <a
1285 address behind proxies.
1286 </dd>
1288 <span id="cfg_Servers_AllowDeny_rules">$cfg['Servers'][$i]['AllowDeny']['rules']</span> array of strings
1289 </dt>
1290 <dd>The general format for the rules is as such:
1292 <pre>
1294 </pre>
1299 well (please note that those containing SERVER_ADDRESS might not be
1300 available on all webservers):
1301 <pre>
1307 </pre>
1309 Having an empty rule list is equivalent to either using
1315 following work:<br />
1317 <tt>xxx.xxx.xxx.[yyy-zzz]</tt> (an <abbr title="Internet Protocol">IP</abbr> address range)<br />
1318 <tt>xxx.xxx.xxx.xxx/nn</tt> (CIDR, Classless Inter-Domain Routing type <abbr title="Internet Protocol">IP</abbr> addresses)<br />
1319 But the following does not work:<br />
1322 Also IPv6 addresses are not supported.
1323 </dd>
1325 <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.
1326 </dd>
1327 <dt><span id="cfg_Servers_ShowDatabasesCommand">$cfg['Servers'][$i]['ShowDatabasesCommand']</span> string</dt>
1329 DATABASES</tt> command used to fetch the name of available databases will
1330 probably be too slow, so it can be replaced by faster commands (see
1332 </dd>
1334 <dd>Whether to count the number of tables for each database when preparing the list of databases for the navigation frame.
1335 </dd>
1337 <dd>Name of PHP script to be sourced and executed to obtain
1338 login credentials. This is alternative approach to session based single
1339 signon. The script needs to provide function
1341 password, accepting single parameter of existing username (can be empty).
1343 </dd>
1344 <dt><span id="cfg_Servers_SignonSession">$cfg['Servers'][$i]['SignonSession']</span> string</dt>
1345 <dd>Name of session which will be used for signon authentication method.
1347 this is session which phpMyAdmin uses internally. Takes effect only if
1349 is not configured.
1350 </dd>
1352 <dd>URL where user will be redirected to log in for signon authentication method. Should be absolute including protocol.
1353 </dd>
1355 <dd>URL where user will be redirected after logout (doesn't affect config authentication method). Should be absolute including protocol.
1356 </dd>
1359 <dd>If you have more than one server configured, you can set
1361 that server when phpMyAdmin is started, or set it to 0 to be given a
1362 list of servers without logging in.<br />
1364 MUST be set to that server.</dd>
1367 <dd>Defines whether to refresh only parts of certain pages using Ajax
1368 techniques. Applies only where a non-Ajax behavior is possible;
1369 for example, the Designer feature is Ajax-only so this directive
1370 does not apply to it.</dd>
1373 <dd>Enables check for latest versions using javascript on main phpMyAdmin
1374 page.</dd>
1377 <dd>The maximum number of database names to be displayed in the
1378 navigation frame and the database list.</dd>
1381 <dd>The maximum number of table names to be displayed in the
1382 main panel's list (except on the Export page). This limit is also enforced in the navigation panel
1383 when in Light mode.</dd>
1389 <dd>The maximum number of characters when a SQL query is displayed. The
1390 default limit of 1000 should be correct to avoid the display of tons
1391 of hexadecimal codes that represent BLOBs, but some users have real
1392 SQL queries that are longer than 1000 characters. Also, if a query's
1393 length exceeds this limit, this query is not saved in the history.</dd>
1396 <dd>Defines whether to use GZip output buffering for increased
1398 Set to true/false for enabling/disabling. When set to 'auto' (string),
1399 phpMyAdmin tries to enable output buffering and will automatically disable
1400 it if your browser has some problems with buffering. IE6 with a certain patch
1401 is known to cause data corruption when having enabled buffering.</dd>
1404 <dd>Whether <a href="http://php.net/manual/en/features.persistent-connections.php">persistent connections</a>
1405 should be used or not. Works with following extensions:
1406 <ul>
1407 <li>mysql (<a href="http://php.net/manual/en/function.mysql-pconnect.php">mysql_pconnect</a>),</li>
1408 <li>mysqli (requires PHP 5.3.0 or newer, <a href="http://php.net/manual/en/mysqli.persistconns.php">more information</a>).</li>
1409 </ul></dd>
1415 <dd>Set the number of seconds a script is allowed to run. If seconds is set
1416 to zero, no time limit is imposed.<br />
1417 This setting is used while importing/exporting dump files and in the
1418 Synchronize feature but has no effect when PHP is running in safe mode.</dd>
1425 <dd>Set the number of bytes a script is allowed to allocate. If set
1426 to zero, no limit is imposed.<br />
1427 This setting is used while importing/exporting dump files and at some
1428 other places in phpMyAdmin so you definitely don't want to put here
1429 a too low value. It has no effect when PHP is running in safe mode.<br />
1430 You can also use any string as in php.ini, eg. '16M'. Ensure
1434 <dd>Mark used tables and make it possible to show databases with locked
1439 generated by phpMyAdmin should be displayed or not.</dd>
1442 <dd>Defines whether normal users (non-administrator) are allowed to
1443 delete their own database or not. If set as FALSE, the link "Drop
1445 mydatabase" will be rejected. Quite practical for
1447 customers.<br />
1448 Please note that this limitation of SQL queries is not as strict as
1449 when using MySQL privileges. This is due to nature of SQL queries
1450 which might be quite complicated. So this choice should be viewed as
1451 help to avoid accidental dropping rather than strict privilege
1452 limitation.</dd>
1456 displayed when you're about to lose data.</dd>
1459 <dd>Define whether the previous login should be recalled or not in cookie
1460 authentication mode.<br /><br />
1462 This is automatically disabled if you do not have configured
1464 </dd>
1467 <dd>Define how long is login cookie valid. Please note that php
1468 configuration option <a href="http://php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime">session.gc_maxlifetime</a>
1469 might limit session validity and if session is lost, login cookie is
1471 not lower than the value of $cfg['LoginCookieValidity'].</dd>
1475 means that it will be kept for existing session. This is recommended
1476 for not trusted environments.</dd>
1479 <dd>If enabled (default), logout deletes cookies for all servers,
1480 otherwise only for current one. Setting this to false makes it easy to
1481 forget to log out from other server, when you are using more of
1482 them.</dd>
1488 <dd>Define whether phpMyAdmin will continue executing a multi-query
1489 statement if one of the queries fails. Default is to abort execution.</dd>
1492 <dd>Define whether phpMyAdmin will output the results of each query of a
1493 multi-query statement embedded into the
1498 <dd>If enabled, allows you to log in to arbitrary servers using cookie auth and permits to specify servers of your choice in the Synchronize dialog.
1499 <br /><br />
1502 MySQL servers behind the firewall where your
1504 </dd>
1513 <dd>Defines whether to use a select-based menu and display only the current
1514 tables in the left frame (smaller page). Only in Non-Lightmode you can
1515 use the feature to display nested folders using
1517 </dd>
1520 <dd>In light mode, defines whether to display the names of databases (in the
1521 selector) using a tree, see also
1523 </dd>
1526 string or array</dt>
1527 <dd>The string used to separate the parts of the database name when showing
1528 them in a tree. Alternatively you can specify more strings in an array
1529 and all of them will be used as a separator.</dd>
1532 <dd>Defines a string to be used to nest table spaces. Defaults to '__'.
1533 This means if you have tables like 'first__second__third' this will be
1535 If set to FALSE or empty, the feature is disabled. NOTE: You should
1536 not use this separator at the beginning or end of a
1537 table name or multiple times after another without any other
1538 characters in between.</dd>
1541 <dd>Defines how many sublevels should be displayed when splitting
1542 up tables by the above separator.</dd>
1545 <dd>The maximum number of recently used tables shown in the left navigation
1549 <dd>Defines whether to display table comment as tool-tip in left frame or
1550 not.</dd>
1553 <dd>If tool-tips are enabled and a DB comment is set, this will flip the
1554 comment and the real name. That means that if you have a table called
1555 'user0001' and add the comment 'MyName' on it, you will see the name
1556 'MyName' used consequently in the left frame and the tool-tip shows
1557 the real name of the DB.</dd>
1560 <dd>Same as <a href="#cfg_ShowTooltipAliasDB" class="configrule">$cfg['ShowTooltipAliasDB']</a>, except this works for table names.
1562 When setting this to 'nested', the Alias of the Tablename is only used
1563 to split/nest the tables according to the
1565 directive. So only the folder is called like the Alias, the tablename itself
1566 stays the real tablename.</dd>
1569 <dd>Defines whether or not to display the phpMyAdmin logo at the top of the left frame.
1572 <dd>Enter URL where logo in the navigation frame will point to.
1573 For use especially with self made theme which changes this.
1582 integer</dt>
1583 <dd>Defines the minimum number of tables to display a JavaScript filter box above the
1584 list of tables in the left frame.
1589 <dd>Defines whether or not to display a server choice at the top of the left frame.
1590 Defaults to FALSE.</dd>
1592 <dd>Defines whether to display this server choice as links instead of in a drop-down.
1593 Defaults to FALSE (drop-down).</dd>
1595 <dd>Defines whether to display database choice in light navigation frame as links
1596 instead of in a drop-down. Defaults to 'auto' - on main page list is
1597 shown, when database is selected, only drop down is displayed.</dd>
1600 <dd>Defines the tab displayed by default when clicking the small
1601 icon next to each table name in the navigation panel. Possible
1607 <dd>Defines whether or not to display space usage and statistics about databases
1608 and tables.<br />
1609 Note that statistics requires at least MySQL 3.23.3 and that, at this
1610 date, MySQL doesn't return such information for Berkeley DB tables.</dd>
1613 <dd>Defines whether to display detailed server information on main page.
1614 You can additionally hide more information by using
1616 </dd>
1621 </dt>
1624 not at the starting main (right) frame. This setting
1625 does not check MySQL commands entered directly.<br /><br />
1627 Please note that to block the usage of phpinfo() in scripts, you
1634 hard coded password value in the configuration file, end users can't
1635 be allowed to change their passwords.</dd>
1638 <dd>Defines whether to suggest a database name on the
1642 <dd>Defines whether navigation bar buttons and the right panel top menu
1643 contain text or symbols only. A value of TRUE displays icons, FALSE
1644 displays text and 'both' displays both icons and text.</dd>
1647 <dd>Defines whether a user should be displayed a
1651 <dd>Number of rows displayed when browsing a result set. If the result set
1658 DATE, DATETIME and TIMESTAMP, ascending order else- by default.</dd>
1662 option is ticked by default.</dd>
1666 from editing when browsing a table's content. Valid values are:
1671 </ul>
1672 </dd>
1675 <dd>Defines whether or not MySQL functions fields should be initially
1676 displayed in edit/insert mode. Since version 2.10, the user can
1677 toggle this setting from the interface.
1678 </dd>
1681 <dd>Defines whether or not type fields should be initially
1682 displayed in edit/insert mode. The user can
1683 toggle this setting from the interface.
1684 </dd>
1687 <dd>Defines which type of editing controls should be used for CHAR and
1688 VARCHAR columns. Possible values are:
1689 <ul><li>input - this allows to limit size of text to size of columns in
1690 MySQL, but has problems with newlines in columns</li>
1691 <li>textarea - no problems with newlines in columns, but also no
1692 length limitations</li>
1693 </ul>
1694 Default is old behavior so input.</dd>
1700 <dd>If there are fewer items than this in the set of foreign keys, then a
1701 drop-down box of foreign keys is presented, in the style described by the
1703 setting.</dd>
1706 <dd>For the foreign key drop-down fields, there are several methods of
1707 display, offering both the key and value data. The contents of the
1708 array should be one or both of the following strings:
1714 </dt>
1715 <dd>Defines whether to allow the use of zip/GZip/BZip2 compression when
1716 creating a dump file</dd>
1719 </dt>
1720 <dd>Defines whether to allow on the fly compression for GZip/BZip2
1721 compressed exports. This doesn't affect smaller dumps and allows users to
1722 create larger dumps that won't otherwise fit in memory due to php
1723 memory limit. Produced files contain more GZip/BZip2 headers, but all
1724 normal programs handle this correctly.</dd>
1728 mainframe.</dd>
1732 properties links (like 'Browse', 'Select', 'Insert', ...).<br /> Can be
1737 <dd>How many columns will be utilized to display the tables on the
1738 database property view? Default is 1 column. When setting this to a
1739 value larger than 1, the type of the database will be omitted for more
1740 display space.</dd>
1744 <dd>Defines the tab displayed by default on server view. Possible
1751 <dd>Defines the tab displayed by default on database view. Possible
1756 <dd>Defines the tab displayed by default on table view. Possible
1763 points to the MySQL documentation (type depends
1764 on <a href="#cfg_MySQLManualType" class="configrule">$cfg['MySQLManualType']</a>), appropriate help links are
1765 generated.<br />
1767 for more information about MySQL manuals and their types.</dd>
1770 <dd>Type of MySQL documentation:
1776 </ul>
1777 </dd>
1780 <dd>Defines the default language to use, if not browser-defined or
1781 user-defined.<br />
1782 The corresponding language file needs to be in
1784 </dd>
1787 <dd>Defines the default connection collation to use, if not
1788 user-defined.<br />
1790 documentation</a> for list of possible values. This setting is ignored when
1791 connected to Drizzle server.</dd>
1795 The corresponding language file needs to be in
1797 </dd>
1800 <dd>Limit list of available languages to those matching the given regular
1801 expression. For example if you want only Czech and English, you should
1805 <dd>You can select here which functions will be used for character set
1806 conversion. Possible values are:
1807 <ul><li>auto - automatically use available one (first is tested
1808 iconv, then recode)</li>
1812 </ul>
1813 Default is auto.</dd>
1814 <dd>
1815 Enabled charset conversion activates a pull-down menu
1816 in the Export and Import pages, to choose the character set when
1817 exporting a file. The default value in this menu comes from
1819 </dd>
1822 <dd>Specify some parameters for iconv used in charset conversion. See
1825 used, so that invalid characters will be transliterated.</dd>
1828 <dd>Available character sets for MySQL conversion. You can add your own (any of
1829 supported by recode/iconv) or remove these which you don't use.
1830 Character sets will be shown in same order as here listed, so if you
1831 frequently use some of these move them to the top.</dd>
1836 default empty, you need to fill in some trusted proxy servers if you
1837 want to use rules for IP addresses behind proxy.<br /><br />
1839 The following example specifies that phpMyAdmin should trust a
1841 <pre>
1842 $cfg['TrustedProxies'] =
1844 </pre>
1845 The $cfg['Servers'][$i]['AllowDeny']['rules'] directive uses the
1846 client's IP address as usual.
1847 </dd>
1851 MIME transformations.<br />
1852 Possible values are:
1856 </ul>
1857 Default is auto.
1858 </dd>
1861 <dd>
1862 We normally check the permissions on the configuration file to ensure
1863 it's not world writable. However, phpMyAdmin could be installed on
1864 a NTFS filesystem mounted on a non-Windows server, in which case the
1865 permissions seems wrong but in fact cannot be detected. In this case
1867 </dd>
1870 <dd>
1871 Limit for length of URL in links. When length would be above this limit, it
1872 is replaced by form with button.
1873 This is required as some web servers (IIS) have problems with long URLs.
1875 </dd>
1877 <dt
1879 <dd>
1880 In the database Structure page, it's possible to mark some tables then
1881 choose an operation like optimizing for many tables. This can slow down
1884 </dd>
1888 </dd>
1890 <dt><span id="cfg_NaviBackground">$cfg['NaviBackground']</span> string [CSS color for background]<br />
1892 </dt>
1893 <dd>The background styles used for both the frames.
1896 <dt id="cfg_NaviPointerBackground">$cfg['NaviPointerBackground'] string [CSS color for background]<br />
1898 <dd>The style used for the pointer in the navi frame.
1907 </dd>
1911 <dd>The style used for table headers. See
1916 </dd>
1920 </dd>
1922 <dt><span id="cfg_BrowsePointerBackground">$cfg['BrowsePointerBackground'] </span>string [CSS color]<br />
1924 <span id="cfg_BrowseMarkerBackground">$cfg['BrowseMarkerBackground'] </span>string [CSS color]<br />
1926 </dt>
1928 The former feature highlights the row over which your mouse is passing
1929 and the latter lets you visually mark/unmark rows by clicking on
1930 them. Highlighting / marking a column is done by hovering over /
1931 clicking the column's header (outside of the text).<br />
1936 <dd>You put here a valid CSS font family value, for example
1941 <dd>You put here a valid CSS font family value, for example
1955 </dt>
1957 This value will be emphasized (*2) for <abbr title="structured query language">SQL</abbr> query textareas and (*1.25) for
1959 The Char* values are used for CHAR and VARCHAR editing (if configured
1963 </dt>
1967 </dt>
1968 <dd>Defines if the whole textarea of the query box will be selected on
1969 click.</dd>
1972 <dd>Maximum number of characters shown in any non-numeric field on browse view.
1973 Can be turned off by a toggle button on the browse page.</dd>
1976 </dt>
1977 <dd>Defines the place where table row links (Edit, Copy,
1978 Delete) would be put when tables contents are displayed (you may
1979 have them displayed at the left side, right side, both sides or nowhere).
1985 Define which one is displayed by default. The first mode displays each
1986 row on a horizontal line, the second rotates the headers by 90
1987 degrees, so you can use descriptive headers even though columns only
1988 contain small values and still print them out. The vertical mode sorts
1989 each row on a vertical lineup.
1990 </dd>
1996 <dd>
1997 The HeaderFlipType can be set to 'auto', 'css' or 'fake'. When using
1998 'css' the rotation of the header for horizontalflipped is done via
1999 CSS. The CSS transformation currently works only in Internet
2000 Explorer.If set to 'fake' PHP does the transformation for you, but of
2001 course this does not look as good as CSS. The 'auto' option enables
2002 CSS transformation when browser supports it and use PHP based one
2003 otherwise.
2004 </dd>
2008 string or integer</dt>
2009 <dd>When editing/creating new columns in a table all fields normally get
2010 lined up one field a line. (default: 'horizontal'). If you set this to
2011 'vertical' you can have each field lined up vertically beneath each
2012 other. You can save up a lot of place on the horizontal direction and
2013 no longer have to scroll. If you set this to integer, editing of fewer
2014 columns will appear in 'vertical' mode, while editing of more columns
2015 still in 'horizontal' mode. This way you can still effectively edit
2016 large number of columns, while having full view on few of them.</dd>
2020 </dt>
2022 display of column comments in Browse or Property display. In browse
2023 mode, the comments are shown inside the header. In property mode,
2024 comments are displayed using a CSS-formatted dashed-line below the
2025 name of the column. The comment is shown as a tool-tip for that column.
2026 </dd>
2038 <dd>Whether to display a link to validate a query in any SQL Query box.
2045 <dd>
2046 The name of the directory where
2048 uploaded by other means than phpMyAdmin (for example, ftp). Those files
2049 are available under a drop-down box when you click the database or
2050 table name, then the Import tab.
2051 <br /><br />
2053 If you want different directory for each user, %u will be replaced
2054 with username.<br /><br />
2058 compressed formats is enabled).<br /><br />
2060 This feature is useful when your file is too big to be uploaded via
2062 uploads are disabled in PHP.<br /><br />
2064 Please note that if PHP is running in safe mode, this directory must
2065 be owned by the same user as the owner of the phpMyAdmin scripts.
2066 <br /><br />
2070 alternatives.
2071 </dd>
2074 <dd>
2075 The name of the directory where dumps can be saved.<br /><br />
2077 If you want different directory for each user, %u will be replaced
2078 with username.<br /><br />
2080 Please note that the directory must exist and has to be writable for
2081 the user running webserver.<br /><br />
2083 Please note that if PHP is running in safe mode, this directory must
2084 be owned by the same user as the owner of the phpMyAdmin scripts.
2085 </dd>
2088 <dd>
2089 The name of the directory where temporary files can be stored.
2090 <br /><br />
2092 This is needed for importing ESRI Shapefiles, see
2097 <br /><br />
2099 If the directory where phpMyAdmin is installed is subject to an
2101 temporary directory in some directory accessible by the web
2102 server. However for security reasons, this directory should be outside
2103 the tree published by webserver. If you cannot avoid having this
2104 directory published by webserver, place at least an empty
2106 possible.
2107 <br /><br />
2109 This directory should have as strict permissions as possible as the only
2110 user required to access this directory is the one who runs the
2111 webserver. If you have root privileges, simply make this user owner of
2112 this directory and make it accessible only by it:
2113 <br /><br />
2115 <pre>
2116 chown www-data:www-data tmp
2117 chmod 700 tmp
2118 </pre>
2120 If you cannot change owner of the directory, you can achieve a similar
2123 <pre>
2124 chmod 700 tmp
2125 setfacl -m "g:www-data:rwx" tmp
2126 setfacl -d -m "g:www-data:rwx" tmp
2127 </pre>
2129 If neither of above works for you, you can still make the directory
2131 system reading and writing data in this directory.
2132 </dd>
2135 <dd>
2136 In this array are defined default parameters for export, names of
2137 items are similar to texts seen on export page, so you can easily
2138 identify what they mean.
2139 </dd>
2142 <dd>
2143 Defines how the export form is displayed when it loads. Valid values are:
2144 <ul>
2147 <li><tt>custom-no-form</tt> same as <tt>custom</tt> but does not display the option of using quick export</li>
2148 </ul>
2149 </dd>
2152 <dd>
2153 In this array are defined default parameters for import, names of
2154 items are similar to texts seen on import page, so you can easily
2155 identify what they mean.
2156 </dd>
2159 <dd>
2160 Defines whether or not to save all edited cells at once in browse-mode.
2161 </dd>
2164 <dd>
2165 Defines whether or not type display direction option is shown
2166 when browsing a table.
2167 </dd>
2170 <dd>
2171 Repeat the headers every X cells, or 0 to deactivate.
2172 </dd>
2180 </dt>
2181 <dd>
2182 All those variables affect the query window feature. A <tt><abbr title="structured query language">SQL</abbr></tt> link
2183 or icon is always displayed on the left panel. If JavaScript is enabled in
2184 your browser, a click on this opens a distinct query window, which is
2185 a direct interface to enter <abbr title="structured query language">SQL</abbr> queries. Otherwise, the right panel
2186 changes to display a query box.<br /><br />
2188 The size of this query window can be customized with
2190 - both integers for the size in pixels. Note that normally, those
2192 theme you are using.<br /><br />
2196 opens the query window and puts the current query
2197 inside it. If set to false, clicking on the link puts the <abbr title="structured query language">SQL</abbr>
2198 query in the right panel's query box.
2199 <br /><br />
2200 The usage of the JavaScript query window is recommended if you have a
2201 JavaScript enabled browser. Basic functions are used to exchange quite
2202 a few variables, so most 4th generation browsers should be capable to
2203 use that feature. It currently is only tested with Internet Explorer 6
2204 and Mozilla 1.x.
2205 <br /><br />
2207 to a table, which has to be created by you (see <a
2209 all your queries will be appended to the form, but only as long as
2210 your window is opened they remain saved.
2211 <br /><br />
2212 When using the JavaScript based query window, it will always get
2213 updated when you click on a new table/db to browse and will focus if
2214 you click on "Edit <abbr title="structured query language">SQL</abbr>" after using a query. You can suppress updating
2215 the query window by checking the box "Do not overwrite this query from
2216 outside the window" below the query textarea. Then you can browse
2217 tables/databases in the background without losing the contents of the
2218 textarea, so this is especially useful when composing a query with
2219 tables you first have to look in. The checkbox will get automatically
2220 checked whenever you change the contents of the textarea. Please
2221 uncheck the button whenever you definitely want the query window to
2222 get updated even though you have made alterations.
2223 <br /><br />
2226 <br /><br />
2227 The query window also has a custom tabbed look to group the features.
2229 default tab to be used when opening the query window. It can be set to
2230 either 'sql', 'files', 'history' or 'full'.</dd>
2236 <dd>For InnoDB tables, determines for how large tables phpMyAdmin
2238 If the approximate row count as returned by
2241 count will be used.
2242 </dd>
2244 <dd>For VIEWs, since obtaining the exact count could have an
2245 impact on performance, this value is the maximum to be displayed, using
2247 any row counting.
2248 </dd>
2251 <dd>Sorts database and table names according to natural order (for example,
2252 t1, t2, t10). Currently implemented in the left panel (Light mode)
2253 and in Database view, for the table list.</dd>
2262 that users can't set through user preferences. For possible values, refer
2266 <dd>Activates in the user preferences a tab containing options for
2267 developers of phpMyAdmin.</dd>
2273 <dd>Allows you to specify window's title bar. You can use
2275 </dd>
2285 </dd>
2288 <dd>If theme manager is active, use this as the path of the subdirectory
2289 containing all the themes.</dd>
2303 </dt>
2304 <dd>Default queries that will be displayed in query boxes when user didn't
2305 specify any. You can use standard
2307 </dd>
2310 <dd>
2311 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
2312 default we use HTML to format the query, but you can disable this by
2314 </dd>
2317 <span id="cfg_SQP">$cfg['SQP']['fmtIndUnit']</span> string [<tt>em</tt>|<tt>px</tt>|<tt>pt</tt>|<tt>ex</tt>]</dt>
2318 <dd>For the pretty-printing of <abbr title="structured query language">SQL</abbr> queries, under some cases the part of a
2319 query inside a bracket is indented. By changing
2322 specifies the units of the indent amount that you specified. This is
2323 used via stylesheets.</dd>
2326 <dd>This array is used to define the colours for each type of element of
2327 the pretty-printed <abbr title="structured query language">SQL</abbr> queries. The tuple format is<br />
2329 If you specify an empty string for the color of a class, it is ignored
2330 in creating the stylesheet.
2331 You should not alter the class names, only the colour strings.<br />
2352 <li><b>alpha_variable</b> Identifiers matching a <abbr title="structured query language">SQL</abbr> variable <tt>"@foo"</tt></li>
2356 <li><b>quote_single</b> Single quotes <tt>'</tt></li>
2357 <li><b>quote_backtick</b> Backtick quotes <tt>`</tt></li>
2358 </ul>
2359 </dd>
2363 <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,
2364 as originally published on
2366 <br />
2367 For help in setting up your system to use the service, see the
2369 </dd>
2373 <dd>The SOAP service allows you to log in with <tt>anonymous</tt>
2374 and any password, so we use those by default. Instead, if
2375 you have an account with them, you can put your login details
2376 here, and it will be used in place of the anonymous login.</dd>
2377 </dl>
2378 </dd>
2381 <dd><b>DEVELOPERS ONLY!</b></dd>
2384 <dd><b>DEVELOPERS ONLY!</b><br />
2385 Enable logging queries and execution times to be displayed in the bottom
2386 of main page (right frame).</dd>
2389 <dd>All possible types of a MySQL column. In most cases you don't need to
2390 edit this.</dd>
2393 <dd>Possible attributes for columns. In most cases you don't need to edit
2394 this.</dd>
2397 <dd>A list of functions MySQL supports. In most cases you don't need to
2398 edit this.</dd>
2401 <dd>Mapping of column types to meta types used for preferring displayed
2402 functions. In most cases you don't need to edit this.</dd>
2405 <dd>Functions preferred for column meta types as defined in
2406 <a href="#cfg_RestrictColumnTypes" class="configrule">$cfg['RestrictColumnTypes']</a>. In most cases you don't need
2407 to edit this.</dd>
2410 <dd>Functions selected by default when inserting/changing row, Functions
2411 are defined for meta types from
2413 <code>first_timestamp</code>, which is used for first timestamp column
2414 in table.</dd>
2416 </dl>
2418 <!-- TRANSFORMATIONS -->
2424 </ol>
2428 <p> To enable transformations, you have to setup the <tt>column_info</tt> table
2430 section</a> on how to do so.</p>
2432 <p> You can apply different transformations to the contents of each column. The
2433 transformation will take the content of each column and transform it with
2434 certain rules defined in the selected transformation.</p>
2436 <p> Say you have a column 'filename' which contains a filename. Normally you would
2437 see in phpMyAdmin only this filename. Using transformations you can transform
2438 that filename into a HTML link, so you can click inside of the phpMyAdmin
2439 structure on the column's link and will see the file displayed in a new browser
2440 window. Using transformation options you can also specify strings to
2441 append/prepend to a string or the format you want the output stored in.</p>
2443 <p> For a general overview of all available transformations and their options,
2444 you can consult your
2445 <i><www.your-host.com>/<your-install-dir>/transformation_overview.php</i>
2446 installation.</p>
2448 <p> For a tutorial on how to effectively use transformations, see our
2450 the official phpMyAdmin homepage.</p>
2454 <p> Go to your <i>tbl_structure.php</i> page (i.e. reached through
2455 clicking on the 'Structure' link for a table). There click on
2456 "Change" (or change icon) and there you will see three new
2457 fields at
2458 the end of the line. They are called 'MIME-type', 'Browser transformation' and
2459 'Transformation options'.</p>
2461 <ul><li>The field 'MIME-type' is a drop-down field. Select the MIME-type
2462 that corresponds to the column's contents. Please note that
2463 transformations are inactive as long as no MIME-type is selected.</li>
2465 <li>The field 'Browser transformation' is a drop-down field. You can choose from a
2466 hopefully growing amount of pre-defined transformations. See below for information on
2467 how to build your own transformation.<br />
2469 There are global transformations and mimetype-bound transformations. Global transformations
2470 can be used for any mimetype. They will take the mimetype, if necessary, into regard.
2471 Mimetype-bound transformations usually only operate on a certain mimetype. There are
2472 transformations which operate on the main mimetype (like 'image'), which will most likely
2473 take the subtype into regard, and those who only operate on a
2474 specific subtype (like 'image/jpeg').<br />
2476 You can use transformations on mimetypes for which the function was not defined for. There
2477 is no security check for you selected the right transformation, so take care of what the
2478 output will be like.</li>
2480 <li>The field 'Transformation options' is a free-type textfield. You have to enter
2481 transform-function specific options here. Usually the transforms can operate with default
2482 options, but it is generally a good idea to look up the overview to see which options are
2483 necessary.<br />
2485 Much like the ENUM/SET-Fields, you have to split up several options using the format
2486 'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
2487 parsed as an array, leaving the first value the first element in the array, and so
2488 forth.<br />
2490 If you want to specify a MIME character set you can define it in the transformation_options.
2491 You have to put that outside of the pre-defined options of the specific mime-transform,
2493 for which you can specify 2 options and you want to append a character set, enter "'first
2494 parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
2496 </ul>
2500 <p> All mimetypes and their transformations are defined through single files in
2501 the directory 'libraries/transformations/'.</p>
2503 <p> They are stored in files to ease up customization and easy adding of new
2504 transformations.</p>
2506 <p> Because the user cannot enter own mimetypes, it is kept sure that transformations
2507 always work. It makes no sense to apply a transformation to a mimetype the
2508 transform-function doesn't know to handle.</p>
2510 <p> One can, however, use empty mime-types and global transformations which should work
2511 for many mimetypes. You can also use transforms on a different mimetype than what they where built
2512 for, but pay attention to option usage as well as what the transformation does to your
2513 column.</p>
2515 <p> There is a basic file called '<i>global.inc.php</i>'. This function can be included by
2516 any other transform function and provides some basic functions.</p>
2518 <p> There are 5 possible file names:</p>
2520 <ol><li>A mimetype+subtype transform:<br /><br />
2522 <tt>[mimetype]_[subtype]__[transform].inc.php</tt><br /><br />
2524 Please not that mimetype and subtype are separated via '_', which shall
2525 not be contained in their names. The transform function/filename may
2526 contain only characters which cause no problems in the file system as
2527 well as the PHP function naming convention.<br /><br />
2529 The transform function will the be called
2530 '<tt>PMA_transform_[mimetype]_[subtype]__[transform]()</tt>'.<br /><br />
2532 <b>Example:</b><br /><br />
2534 <tt>text_html__formatted.inc.php</tt><br />
2535 <tt>PMA_transform_text_html__formatted()</tt></li>
2537 <li>A mimetype (w/o subtype) transform:<br /><br />
2539 <tt>[mimetype]__[transform].inc.php</tt><br /><br />
2541 Please note that there are no single '_' characters.
2542 The transform function/filename may contain only characters which cause
2543 no problems in the file system as well as the PHP function naming
2544 convention.<br /><br />
2546 The transform function will the be called
2547 '<tt>PMA_transform_[mimetype]__[transform]()</tt>'.<br /><br />
2549 <b>Example:</b><br /><br />
2551 <tt>text__formatted.inc.php</tt><br />
2552 <tt>PMA_transform_text__formatted()</tt></li>
2554 <li>A mimetype+subtype without specific transform function<br /><br />
2556 <tt>[mimetype]_[subtype].inc.php</tt><br /><br />
2558 Please note that there are no '__' characters in the filename. Do not
2559 use special characters in the filename causing problems with the file
2560 system.<br /><br />
2562 No transformation function is defined in the file itself.<br /><br />
2564 <b>Example:</b><br /><br />
2566 <tt>text_plain.inc.php</tt><br />
2567 (No function)</li>
2569 <li>A mimetype (w/o subtype) without specific transform function<br /><br />
2571 <tt>[mimetype].inc.php</tt><br /><br />
2573 Please note that there are no '_' characters in the filename. Do not use
2574 special characters in the filename causing problems with the file system.
2575 <br /><br />
2577 No transformation function is defined in the file itself.<br /><br />
2579 <b>Example:</b><br /><br />
2581 <tt>text.inc.php</tt><br />
2582 (No function)</li>
2584 <li>A global transform function with no specific mimetype<br /><br />
2586 <tt>global__[transform].inc.php</tt><br /><br />
2588 The transform function will the be called
2589 '<tt>PMA_transform_global__[transform]()</tt>'.<br /><br />
2591 <b>Example:</b><br /><br />
2593 <tt>global__formatted</tt><br />
2594 <tt>PMA_transform_global__formatted()</tt></li>
2595 </ol>
2597 <p> So generally use '_' to split up mimetype and subtype, and '__' to provide a
2598 transform function.</p>
2600 <p> All filenames containing no '__' in themselves are not shown as valid transform
2601 functions in the dropdown.</p>
2603 <p> Please see the libraries/transformations/TEMPLATE file for adding your own transform
2604 function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
2605 without a transform function.</p>
2607 <p> To create a new transform function please see
2608 <tt>libraries/transformations/template_generator.sh</tt>.
2609 To create a new, empty mimetype please see
2610 <tt>libraries/transformations/template_generator_mimetype.sh</tt>.</p>
2612 <p> A transform function always gets passed three variables:</p>
2614 <ol><li><b>$buffer</b> - Contains the text inside of the column. This is the text,
2615 you want to transform.</li>
2616 <li><b>$options</b> - Contains any user-passed options to a transform function
2617 as an array.</li>
2618 <li><b>$meta</b> - Contains an object with information about your column.
2619 The data is drawn from the output of the
2621 function. This means, all object properties described on the
2623 available in this variable and can be used to transform a column accordingly
2624 to unsigned/zerofill/not_null/... properties.<br />
2625 The $meta->mimetype variable contains the original MIME-type of the
2626 column (i.e. 'text/plain', 'image/jpeg' etc.)</li>
2627 </ol>
2629 <p> Additionally you should also provide additional function to provide
2630 information about the transformation to the user. This function should
2631 have same name as transformation function just with appended
2632 <code>_info</code> suffix. This function accepts no parameters and returns
2633 array with information about the transformation. Currently following keys
2634 can be used:
2635 </p>
2636 <dl>
2637 <dt><code>info</code></dt>
2638 <dd>Long description of the transformation.</dd>
2639 </dl>
2641 <!-- FAQ -->
2648 <li><a href="#faqbrowsers">Browsers or client <abbr title="operating system">OS</abbr></a></li>
2653 </ol>
2655 <p> Please have a look at our
2657 the official phpMyAdmin homepage for in-depth coverage of phpMyAdmin's
2658 features and or interface.</p>
2664 action is required or phpMyAdmin sends a blank page or a page full of
2665 cryptic characters to my browser, what can I do?</a></h4>
2668 directive to <tt>FALSE</tt> in your <i>config.inc.php</i> file and the
2669 <tt>zlib.output_compression</tt> directive to <tt>Off</tt> in your php
2670 configuration file.<br /></p>
2675 <p> You should first try the latest versions of Apache (and possibly MySQL).<br />
2676 See also the
2678 entry about PHP bugs with output buffering.<br />
2679 If your server keeps crashing, please ask for help in the various Apache
2680 support groups.</p>
2689 application misbehaved by not returning a complete set of
2691 </h4>
2693 <p> You just forgot to read the <i>install.txt</i> file from the PHP distribution.
2694 Have a look at the last message in this
2696 official PHP bug database.</p>
2701 and/or many error messages with the
2704 <p> This is a known problem with the PHP
2706 filter: it's not so stable. Please use instead the cookie authentication mode.
2707 </p>
2712 <p> This seems to be a PWS bug. Filippo Simoncini found a workaround (at this
2713 time there is no better fix): remove or comment the <tt>DOCTYPE</tt>
2714 declarations (2 lines) from the scripts <i>libraries/header.inc.php</i>,
2715 <i>libraries/header_printview.inc.php</i>, <i>index.php</i>,
2716 <i>navigation.php</i> and <i>libraries/common.lib.php</i>.</p>
2721 work.</a></h4>
2723 <p> These features are based on the <tt>gzencode()</tt> and <tt>bzcompress()</tt>
2724 PHP functions to be more independent of the platform (Unix/Windows, Safe Mode
2725 or not, and so on). So, you must have Zlib/Bzip2
2726 support (<tt>--with-zlib</tt> and <tt>--with-bz2</tt>).<br /></p>
2730 an error about safe mode being in effect.</a></h4>
2732 <p> Your uploaded file is saved by PHP in the "upload dir", as
2733 defined in <i>php.ini</i> by the variable <tt>upload_tmp_dir</tt> (usually
2734 the system default is <i>/tmp</i>).<br />
2735 We recommend the following setup for Apache servers running in safe mode,
2736 to enable uploads of files while being reasonably secure:</p>
2738 <ul><li>create a separate directory for uploads: <tt>mkdir /tmp/php</tt></li>
2739 <li>give ownership to the Apache server's user.group:
2740 <tt>chown apache.apache /tmp/php</tt></li>
2741 <li>give proper permission: <tt>chmod 600 /tmp/php</tt></li>
2742 <li>put <tt>upload_tmp_dir = /tmp/php</tt> in <i>php.ini</i></li>
2743 <li>restart Apache</li>
2744 </ul>
2751 phpMyAdmin running on a secure server. My browser is Internet Explorer and
2752 I'm using the Apache server.</a></h4>
2754 <p> As suggested by "Rob M" in the phpWizard forum, add this line to
2755 your <i>httpd.conf</i>:</p>
2759 <p> It seems to clear up many problems between Internet Explorer and SSL.</p>
2763 uploading a file from the query box.</a></h4>
2765 <p> Since version 2.2.4, phpMyAdmin supports servers with open_basedir
2766 restrictions. However you need to create temporary directory and
2768 The uploaded files will be moved there, and after execution of your
2774 <p> The MySQL manual explains how to
2776 reset the permissions</a>.</p>
2786 </h4>
2788 <p> In previous MySQL versions, the <tt>User</tt> and <tt>Password</tt>columns
2789 were named <tt>user</tt> and <tt>password</tt>. Please modify your column
2790 names to align with current standards.</p>
2795 </h4>
2797 <p> Starting with version 2.7.0, the import engine has been re–written and these
2798 problems should not occur. If possible, upgrade your phpMyAdmin to the latest version
2799 to take advantage of the new import features.</p>
2801 <p> The first things to check (or ask your host provider to check) are the
2802 values of <tt>upload_max_filesize</tt>, <tt>memory_limit</tt> and
2803 <tt>post_max_size</tt> in the <i>php.ini</i> configuration file.
2804 All of these three settings limit the maximum size of data that can be
2805 submitted and handled by PHP. One user also said that post_max_size
2806 and memory_limit need to be larger than upload_max_filesize.<br /> <br />
2808 There exist several workarounds if your upload is too big or your
2809 hosting provider is unwilling to change the settings:</p>
2812 feature. This allows one to
2813 upload a file to the server via scp, ftp, or your favorite file transfer
2814 method. PhpMyAdmin is then able to import the files from the temporary
2816 section</a> of this document.</li>
2818 BigDump</a>) to split the files before uploading. We cannot support this
2819 or any third party applications, but are aware of users having success
2820 with it.</li>
2821 <li>If you have shell (command line) access, use MySQL to import the files
2822 directly. You can do this by issuing the "source" command from
2823 within MySQL: <tt>source <i>filename.sql</i></tt>.</li>
2824 </ul>
2828 support?</a></h4>
2830 <p> Since phpMyAdmin 3.0.x, only MySQL 5.0.1 and newer are supported. For
2831 older MySQL versions, you need to use the latest 2.x branch. phpMyAdmin can
2832 connect to your MySQL server using PHP's classic
2835 is available in PHP 5.0. The latter one should be used unless you have a
2836 good reason not to do so.<br />
2837 When compiling PHP, we strongly recommend that you manually link the MySQL
2838 extension of your choice to a MySQL client library of at least the same
2839 minor version since the one that is bundled with some PHP distributions is
2843 (versions 5.1 and 5.2 were tested).<br /><br />
2845 </p>
2849 message, "Client does not support authentication protocol requested
2850 by server; consider upgrading MySQL client"</a></h5>
2852 <p> You tried to access MySQL with an old MySQL client library. The version of
2853 your MySQL client library can be checked in your phpinfo() output.
2854 In general, it should have at least the same minor version as your server
2858 This problem is generally caused by using MySQL version 4.1 or newer. MySQL
2859 changed the authentication hash and your PHP is trying to use the old method.
2861 with the proper client library to match your MySQL installation. Your
2862 chosen extension is specified in <a href="#cfg_Servers_extension" class="configrule">$cfg['Servers'][$i]['extension']</a>.
2863 More information (and several workarounds) are located in the
2865 </p>
2872 script seems not to know the font face I'm using!</a></h4>
2874 <p> The "FPDF" library we're using for this feature requires some
2875 special files to use font faces.<br />
2877 these files.</p>
2881 check PHP Configuration".</a></h4>
2883 <p> To connect to a MySQL server, PHP needs a set of MySQL functions called
2884 "MySQL extension". This extension may be part of the PHP
2885 distribution (compiled-in), otherwise it needs to be loaded dynamically. Its
2886 name is probably <i>mysql.so</i> or <i>php_mysql.dll</i>. phpMyAdmin tried
2887 to load the extension but failed.<br /><br />
2889 Usually, the problem is solved by installing a software package called
2890 "PHP-MySQL" or something similar.</p>
2895 and I cannot log in using cookie auth.</a></h4>
2897 <p> In <i>php.ini</i>, set <tt>mysql.max_links</tt> higher than 1.</p>
2901 so I cannot upload.</a></h4>
2903 <p> This is most likely because in <i>php.ini</i>, your <tt>file_uploads</tt>
2904 parameter is not set to "on".</p>
2908 a new table the table and column names are changed to lowercase!</a></h4>
2910 <p> This happens because the MySQL directive <tt>lower_case_table_names</tt>
2911 defaults to 1 (<tt>ON</tt>) in the Win32 version of MySQL. You can change
2912 this behavior by simply changing the directive to 0 (<tt>OFF</tt>):<br />
2913 Just edit your <tt>my.ini</tt> file that should be located in your Windows
2914 directory and add the following line to the group [mysqld]:</p>
2916 <pre>set-variable = lower_case_table_names=0</pre>
2918 <p> Next, save the file and restart the MySQL service. You can always check the
2919 value of this directive using the query</p>
2921 <pre>SHOW VARIABLES LIKE 'lower_case_table_names';</pre>
2928 and I get problems, such as undefined variables when I run a
2931 <p> A tip from Jose Fandos: put a comment on the following two lines
2932 in httpd.conf, like this:</p>
2934 <pre>
2935 # mod_gzip_item_include file \.php$
2937 </pre>
2939 <p> as this version of mod_gzip on Apache (Windows) has problems handling
2940 PHP scripts. Of course you have to restart Apache.</p>
2945 I get the error "No input file specified" when trying to
2946 run phpMyAdmin.</a></h4>
2948 <p> This is a permission problem. Right-click on the phpmyadmin folder
2949 and choose properties. Under the tab Security, click on "Add"
2950 and select the user "IUSR_machine" from the list. Now set his
2951 permissions and it should work.</p>
2955 db_structure.php with plenty of tables).</a></h4>
2958 GZIP output buffering is enabled. If you turn off it (by
2960 in <i>config.inc.php</i>), it should work. This bug will be fixed in
2961 PHP 5.0.0.</p>
2965 message 'Errorcode: 13'. What does this mean?</a></h4>
2967 <p> This can happen due to a MySQL bug when having database / table names with
2968 upper case characters although <tt>lower_case_table_names</tt> is set to 1.
2969 To fix this, turn off this directive, convert all database and table names
2970 to lower case and turn it on again. Alternatively, there's a bug-fix
2971 available starting with MySQL 3.23.56 / 4.0.11-gamma.</p>
2975 and the columns are duplicated.</a></h4>
2977 <p> It is possible to configure Apache in such a way that PHP has problems
2978 interpreting .php files.</p>
2980 <p> The problems occur when two different (and conflicting) set of directives
2981 are used:</p>
2983 <pre>
2984 SetOutputFilter PHP
2985 SetInputFilter PHP
2986 </pre>
2988 <p> and</p>
2990 <pre>AddType application/x-httpd-php .php</pre>
2992 <p> In the case we saw, one set of directives was in
2993 <tt>/etc/httpd/conf/httpd.conf</tt>, while
2994 the other set was in <tt>/etc/httpd/conf/addon-modules/php.conf</tt>.<br />
2995 The recommended way is with <tt>AddType</tt>, so just comment out
2996 the first set of lines and restart Apache:</p>
2998 <pre>
2999 #SetOutputFilter PHP
3000 #SetInputFilter PHP
3001 </pre>
3006 <p> This problem is known to happen when the server is running Turck MMCache
3007 but upgrading MMCache to version 2.3.21 solves the problem.</p>
3012 <p>Yes.</p>
3013 <p>
3014 Since release 3.0 only PHP 5.2 and newer. For older PHP versions 2.9 branch
3015 is still maintained.
3016 </p>
3019 <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>
3021 <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>
3024 <ol><li>In your <tt>php.ini</tt> file, set <tt>cgi.rfc2616_headers = 0</tt></li>
3025 <li>In <tt>Web Site Properties -> File/Directory Security -> Anonymous
3026 Access</tt> dialog box, check the <tt>Anonymous access</tt> checkbox and
3027 uncheck any other checkboxes (i.e. uncheck <tt>Basic authentication</tt>,
3028 <tt>Integrated Windows authentication</tt>, and <tt>Digest</tt> if it's
3029 enabled.) Click <tt>OK</tt>.</li>
3030 <li>In <tt>Custom Errors</tt>, select the range of <tt>401;1</tt> through
3031 <tt>401;5</tt> and click the <tt>Set to Default</tt> button.</li>
3032 </ol>
3041 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
3042 the order of the server paragraph in <tt>config.inc.php</tt>.
3043 Table and script parts are optional. If you want
3044 http://server/phpMyAdmin/database[/table][/script] <abbr title="Uniform Resource Locator">URL</abbr>s, you need to do
3045 some configuration. Following lines apply only for <a
3047 that you have enabled some features within global configuration. You need
3048 <code>Options FollowSymLinks</code> and <code>AllowOverride
3049 FileInfo</code> enabled for directory where phpMyAdmin is installed and
3050 you need mod_rewrite to be enabled. Then you just need to create following
3051 <code>.htaccess</code> file in root folder of phpMyAdmin installation
3052 (don't forget to change directory name inside of it):</p>
3054 <pre>
3055 RewriteEngine On
3056 RewriteBase /path_to_phpMyAdmin
3057 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&table=$2&target=$3 [R]
3058 RewriteRule ^([a-zA-Z0-9_]+)/([a-z_]+\.php)$ index.php?db=$1&target=$2 [R]
3059 RewriteRule ^([a-zA-Z0-9_]+)/([a-zA-Z0-9_]+)$ index.php?db=$1&table=$2 [R]
3060 RewriteRule ^([a-zA-Z0-9_]+)$ index.php?db=$1 [R]
3061 </pre>
3064 <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>
3066 <p> Yes. However you need to pass authentication variable to <abbr title="Common Gateway Interface">CGI</abbr> using
3067 following rewrite rule:</p>
3069 <pre>
3070 RewriteEngine On
3071 RewriteRule .* - [E=REMOTE_USER:%{HTTP:Authorization},L]
3072 </pre>
3076 </h4>
3077 <p>
3078 There can be many explanations to this and a look at your server's
3079 error log file might give a clue.
3080 </p>
3084 password encryption in cookie auth doesn't work.</a></h4>
3086 <p> If your cluster consist of different architectures, PHP code used for
3087 encryption/decryption won't work correct. This is caused by use of
3088 pack/unpack functions in code. Only solution is to use mcrypt extension
3089 which works fine in this case.</p>
3094 <p> Yes but the default configuration values of Suhosin are known to cause
3095 problems with some operations, for example editing a table with many
3096 columns and no primary key or with textual primary key.
3097 </p>
3098 <p>
3099 Suhosin configuration might lead to malfunction in some cases and it can
3100 not be fully avoided as phpMyAdmin is kind of application which needs to
3101 transfer big amounts of columns in single HTTP request, what is something
3102 what Suhosin tries to prevent. Generally all
3103 <code>suhosin.request.*</code>, <code>suhosin.post.*</code> and
3104 <code>suhosin.get.*</code> directives can have negative effect on
3105 phpMyAdmin usability. You can always find in your error logs which limit
3106 did cause dropping of variable, so you can diagnose the problem and adjust
3107 matching configuration variable.
3108 </p>
3109 <p>
3110 The default values for most Suhosin configuration options will work in most
3111 scenarios, however you might want to adjust at least following parameters:
3112 </p>
3114 <ul>
3115 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.request.max_vars">suhosin.request.max_vars</a> should be increased (eg. 2048)</li>
3116 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.post.max_vars">suhosin.post.max_vars</a> should be increased (eg. 2048)</li>
3117 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.request.max_array_index_length">suhosin.request.max_array_index_length</a> should be increased (eg. 256)</li>
3118 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.post.max_array_index_length">suhosin.post.max_array_index_length</a> should be increased (eg. 256)</li>
3119 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.request.max_totalname_length">suhosin.request.max_totalname_length</a> should be increased (eg. 8192)</li>
3120 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.post.max_totalname_length">suhosin.post.max_totalname_length</a> should be increased (eg. 8192)</li>
3121 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.get.max_value_length">suhosin.get.max_value_length</a> should be increased (eg. 1024)</li>
3122 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#suhosin.sql.bailout_on_error">suhosin.sql.bailout_on_error</a> needs to be disabled (the default)</li>
3123 <li><a href="http://www.hardened-php.net/suhosin/configuration.html#logging_configuration">suhosin.log.*</a> should not include SQL, otherwise you get big slowdown</li>
3124 </ul>
3126 <p>
3128 <tt>SuhosinDisableWarning</tt> directive</a>.
3129 </p>
3133 but then my connection is redirected back to http. What can cause this
3134 behavior?</a></h4>
3136 <p> Be sure that you have enabled <tt>SSLOptions</tt> and <tt>StdEnvVars</tt>
3137 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>
3140 <a href="#faq1_40">1.40 When accessing phpMyAdmin via an Apache reverse proxy, cookie login does not work.</a></h4>
3142 <p>To be able to use cookie auth Apache must know that it has to rewrite the set-cookie headers.<br />
3143 Example from the Apache 2.2 documentation:</p>
3144 <pre>
3145 ProxyPass /mirror/foo/ http://backend.example.com/
3146 ProxyPassReverse /mirror/foo/ http://backend.example.com/
3147 ProxyPassReverseCookieDomain backend.example.com public.example.com
3148 ProxyPassReverseCookiePath / /mirror/foo/
3149 </pre>
3151 <p>Note: if the backend url looks like http://host/~user/phpmyadmin,
3152 the tilde (~) must be url encoded as %7E in the ProxyPassReverse* lines.
3153 This is not specific to phpmyadmin, it's just the behavior of Apache.
3154 </p>
3156 <pre>
3157 ProxyPass /mirror/foo/ http://backend.example.com/~user/phpmyadmin
3158 ProxyPassReverse /mirror/foo/
3159 http://backend.example.com/%7Euser/phpmyadmin
3160 ProxyPassReverseCookiePath /%7Euser/phpmyadmin /mirror/foo
3161 </pre>
3163 <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>
3164 for more details.</p>
3168 privileges, I get an error about an unknown column.</a></h4>
3170 <p> The MySQL server's privilege tables are not up to date, you need to run
3171 the <tt>mysql_upgrade</tt> command on the server.</p>
3178 headers already sent by ..." is displayed, what's the problem?</a></h4>
3180 <p> Edit your <i>config.inc.php</i> file and ensure there is nothing
3181 (I.E. no blank lines, no spaces, no characters...) neither before the
3182 <tt><?php</tt> tag at the beginning, neither after the <tt>?></tt>
3183 tag at the end. We also got a report from a user under IIS, that used
3184 a zipped distribution kit: the file <tt>libraries/Config.class.php</tt>
3185 contained an end-of-line character (hex 0A) at the end; removing this character
3186 cleared his errors.</p>
3191 <p> Either there is an error with your PHP setup or your username/password is
3192 wrong. Try to make a small script which uses mysql_connect and see if it
3193 works. If it doesn't, it may be you haven't even compiled MySQL support
3194 into PHP.</p>
3198 connect to local MySQL server through socket '/tmp/mysql.sock'
3199 (111) ..." is displayed. What can I do?</a></h4>
3201 <p> For RedHat users, Harald Legner suggests this on the mailing list:</p>
3203 <p> On my RedHat-Box the socket of MySQL is <i>/var/lib/mysql/mysql.sock</i>.
3204 In your <i>php.ini</i> you will find a line</p>
3206 <pre>mysql.default_socket = /tmp/mysql.sock</pre>
3208 <p> change it to</p>
3210 <pre>mysql.default_socket = /var/lib/mysql/mysql.sock</pre>
3212 <p> Then restart apache and it will work.</p>
3214 <p> Here is a fix suggested by Brad Ummer:</p>
3216 <ul><li>First, you need to determine what socket is being used by MySQL.<br />
3217 To do this, telnet to your server and go to the MySQL bin directory. In
3218 this directory there should be a file named <i>mysqladmin</i>. Type
3219 <tt>./mysqladmin variables</tt>, and this should give you a bunch of
3220 info about your MySQL server, including the socket
3221 (<i>/tmp/mysql.sock</i>, for example).</li>
3222 <li>Then, you need to tell PHP to use this socket.<br /> To do this in
3223 phpMyAdmin, you need to complete the socket information in the
3224 <i>config.inc.php</i>.<br />
3225 For example:
3227 $cfg['Servers'][$i]['socket'] = '/tmp/mysql.sock';</a>
3228 <br /><br />
3230 Please also make sure that the permissions of this file allow to be readable
3231 by your webserver (i.e. '0755').</li>
3232 </ul>
3234 <p> Have also a look at the
3236 corresponding section of the MySQL documentation</a>.</p>
3240 what can I do?</a></h4>
3243 directive to <tt>FALSE</tt> in the phpMyAdmin configuration file. It helps
3244 sometime.<br />
3245 Also have a look at your PHP version number: if it contains "b" or "alpha"
3246 it means you're running a testing version of PHP. That's not a so good idea,
3247 please upgrade to a plain revision.</p>
3251 or a table, an error 404 (page not found) is displayed or, with <abbr title="HyperText Transfer Protocol">HTTP</abbr> or
3252 cookie authentication, I'm asked to log in again. What's wrong?</a></h4>
3254 <p> Check the value you set for the
3256 directive in the phpMyAdmin configuration file.</p>
3260 password: YES)"-error when trying to access a MySQL-Server on a
3261 host which is port-forwarded for my localhost.</a></h4>
3263 <p> When you are using a port on your localhost, which you redirect via
3264 port-forwarding to another host, MySQL is not resolving the localhost
3265 as expected.<br />
3266 Erik Wasser explains: The solution is: if your host is "localhost"
3267 MySQL (the command line tool <code>mysql</code> as well) always tries to use the socket
3268 connection for speeding up things. And that doesn't work in this configuration
3269 with port forwarding.<br />
3275 <p> Themes are configured with
3279 <br />
3281 should not delete the directory "original" or its underlying
3282 structure, because this is the system theme used by phpMyAdmin.
3283 "original" contains all images and styles, for backwards
3284 compatibility and for all themes that would not include images or css-files.
3285 <br /><br />
3288 is enabled, you can select your favorite theme on the main page. Your
3289 selected theme will be stored in a cookie.<br /><br /></p>
3291 <p> To create a theme:</p>
3293 <ul><li>make a new subdirectory (for example "your_theme_name") under
3295 (by default <tt>themes</tt>)</li>
3296 <li>copy the files and directories from "original" to
3297 "your_theme_name"</li>
3298 <li>edit the css-files in "your_theme_name/css"</li>
3299 <li>put your new images in "your_theme_name/img"</li>
3300 <li>edit <tt>layout.inc.php</tt> in "your_theme_name"</li>
3301 <li>edit <tt>info.inc.php</tt> in "your_theme_name" to
3302 contain your chosen theme name, that will be visible in user interface</li>
3303 <li>make a new screenshot of your theme and save it under
3304 "your_theme_name/screen.png"</li>
3305 </ul>
3307 <p> In theme directory there is file <tt>info.inc.php</tt> which contains
3308 theme verbose name, theme generation and theme version. These versions and
3309 generations are enumerated from 1 and do not have any direct dependence on
3310 phpMyAdmin version. Themes within same generation should be backwards
3311 compatible - theme with version 2 should work in phpMyAdmin requiring
3312 version 1. Themes with different generation are incompatible.</p>
3314 <p> If you do not want to use your own symbols and buttons, remove the
3315 directory "img" in "your_theme_name". phpMyAdmin will
3316 use the default icons and buttons (from the system-theme "original").
3317 </p>
3321 what can I do?</a></h4>
3323 <p> Here are a few points to check:</p>
3325 <ul><li>In <tt>config.inc.php</tt>, try to leave the
3327 directive empty. See also
3329 </li>
3330 <li>Maybe you have a broken PHP installation or you need to upgrade
3331 your Zend Optimizer. See
3333 http://bugs.php.net/bug.php?id=31134</a>.
3334 </li>
3335 <li>If you are using Hardened PHP with the ini directive <tt>varfilter.max_request_variables</tt>
3336 set to the default (200) or another low value, you could get this
3337 error if your table has a high number of columns. Adjust this setting
3338 accordingly. (Thanks to Klaus Dorninger for the hint).
3339 </li>
3340 <li>In the <tt>php.ini</tt> directive <tt>arg_separator.input</tt>, a value
3341 of ";" will cause this error. Replace it with "&;".
3342 </li>
3344 you might want to increase
3346 </li>
3347 <li>The directory specified in the <tt>php.ini</tt> directive <tt>session.save_path</tt> does not exist or is read-only.
3348 </li>
3349 </ul>
3354 <p> To be able to see a progress bar during your uploads, your server must
3357 one. Moreover, the JSON extension has to be enabled in your PHP.</p>
3358 <p> If using APC, you must set <tt>apc.rfc1867</tt> to <tt>on</tt> in your php.ini.</p>
3365 who logged out can not log in again in with the same nick.</a></h4>
3367 <p> This is related to the authentication mechanism (protocol) used by
3368 phpMyAdmin. To bypass this problem: just close all the opened
3369 browser windows and then go back to phpMyAdmin. You should be able to
3370 log in again.</p>
3374 limit error or a time limit error.</a></h4>
3376 <p> Compressed dumps are built in memory and because of this are limited to
3377 php's memory limit. For GZip/BZip2 exports this can be overcome since 2.5.4
3378 using
3380 (enabled by default). Zip exports can not be handled this way, so if you need
3381 Zip files for larger dump, you have to use another way.</p>
3385 when I rename a table or a column.</a></h4>
3387 <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>
3391 bundled with the MySQL server distribution.</a></h4>
3393 <p> The problem is that older versions of <code>mysqldump</code> created invalid comments like this:</p>
3395 <pre>
3396 -- MySQL dump 8.22
3397 --
3398 -- Host: localhost Database: database
3399 ---------------------------------------------------------
3400 -- Server version 3.23.54
3401 </pre>
3403 <p> The invalid part of the code is the horizontal line made of dashes that
3404 appears once in every dump created with mysqldump. If you want to run your
3405 dump you have to turn it into valid MySQL. This means, you have to add a
3406 whitespace after the first two dashes of the line or add a # before it:
3407 <br />
3408 <code>
3409 -- -------------------------------------------------------<br />
3410 </code>
3411 or<br />
3412 <code>
3413 #---------------------------------------------------------
3414 </code>
3415 </p>
3422 <p> Please note that you should not use the separating string multiple times
3423 without any characters between them, or at the beginning/end of your table
3424 name. If you have to, think about using another TableSeparator or disabling
3425 that feature</p>
3430 <p> In Relation view, being able to choose a table in another database,
3431 or having more than one index column in the foreign key.<br /><br/>
3432 In Query-by-example (Query), automatic generation of the query
3433 LEFT JOIN from the foreign table.<br /><br/>
3434 </p>
3438 I get series of errors like "Warning: unable to parse url". How
3439 can this be fixed?</a></h4>
3440 <p>
3441 Your table neither have a primary key nor an unique one, so we must use a
3442 long expression to identify this row. This causes problems to parse_url
3443 function. The workaround is to create a primary or unique key.
3444 <br />
3445 </p>
3449 a MIME-Transformation onto!</a></h4>
3451 <p> Due to a surrounding form-container (for multi-row delete checkboxes), no
3452 nested forms can be put inside the table where phpMyAdmin displays the results.
3453 You can, however, use any form inside of a table if keep the parent
3454 form-container with the target to tbl_row_delete.php and just put your own
3455 input-elements inside. If you use a custom submit input field, the form will
3456 submit itself to the displaying page again, where you can validate the
3457 $HTTP_POST_VARS in a transformation.
3459 For a tutorial on how to effectively use transformations, see our
3461 on the official phpMyAdmin-homepage.</p>
3465 MySQL server</a></h4>
3467 <p> When MySQL is running in ANSI-compatibility mode, there are some major
3470 http://dev.mysql.com/doc/mysql/en/ansi-mode.html</a>). Most important of all,
3471 the quote-character (") is interpreted as an identifier quote character and
3472 not as a string quote character, which makes many internal phpMyAdmin
3474 statements. There is no workaround to this behaviour. News to this item will
3475 be posted in Bug report
3476 <a href="https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408">#816858</a>
3477 </p>
3481 more that one column with the same value
3482 (for example <tt>SELECT lastname from employees where firstname like 'A%'</tt> and two "Smith" values are displayed),
3483 if I click Edit I cannot be sure that I am editing the intended row.</a></h4>
3485 <p> Please make sure that your table has a primary key, so that phpMyAdmin
3486 can use it for the Edit and Delete links.</p>
3491 <p> phpMyAdmin uses a quick method to get the row count, and this method
3492 only returns an approximate count in the case of InnoDB tables. See
3494 a way to modify those results, but
3495 this could have a serious impact on performance.</p>
3502 containing an hyphen.
3503 </a></h4>
3504 <p>
3505 The tests I have made with MySQL 5.1.49 shows that the
3506 API does not accept this syntax for the USE command.
3507 </p>
3510 <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>
3511 <p>
3512 This has been a known limitation of phpMyAdmin since the beginning and
3513 it's not likely to be solved in the future.
3514 </p>
3516 <!-- Begin: Excel import limitations -->
3527 <!-- End: Excel import limitations -->
3528 <!-- Begin: CSV import limitations -->
3531 <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>
3532 <p>
3533 There is no reliable way to differentiate tables in CSV format. For the time being, you will have to break apart CSV files containing multiple tables.
3534 </p>
3536 <!-- End: CSV import limitations -->
3537 <!-- Begin: Import type-detection limitations -->
3540 <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>
3541 <p>
3542 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
3543 you will have to edit the structure to your liking post-import.
3544 <br /><br />
3545 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
3546 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.
3547 </p>
3549 <!-- End: Import type-detection limitations -->
3551 <h3 id="faqmultiuser"><abbr title="Internet service provider">ISP</abbr>s, multi-user installations</h3>
3554 <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
3555 need to install it for each customer.
3556 </a></h4>
3557 <p>
3558 Since version 2.0.3, you can setup a central copy of phpMyAdmin for all
3559 your users. The development of this feature was kindly sponsored by
3560 NetCologne GmbH.
3561 This requires a properly setup MySQL user management and phpMyAdmin
3562 <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication. See the install section on
3564 </p>
3568 access.
3569 </a></h4>
3570 <p>
3571 This depends on your system.<br />
3572 If you're running a server which cannot be accessed by other people, it's
3573 sufficient to use the directory protection bundled with your webserver
3575 If other people have telnet access to your server, you should use
3576 phpMyAdmin's <abbr title="HyperText Transfer Protocol">HTTP</abbr> or cookie authentication features.
3577 <br /><br />
3578 Suggestions:
3579 </p>
3580 <ul>
3581 <li>
3583 </li>
3584 <li>
3585 All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
3586 is a user whose password is only known to you, and apache is the
3587 group under which Apache runs.
3588 </li>
3589 <li>
3590 You should use PHP safe mode, to protect from other users that try
3592 </li>
3593 </ul>
3598 </a></h4>
3599 <p>
3604 </p>
3607 <a href="#faq4_4">4.4 phpMyAdmin always gives "Access denied" when using <abbr title="HyperText Transfer Protocol">HTTP</abbr>
3608 authentication.
3609 </a></h4>
3613 <ul><li><a href="#cfg_Servers_controluser" class="configrule">$cfg['Servers'][$i]['controluser']</a>
3614 and/or
3616 are wrong.</li>
3618 <li>You have already setup a security mechanism for the
3619 phpMyAdmin-directory, eg. a .htaccess file. This would interfere with
3620 phpMyAdmin's authentication, so remove it.</li>
3621 </ul>
3628 and put the privileges you want. For example,
3630 would let a user create/manage his/her database(s).</p>
3635 <p> If you have existing rules from an old .htaccess file, you can take them
3638 be a major benefit here if your installation is suited to using it. Then
3639 you can just add those updated lines into the
3643 <p> If you want a pre-made sample, you can try this fragment. It stops the
3644 'root' user from logging in from any networks other than the private
3647 <pre>
3648 //block root from logging in except from the private networks
3649 $cfg['Servers'][$i]['AllowDeny']['order'] = 'deny,allow';
3650 $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
3651 'deny root from all',
3652 'allow root from localhost',
3656 );
3657 </pre>
3662 <p> This happens if you are using a <abbr title="Uniform Resource Locator">URL</abbr> to start phpMyAdmin which is
3663 different than the one set in your
3665 For example, a missing "www", or entering with an <abbr title="Internet Protocol">IP</abbr> address
3666 while a domain name is defined in the config file.</p>
3671 <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>
3677 when trying to create a table with more than 14 columns.
3678 </a></h4>
3679 <p>
3680 We could reproduce this problem only under Win98/98SE. Testing under
3681 WinNT4 or Win2K, we could easily create more than 60 columns.
3682 <br />
3683 A workaround is to create a smaller number of columns, then come back to
3684 your table properties and add the other columns.
3685 </p>
3689 <p>
3690 This is not a phpMyAdmin problem but a Xitami known bug: you'll face it
3691 with each script/website that use forms.<br />
3692 Upgrade or downgrade your Xitami server.
3693 </p>
3696 <a href="#faq5_3">5.3 I have problems dumping tables with Konqueror (phpMyAdmin 2.2.2).</a></h4>
3697 <p>
3698 With Konqueror 2.1.1: plain dumps, zip and GZip dumps work ok, except that
3699 the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps
3700 don't seem to work.<br />
3702 With Konqueror 2.2.1: plain dumps work; zip dumps are placed into
3703 the user's temporary directory, so they must be moved before closing
3704 Konqueror, or else they disappear. GZip dumps give an error message.<br />
3707 </p>
3711 Explorer never stores the cookies.
3712 </a></h4>
3713 <p>
3714 MS Internet Explorer seems to be really buggy about cookies, at least till
3715 version 6.
3716 </p>
3720 rows.
3721 </a></h4>
3722 <p>
3724 </p>
3727 <a href="#faq5_6">5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found")
3728 when trying to modify a row in a table with many columns, or with a text
3729 column
3730 </a></h4>
3731 <p>
3732 Your table neither have a primary key nor an unique one, so we must use a
3733 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
3734 those browsers, and this not happen in Netscape, for example. The
3735 workaround is to create a primary or unique key, or use another browser.
3736 <br />
3737 </p>
3741 page.
3742 </a></h4>
3743 <p>
3744 Some browsers support right-clicking into the frame you want to refresh,
3745 just do this in the right frame.<br />
3746 </p>
3750 query box.
3751 </a></h4>
3752 <p>
3753 Looks like a Mozilla bug: 0.9.6 was OK. We will keep an eye on future
3754 Mozilla versions.<br />
3755 </p>
3759 whitespace in the <abbr title="structured query language">SQL</abbr>-Query edit area: the page scrolls down.
3760 </a></h4>
3761 <p>
3762 This is a Mozilla bug (see bug #26882 at
3764 </p>
3769 </a></h4>
3770 <p>
3771 This is a known Netscape 4.75 bug: it adds some line feeds when exporting
3772 data in octet-stream mode. Since we can't detect the specific Netscape
3773 version, we cannot workaround this bug.
3774 </p>
3778 wrong.</a></h4>
3780 <p> Please ensure that you have set your browser's character set to the one of the
3781 language file you have selected on phpMyAdmin's start page.
3782 Alternatively, you can try the auto detection mode that is supported by the
3783 recent versions of the most browsers.</p>
3786 <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
3789 <p> This issue has been reported by a <abbr title="operating system">OS</abbr> X user, who adds that Chimera,
3790 Netscape and Mozilla do not have this problem.</p>
3793 <a href="#faq5_13">5.13 With Internet Explorer 5.5 or 6, and <abbr title="HyperText Transfer Protocol">HTTP</abbr> authentication type,
3794 I cannot manage two servers: I log in to the first one, then the other one,
3795 but if I switch back to the first, I have to log in on each operation.</a></h4>
3801 but nothing happens after that, only a blank screen.</a></h4>
3812 Javascript errors. Or I cannot make phpMyAdmin work under Windows.</a></h4>
3817 address and you are starting
3819 containing a domain name, or the reverse situation.</li>
3820 <li>Security settings in IE and/or Microsoft Security Center are
3821 too high, thus blocking scripts execution.</li>
3822 <li>The Windows Firewall is blocking Apache and MySQL. You must
3826 </ul>
3829 <a href="#faq5_17">5.17 With Firefox, I cannot delete rows of data or drop a database.</a></h4>
3830 <p> Many users have confirmed that the Tabbrowser Extensions plugin they
3831 installed in their Firefox is causing the problem.</p>
3835 clause is generated when I browse a table.</a></h4>
3836 <p> This happens only when both of these conditions are met: using the
3846 </a></h4>
3847 <p>
3848 Examine the <abbr title="structured query language">SQL</abbr> error with care. Often the problem is caused by
3849 specifying a wrong column-type.<br />
3850 Common errors include:
3851 </p>
3852 <ul>
3855 </ul>
3856 <p>
3857 Also, look at the syntax chapter in the MySQL manual to confirm that your
3858 syntax is correct.
3859 </p>
3863 columns and
3864 phpMyAdmin generates only one index with those two columns.
3865 </a></h4>
3866 <p>
3867 This is the way to create a multi-columns
3868 index. If you want two indexes, create the first one when creating the
3869 table, save, then display the table properties and click the Index link to
3870 create the other index.
3871 </p>
3875 <p>
3876 Since version 2.2.3, you have a checkbox for each column that can be null.
3878 column's value. Since version 2.5.5, you have to use the checkbox to get
3880 a literal NULL in the column, and not a NULL value (this works in PHP4).
3881 </p>
3886 <p> Click on a database or table name in the left frame, the properties will be
3888 the structure, the data, or both. This will generate standard <abbr title="structured query language">SQL</abbr>
3889 statements that can be used to recreate your database/table.
3890 <br /><br />
3892 transmit the resulting dump to your station. Depending on your PHP
3893 configuration, you will see options to compress the dump. See also the
3895 configuration variable.<br /><br />
3898 this document.</p>
3903 </a></h4>
3905 <p> Click on a database name in the left frame, the properties will be
3907 of tabs in the right–hand frame (or "<abbr title="structured query language">SQL</abbr>" if your phpMyAdmin
3909 the path to your dump filename, or use the Browse button. Then click Go.
3910 <br /><br />
3912 that you upgrade to take advantage of the new features.
3913 <br /><br />
3915 in this document.
3916 </p>
3921 <p> Here is an example with the tables persons, towns and countries, all
3923 table, create it as explained in the configuration section. Then create the
3924 example tables:</p>
3926 <pre>
3927 CREATE TABLE REL_countries (
3928 country_code char(1) NOT NULL default '',
3929 description varchar(10) NOT NULL default '',
3930 PRIMARY KEY (country_code)
3931 ) TYPE=MyISAM;
3933 INSERT INTO REL_countries VALUES ('C', 'Canada');
3935 CREATE TABLE REL_persons (
3936 id tinyint(4) NOT NULL auto_increment,
3937 person_name varchar(32) NOT NULL default '',
3939 country_code char(1) NOT NULL default '',
3940 PRIMARY KEY (id)
3941 ) TYPE=MyISAM;
3943 INSERT INTO REL_persons VALUES (11, 'Marc', 'S', '');
3944 INSERT INTO REL_persons VALUES (15, 'Paul', 'S', 'C');
3946 CREATE TABLE REL_towns (
3948 description varchar(30) NOT NULL default '',
3949 PRIMARY KEY (town_code)
3950 ) TYPE=MyISAM;
3952 INSERT INTO REL_towns VALUES ('S', 'Sherbrooke');
3953 INSERT INTO REL_towns VALUES ('M', 'Montréal');
3954 </pre>
3960 <li>in Links, for "country_code" choose "REL_countries->country_code"</li>
3964 </ul>
3972 <li>In the columns row, choose persons.person_name and click the
3974 <li>Do the same for towns.description and countries.descriptions in the
3977 the correct joins have been generated</li>
3979 </ul>
3983 <p>
3984 Starting from the previous example, create the pma_table_info as explained
3985 in the configuration section, then browse your persons table,
3986 and move the mouse over a town code or country code.
3987 <br /><br />
3988 See also <a href="#faq6_21"><abbr title="Frequently Asked Questions">FAQ</abbr> 6.21</a> for an additional feature that "display column"
3989 enables: drop-down list of possible values.
3990 </p>
3993 <a href="#faqpdf">6.8 How can I produce a <abbr title="Portable Document Format">PDF</abbr> schema of my database?</a></h4>
3994 <p>
3997 <br /><br />
3998 Then you need to think about your schema layout. Which tables will go on
3999 which pages?
4000 </p>
4001 <ul>
4007 page and click Go. If you like, you
4009 linked tables onto the new page.</li>
4010 <li>Select the name of the new page (making sure the Edit radio button
4011 is selected) and click Go.</li>
4013 Coordinates are relative; your diagram will
4014 be automatically scaled to fit the page. When initially placing tables
4015 on the page, just pick any coordinates -- say, 50x50. After clicking
4017 position the element correctly.</li>
4019 first be sure to click the Save
4020 button beneath the list of tables and coordinates, to save any changes
4021 you made there. Then scroll all the way down, select the
4023 you want, and click Go.</li>
4024 <li>Internet Explorer for Windows may suggest an incorrect filename when
4029 browsers on Windows, do not have this problem.</li>
4030 </ul>
4034 columns!</a></h4>
4036 <p> No, it's MySQL that is doing
4042 underscores in the database name?</a></h4>
4044 <p> If you do not put a backslash before the underscore, this is a wildcard
4047 john2db ...<br /><br />
4049 If you put a backslash before the underscore, it means that the database
4050 name will have a real underscore.</p>
4054 statistics pages?</a></h4>
4065 if it already exists during the import. It does NOT drop the table after
4066 your export, it only affects the import file.</li>
4068 Otherwise, you may get an error if the table name exists but has a
4069 different structure.</li>
4071 (if any) will be included in backup.</li>
4073 column and table names formed with special characters are protected.</li>
4075 types set in the pmadb in the dump as
4077 </li>
4078 </ul>
4083 command, for better documentation (but resulting file is bigger).</li>
4085 once the INSERT verb and the table name.</li>
4088 </li>
4090 more info is provided in the
4092 but basically with this selected, invalid values are adjusted and
4093 inserted rather than causing the entire statement to fail.</li>
4094 </ul>
4098 in its name.</a></h4>
4101 is the normal way to reference a database and table name. Worse, MySQL
4102 will usually let you create a database with a dot, but then you cannot
4103 work with it, nor delete it.</p>
4109 <p>
4110 To use SQL Validator, you need PHP with
4116 module.
4117 </p>
4119 <p>
4125 usage.
4126 </p>
4128 <p>
4129 If you use the Validator, you should be aware that any
4131 submit will be stored anonymously (database/table/column names,
4132 strings, numbers replaced with generic values). The Mimer
4135 We utilize it as free SOAP service.
4136 </p>
4140 it, but MySQL says "BLOB column '...' used in key specification without
4143 <p> The right way to do this, is to create the column without any indexes,
4145 dialog. On this page, you will be able to choose your BLOB column, and
4146 set a size to the index, which is the condition to create an index on
4147 a BLOB column.</p>
4151 editing fields?</a></h4>
4153 <p> You can use Ctrl+arrows (Option+Arrows in Safari) for moving on most pages
4154 with many editing fields (table structure changes, row editing, etc.).
4155 You can also have a look at the directive
4157 ('vertical') and see if this eases up editing for you.</p>
4161 WTF is this feature then useful for?</a></h4>
4163 <p> Slow down :). Defining mimetypes is of no use, if you can't put transformations
4164 on them. Otherwise you could just put a comment on the column. Because entering
4165 your own mimetype will cause serious syntax checking issues and validation,
4166 this introduces a high-risk false-user-input situation. Instead you have to
4167 initialize mimetypes using functions or empty mimetype definitions.<br />
4168 Plus, you have a whole overview of available mimetypes. Who knows all those
4169 mimetypes by heart so he/she can enter it at will?</p>
4173 can't I see any bookmarks below the query box? What is this variable for?
4174 </a></h4>
4176 <p> Any query you have executed can be stored as a bookmark on the page where the
4177 results are displayed. You will find a button labeled 'Bookmark this query'
4178 just at the end of the page.<br />
4179 As soon as you have stored a bookmark, it is related to the database you run
4180 the query on. You can now access a bookmark dropdown on each page, the query
4181 box appears on for that database.<br /><br />
4183 Since phpMyAdmin 2.5.0 you are also able to store variables for the bookmarks.
4187 aware of that you HAVE to create a valid query, otherwise your query won't be
4188 even able to be stored in the database.<br />
4190 for your query will remain the way it is, but will be stripped of the /**/
4191 chars. So you can use:<br /><br />
4195 which will be expanded to<br /><br />
4199 in your query, where VARIABLE is the string you entered in the input box. If
4200 an empty string is provided, no replacements are made.<br /><br />
4202 A more complex example. Say you have stored this query:<br /><br />
4204 <br /><br />
4207 the full query will be:<br /><br />
4210 <br /><br />
4212 You can use multiple occurrences of <b>/*[VARIABLE]*/</b> in a single query (that is, multiple occurrences of the <i>same</i> variable).<br />
4214 spaces inserted there
4215 will be later also inserted as spaces in your query and may lead to unexpected
4216 results especially when
4218 Your initial query which is going to be stored as a bookmark has to yield at
4219 least one result row so
4220 you can store the bookmark. You may have that to work around using well
4224 <a href="#faq6_19">6.19 How can I create simple L<sup>A</sup>T<sub><big>E</big></sub>X document to
4225 include exported table?</a></h4>
4227 <p> You can simply include table in your L<sup>A</sup>T<sub><big>E</big></sub>X documents, minimal sample
4228 document should look like following one (assuming you have table
4231 <pre>
4232 \documentclass{article} % or any class you want
4233 \usepackage{longtable} % for displaying table
4234 \begin{document} % start of document
4235 \include{table} % including exported table
4236 \end{document} % end of document
4237 </pre>
4241 access them.
4242 </a></h4>
4244 <p> You have one of these global privileges: CREATE
4245 TEMPORARY TABLES, SHOW DATABASES, LOCK TABLES. Those privileges also
4246 enable users to see all the database names.
4249 So if your users do not need those privileges, you can remove them and their
4250 databases list will shorten.</p>
4254 possible values for a column, based on some foreign table?</a></h4>
4256 <p> You have to setup appropriate links between the tables, and also
4260 foreign table, a drop-down list of values will be available.
4261 You will see two lists of values, the first list containing the key
4262 and the display column, the second list containing the display column
4263 and the key. The reason for this is to be able to type the first
4264 letter of either the key or the display column.<br /><br />
4266 For 100 values or more, a distinct window will appear, to browse foreign
4267 key values and choose one. To change the default limit of 100, see
4268 <tt><a href="#cfg_ForeignKeyMaxLimit" class="configrule">$cfg['ForeignKeyMaxLimit']</a></tt>.</p>
4272 automatically when entering Browse mode for a table?</a></h4>
4274 <p> Yes. If a bookmark has the same label as a table name, it will be executed.
4275 </p>
4280 <p> You can use
4282 which works out of the box.<br />
4283 Since phpMyAdmin 3.4.5 support for direct export to Microsoft Excel
4284 version 97 and newer was dropped.
4285 </p>
4289 what happens to my column comments stored in pmadb?</a></h4>
4291 <p> Automatic migration of a table's pmadb-style column comments to the native
4292 ones is done whenever you enter Structure page for this table.</p>
4297 <p> For general information about BLOB streaming on MySQL, visit <a href="http://blobstreaming.org">blobstreaming.org</a>. You need the following components:</p>
4298 <ul>
4301 later)</li>
4304 </ul>
4308 <ol>
4309 <li>In <tt>config.inc.php</tt> your host should be defined with a FQDN (fully qualified domain name) instead of "localhost".</li>
4310 <li>Ensure that your target table is under the <tt>PBXT</tt> storage engine and has a <tt>LONGBLOB</tt> column (which must be nullable if you want to remove the BLOB reference from it).</li>
4311 <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 LONGBLOB column instead of the repository.</li>
4312 <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.</li>
4313 </ol>
4318 <p> Click the first row of the range, hold the shift key and click the last row of the range. This works everywhere you see rows, for example in Browse mode or on the Structure page.</p>
4324 <p>
4325 In all places where phpMyAdmin accepts format strings, you can use
4328 expanded variables depend on a context (for example, if you haven't chosen a
4329 table, you can not get the table name), but the following variables can be used:
4330 </p>
4331 <dl>
4337 <dd>Verbose MySQL server name as defined in <a href="#cfg_Servers_verbose">server configuration</a></dd>
4348 </dl>
4353 <p>
4354 By clicking on the button 'toggle scratchboard' on the page
4355 where you edit x/y coordinates of those elements you can activate a
4356 scratchboard where all your elements are placed. By clicking on an
4357 element, you can move them around in the pre-defined area and the x/y
4358 coordinates will get updated dynamically. Likewise, when entering a
4359 new position directly into the input field, the new position in the
4360 scratchboard changes after your cursor leaves the input field.
4361 </p>
4362 <p>
4363 You have to click on the 'OK'-button below the tables to save the new
4364 positions. If you want to place a new element, first add it to the
4365 table of elements and then you can drag the new element around.
4366 </p>
4367 <p>
4368 By changing the paper size and the orientation you can change the size
4369 of the scratchboard as well. You can do so by just changing the
4370 dropdown field below, and the scratchboard will resize automatically,
4371 without interfering with the current placement of the elements.
4372 </p>
4373 <p>
4374 If ever an element gets out of range you can either enlarge the paper
4375 size or click on the 'reset' button to place all elements below each
4376 other.
4377 </p>
4382 <p> Not every table can be put to the chart. Only tables with one, two or three columns can be visualised as a chart. Moreover the table must be in a special format for chart script to understand it. Currently supported formats can be found in the <a href="http://wiki.phpmyadmin.net/pma/Charts#Data_formats_for_query_results_chart">wiki</a>.</p>
4387 <p>
4388 An ESRI Shapefile is actually a set of several files, where .shp file contains
4389 geometry data and .dbf file contains data related to those geometry data.
4390 To read data from .dbf file you need to have PHP compiled with the dBase extension
4391 (--enable-dbase). Otherwise only geometry data will be imported.
4392 </p>
4395 <ul>
4396 <li>
4397 <p>
4398 Configure upload directory with
4400 .shp and .dbf files with the same filename and chose the .shp file from the import page.
4401 </p>
4402 </li>
4403 <li>
4404 <p>
4405 Create a Zip archive with .shp and .dbf files and import it. For this to work,
4408 </p>
4411 <pre>
4412 cd phpMyAdmin
4413 mkdir tmp
4414 chmod o+rwx tmp
4415 </pre>
4416 </li>
4417 </ul>
4425 <p>The display column is shown in pink. To set/unset a column as the display column, click the "Choose column to display" icon, then click on the appropriate column name.</p>
4430 <p> The Zoom search feature is an alternative to table search feature. It allows you to explore
4431 a table by representing its data in a scatter plot. You can locate this feature by selecting
4432 a table and clicking the 'Search' tab. One of the sub-tabs in the 'Table Search' page is
4433 'Zoom Search'. <br/><br/>
4437 for example, id and town_code. The id values will be represented on one axis and town_code
4438 values on the other axis. Each row will be represented as a point in a scatter plot based
4439 on its id and town_code. You can include two additional search criteria apart from the two
4440 fields to display.<br/><br/>
4442 You can choose which field should be displayed as label for each point. If a display
4445 You can also select the maximum number of rows you want to be displayed in the plot by
4446 specifing it in the 'Max rows to plot' field. Once you have decided over your criteria,
4447 click 'Go' to display the plot.<br/><br/>
4449 After the plot is generated, you can use the mousewheel to zoom in and out of the plot.
4450 In addition, panning feature is enabled to navigate through the plot. You can zoom-in to
4451 a certail level of detail and use panning to locate your area of interest. Clicking on a
4452 point opens a dialogue box, displaying field values of the data row represented by the point.
4453 You can edit the values if required and click on submit to issue an update query. Basic
4454 instructions on how to use can be viewed by clicking the 'How to use?' link located just above
4455 the plot.</p>
4462 <p> Our Bug Tracker is located at
4464 under the Bugs section.<br /><br />
4466 But please first discuss your bug with other users:<br />
4468 https://sourceforge.net/projects/phpmyadmin/forums</a>.
4469 </p>
4473 existing language, where do I start?</a></h4>
4475 <p> Always use latest Git version of the po file to translate. You can optionally
4477 server</a> where you can also get the latest po files and merge them
4478 with your translations. For creating a new translation simply use
4482 to do this) or ask on the mailing list to add the translation to the web
4483 interface. More details are available on <a href="http://wiki.phpmyadmin.net/pma/Gettext_for_translators">our wiki</a>.
4484 </p>
4485 <p>
4486 Please note that we try not to use HTML entities like &eacute; in
4487 the translations, since we define the right character set in the file.
4488 With HTML entities, the text on JavaScript messages would not
4489 display correctly.
4490 However there are some entities that need to be there: quotes,
4491 non-breakable spaces, ampersands, less than, greater than.
4492 </p>
4493 <p>
4494 You can then put your translations, as a zip file to avoid losing special
4495 characters, on the sourceforge.net <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker.</a>
4496 </p>
4497 <p>
4498 It would be a good idea to subscribe to the <a href="https://lists.sourceforge.net/lists/listinfo/phpmyadmin-translators">phpmyadmin-translators</a> mailing
4499 list, because this is where we ask for translations of new messages.
4500 </p>
4502 <p>
4503 Documentation is being translated using po4a and gettext (see
4505 for existing translations). To start, checkout
4506 <a href="http://phpmyadmin.git.sourceforge.net/git/gitweb.cgi?p=phpmyadmin/localized_docs;a=tree;f=po"><code>localized_docs/po</code></a>
4507 from Git, or just go to the <a href="https://l10n.cihar.com/projects/pmadoc/">translation server</a>
4508 and translate it online. If your language is missing, just contact
4510 you prefer to directly translate the po files, please put updated ones into our
4511 <a href="https://sourceforge.net/tracker/?group_id=23067&atid=387645">translation tracker</a>.
4512 </p>
4516 phpMyAdmin. How should I proceed?</a></h4>
4521 <tt>git clone
4522 git://phpmyadmin.git.sourceforge.net/gitroot/phpmyadmin/phpmyadmin</tt><br />
4523 </li>
4525 <li>generate patch with your changes:
4527 </li>
4530 tracker of the phpMyAdmin project</a>.
4531 </li>
4532 </ol>
4534 <p>More details on git are available on <a href="http://wiki.phpmyadmin.net/pma/Git">our wiki</a>.</p>
4536 <p> Write access to the repository is granted only to experienced developers who
4537 have already contributed something useful to phpMyAdmin.<br />
4543 <a href="#faq8_1">8.1 Where can I get information about the security alerts issued for phpMyAdmin?</a></h4>
4545 <p> Please refer to
4546 <a href="http://www.phpmyadmin.net/home_page/security.php">http://www.phpmyadmin.net/home_page/security.php</a>
4547 </p>
4552 <p> If you use Apache web server, phpMyAdmin exports information about
4553 authentication to the Apache environment and it can be used in Apache logs.
4554 Currently there are two variables available:
4555 </p>
4556 <dl>
4558 <dd>User name of currently active user (he does not have to be logged
4559 in).</dd>
4566 </dl>
4567 <p>
4569 </p>
4570 <pre>
4573 </pre>
4574 <p>
4575 You can then use any log analyzing tools to detect possible break-in
4576 attempts.
4577 </p>
4583 <p> You can now synchronize databases/tables in phpMyAdmin using the Synchronize feature.
4584 It allows you to connect to local as well as remote servers. This requires you to enter
4585 server host name, username, password, port and the name of the database. Therefore you can
4586 now synchronize your databases placed on the same server or some remote server.
4587 </p>
4589 <p>
4590 This feature is helpful for developers who need to replicate their
4591 database’s structure as well as data. Moreover, this feature not only
4592 helps replication but also facilitates the user to keep his/her database
4593 in sync with another database. Other than the full database, certain
4594 tables of the databases can also be synchronized.
4595 </p>
4597 <p>
4598 You need to fill in the host name of the server, the username and
4599 password of an user account already there in MySQL. Port is by default
4600 populated with 3306 (MySQL default port). Then the name of the database
4601 should be mentioned at the end. All the information other than the port
4602 needs to be filled explicitly for the source as well as target servers.
4603 </p>
4605 <p>
4606 After successfully passing through the authentication phase, the source and
4607 target database table names will be displayed. It will be a tabular
4608 representation.
4609 </p>
4611 <p>
4612 On the left, are listed the source database table names. Some of the
4614 are only present in source database and they need to be added to the
4615 target database in order to synchronize the target database. The tables
4617 target database.
4618 </p>
4620 <p>
4621 On the right, are listed the target database table names. There are few
4623 means that these tables are to be created in target database in order to
4624 synchronize target database with source database. Some table names
4626 only present in target database and they will remain unchanged in the
4627 target database. The column in the middle shows the difference between
4628 the source and target corresponding tables.
4629 </p>
4631 <p>
4633 letters, indicating that either Structure or Data are not up to date. By
4634 clicking on them, they will turn grey, what means that they will be synchronized.
4635 </p>
4637 <!-- DEVELOPERS -->
4640 <p> phpMyAdmin is Open Source, so you're invited to contribute to it. Many
4641 great features have been written by other people and you too can help to
4642 make phpMyAdmin a useful tool.</p>
4644 <p> If you're planning to contribute source, please read the following
4645 information:</p>
4651 it free from other code.<br />
4652 Commonly used functions should be added to
4655 <li>Obviously, you're free to use whatever coding style you want. But
4656 please try to keep your code as simple as possible: beginners are
4657 using phpMyAdmin as an example application.<br />
4658 As far as possible, we want the scripts to be XHTML1.0 and CSS2
4659 compliant on one hand, they fit the
4662 coding standards</a>
4663 on the other hand. Please pay attention to this.</li>
4664 <li>Please enable showing PHP errors and warnings by the
4666 configuration directive.</li>
4667 <li>Please try to keep up the file-naming conventions. Table-related stuff
4670 <li>Please use gettext wrappers around all messages
4673 script. To use translated messages, call
4675 Gettext.</li>
4679 Debugger DBG</a>) is now supported by phpMyAdmin for developers to
4680 better debug and profile their code.<br />
4681 Please see the
4683 options for more information.<br />
4684 This is in memoriam of the Space Shuttle Columbia (STS-107) which was
4685 lost during its re-entry into Earth's atmosphere and in memory of the
4686 brave men and women who gave their lives for the people of Earth.</li>
4687 </ul>
4691 <pre>
4702 </pre>
4704 <p>
4705 This program is free software; you can redistribute it and/or modify
4706 it under the terms of the GNU General Public License version 2,
4707 as published by the Free Software Foundation.
4708 </p>
4710 <p>
4711 This program is distributed in the hope that it will be useful,
4712 but WITHOUT ANY WARRANTY; without even the implied warranty of
4713 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
4714 GNU General Public License for more details.
4715 </p>
4717 <p>
4718 You should have received a copy of the GNU General Public License
4719 along with this program; if not, write to the Free Software
4721 </p>
4723 <!-- CREDITS -->
4728 <ul>
4731 <ul>
4734 </ul></li>
4737 <ul>
4742 </ul></li>
4745 <ul>
4751 </ul></li>
4754 <ul>
4756 <li>rewrote the scripts so they fit the <abbr title="PHP Extension and Application Repository">PEAR</abbr> coding standards and
4757 generate XHTML1.0 and CSS2 compliant codes</li>
4760 </ul></li>
4763 <ul>
4771 </ul></li>
4774 <ul>
4779 </ul></li>
4782 <ul>
4785 </ul></li>
4788 <ul>
4790 </ul></li>
4793 <ul>
4796 </ul></li>
4799 <ul>
4803 </ul></li>
4806 <ul>
4809 </ul></li>
4812 <ul>
4819 </ul></li>
4822 <ul>
4826 </ul></li>
4829 <ul>
4835 </ul></li>
4838 (http://sf.net/projects/phpmysqlformgen/)
4839 <ul>
4841 </ul></li>
4844 <ul>
4846 <li>built the Javascript based Query window + <abbr title="structured query language">SQL</abbr> history</li>
4851 <li><abbr title="Portable Document Format">PDF</abbr>-scratchboard for WYSIWYG-distribution of <abbr title="Portable Document Format">PDF</abbr> relations</li>
4855 </ul></li>
4858 <ul>
4860 </ul></li>
4863 <ul>
4865 </ul></li>
4868 <ul>
4870 </ul></li>
4873 <ul>
4874 <li><abbr title="Portable Document Format">PDF</abbr> schema output, thanks also to Olivier Plathey for the
4875 "FPDF" library (see <a href="http://www.fpdf.org/">http://www.fpdf.org/</a>) and Steven Wittens
4876 for the "UFPDF" library (see <a href="http://www.acko.net/node/56">http://www.acko.net/node/56</a>).</li>
4877 </ul></li>
4880 <ul>
4882 </ul></li>
4885 <ul>
4887 </ul></li>
4890 <ul>
4892 </ul></li>
4895 <ul>
4898 </ul></li>
4900 <li>Nicola Asuni (Tecnick.com)
4901 <ul>
4904 </ul></li>
4907 <ul>
4910 </ul></li>
4913 <ul>
4915 </ul></li>
4918 <ul>
4921 </ul></li>
4923 <li>Ivan A Kirillov
4924 <ul>
4926 </ul></li>
4929 <ul>
4931 </ul></li>
4934 <ul>
4938 </ul></li>
4941 <ul>
4943 </ul></li>
4946 <ul>
4948 </ul></li>
4951 <ul>
4953 </ul></li>
4956 <ul>
4958 </ul></li>
4961 <ul>
4963 </ul></li>
4966 <ul>
4970 </ul></li>
4973 <ul>
4975 </ul></li>
4978 <ul>
4980 </ul></li>
4982 <li>Barrie Leslie
4983 <ul>
4985 </ul></li>
4988 <ul>
4990 </ul></li>
4993 </ul>
4995 <p>
4996 And also to the following people who have contributed minor changes,
4997 enhancements, bugfixes or support for a new language since version 2.1.0:
4998 </p>
5000 <p>
5001 Bora Alioglu, Ricardo ?, Sven-Erik Andersen, Alessandro Astarita,
5002 Péter Bakondy, Borges Botelho, Olivier Bussier, Neil Darlow,
5003 Mats Engstrom, Ian Davidson, Laurent Dhima, Kristof Hamann, Thomas Kläger,
5004 Lubos Klokner, Martin Marconcini, Girish Nair, David Nordenberg, Andreas Pauley,
5006 www.securereality.com.au, Alexis Soulard, Alvar Soome, Siu Sun, Peter Svec,
5007 Michael Tacelosky, Rachim Tamsjadi, Kositer Uros,
5008 Luís V., Martijn W. van der Lee,
5009 Algis Vainauskas, Daniel Villanueva, Vinay, Ignacio Vazquez-Abrams, Chee Wai,
5011 </p>
5016 <p>
5017 This work is based on Peter Kuppelwieser's MySQL-Webadmin. It was his idea
5018 to create a web-based interface to MySQL using PHP3. Although I have not
5019 used any of his source-code, there are some concepts I've borrowed from
5020 him. phpMyAdmin was created because Peter told me he wasn't going to
5021 further develop his (great) tool.
5022 </p>
5023 <p>
5024 Thanks go to
5025 </p>
5026 <ul>
5028 code for the check when dropping a table or database. He also suggested
5029 that you should be able to specify the primary key on tbl_create.php3. To
5030 version 1.1.1 he contributed the ldi_*.php3-set (Import text-files) as
5031 well as a bug-report. Plus many smaller improvements.
5032 </li>
5034 were introduced in 1.3.0 (including quite significant ones like the
5035 authentication). For 1.4.1 he enhanced the table-dump feature. Plus
5036 bug-fixes and help.
5037 </li>
5039 language-independent by outsourcing the strings to a separate file. He
5040 also contributed the French translation.
5041 </li>
5043 tbl_select.php3, a feature to display only some columns from a table.
5044 </li>
5046 functions in tbl_change.php3. He also added the
5048 </li>
5050 servers and is a regular contributor for bug-fixes.
5051 </li>
5053 features for 2.0.6.
5054 </li>
5055 </ul>
5056 <p>
5057 The following people have contributed minor changes, enhancements, bugfixes
5058 or support for a new language:
5059 </p>
5060 <p>
5061 Jim Kraai, Jordi Bruguera, Miquel Obrador, Geert Lund, Thomas Kleemann,
5062 Alexander Leidinger, Kiko Albiol, Daniel C. Chao, Pavel Piankov,
5063 Sascha Kettler, Joe Pruett, Renato Lins, Mark Kronsbein, Jannis Hermanns,
5064 G. Wieggers.
5065 </p>
5066 <p>
5067 And thanks to everyone else who sent me email with suggestions, bug-reports
5068 and or just some feedback.
5069 </p>
5075 <ul>
5077 - the default name of Apache's directory-level configuration file.</li>
5081 - a software application that enables a user to display and interact with
5082 text, images, and other information typically located on a web page at a
5083 website on the World Wide Web.</li>
5085 - a free software/open source data compression algorithm and program
5086 developed by Julian Seward.</li>
5088 - an important World Wide Web technology that enables a client web browser
5089 to request data from a program executed on the Web server.</li>
5091 - a log or record of changes made to a project.</li>
5093 - a computer system that accesses a (remote) service on another computer
5094 by some kind of network.</li>
5096 - a set of data values of a particular simple type, one for each row of
5097 the table.</li>
5099 - a packet of information sent by a server to a World Wide Web browser
5100 and then sent back by the browser each time it accesses that server.</li>
5102 - Comma-separated values</li>
5105 - an organized collection of data.</li>
5108 - a PHP module that extends PHP with additional functionality.</li>
5110 - a list of commonly asked question and there answers.</li>
5112 - one part of divided data/columns.</li>
5114 - a column or group of columns in a database row that point to a key
5115 column or group of columns forming a key of another database row in some
5116 (usually different) table.</li>
5118 - the free PDF library</li>
5120 GD Graphics Library</a> - a library by Thomas Boutell and others for
5121 dynamically manipulating images.</li>
5124 - gzip is short for GNU zip, a GNU free software file compression
5125 program.</li>
5127 - any machine connected to a computer network, a node that has a hostname.</li>
5129 - the unique name by which a network attached device is known on a network.</li>
5131 (HyperText Transfer Protocol)</a>
5132 - the primary method used to transfer or convey information on the World
5133 Wide Web.</li>
5136 additional security measures.</li>
5137 <li><a href="http://www.wikipedia.org/wiki/Internet_Information_Services">IIS (Internet Information Services)</a>
5138 - a set of Internet-based services for servers using Microsoft Windows.</li>
5140 - a feature that allows quick access to the rows in a table.</li>
5142 - a data-oriented protocol used by source and destination hosts for
5143 communicating data across a packet-switched internetwork.</li>
5145 - a unique number that devices use in order to identify and communicate
5146 with each other on a network utilizing the Internet Protocol standard.</li>
5148 (Internet Server Application Programming Interface)</a>
5149 - the API of Internet Information Services (IIS).</li>
5151 - a business or organization that offers users access to the Internet and related services.</li>
5153 - a most commonly used standard method of lossy compression for
5154 photographic images.</li>
5160 - line of personal computers is designed, developed, manufactured, and
5161 marketed by Apple Computer.</li>
5162 <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>
5163 - the operating system which is included with all currently shipping Apple
5164 Macintosh computers in the consumer and professional markets.</li>
5166 - a cryptographic library.</li>
5168 - the MCrypt PHP extension.</li>
5169 <li><a href="http://www.wikipedia.org/wiki/MIME">MIME (Multipurpose Internet Mail Extensions)</a>
5170 - an Internet Standard for the format of e-mail.</li>
5172 - some sort of extension for the Apache Webserver.</li>
5174 - a multithreaded, multi-user, SQL (Structured Query Language) Database
5175 Management System (DBMS).</li>
5177 - the improved MySQL client PHP extension.</li>
5179 - the MySQL client PHP extension.</li>
5181 - open standard for office documents.</li>
5182 <li><a href="http://www.wikipedia.org/wiki/OS_X"><abbr title="operating system">OS</abbr> X</a>
5183 - look at <a href="#glossar_mac_os_x"><acronym title="Apple Macintosh">Mac</acronym> <abbr title="operating system">OS</abbr> X</a>.</li>
5185 (Portable Document Format)</a>
5186 - a file format developed by Adobe Systems for representing two
5187 dimensional documents in a device independent and resolution independent
5188 format.</li>
5190 - the PHP Extension and Application Repository.</li>
5192 - the perl-compatible regular expression functions for PHP</li>
5194 - short for "PHP: Hypertext Preprocessor", is an open-source, reflective
5195 programming language used mainly for developing server-side applications
5196 and dynamic web content, and more recently, a broader range of software
5197 applications.</li>
5199 - a connection through which data is sent and received.</li>
5201 - Request for Comments (RFC) documents are a series of memoranda
5202 encompassing new research, innovations, and methodologies applicable to
5203 Internet technologies.</li>
5207 - represents a single, implicitly structured data item in a table.</li>
5209 - a computer system that provides services to other computing
5210 systems over a network.</li>
5211 <li><a id="glossar_storage_engine" href="http://dev.mysql.com/doc/en/storage-engines.html">Storage Engines</a>
5212 - handlers for different table types</li>
5214 - a form of inter-process communication.</li>
5216 Sockets Layer)</a>
5217 - a cryptographic protocol which provides secure communication on the Internet.</li>
5219 - a subroutine available to applications accessing a relational database system</li>
5221 - Structured Query Language</li>
5223 - a set of data elements (cells) that is organized, defined and stored as
5224 horizontal rows and vertical columns where each item can be uniquely
5225 identified by a label or key or by it?s position in relation to other items.</li>
5228 - a type of archive file format: the Tape ARchive format.</li>
5230 - one of the core protocols of the Internet protocol suite.</li>
5232 - a procedural code that is automatically executed in response to
5233 certain events on a particular table or view in a database</li>
5237 - a sequence of characters, conforming to a standardized format, that is
5238 used for referring to resources, such as documents and images on the
5239 Internet, by their location.</li>
5241 - A computer (program) that is responsible for accepting HTTP requests
5242 from clients and serving them Web pages.</li>
5244 - a W3C-recommended general-purpose markup language for creating
5245 special-purpose markup languages, capable of describing many different
5246 kinds of data.</li>
5248 - a popular data compression and archival format.</li>
5250 - an open-source, cross-platform data compression library by Jean-loup
5251 Gailly and Mark Adler.</li>
5252 </ul>
5253 </div>
5256 <li>Copyright © 2003 - 2010 <a href="http://www.phpmyadmin.net/home_page/team.php">phpMyAdmin devel team</a></li>
5259 <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>
5260 </ul>
5262 </body>
5263 </html>