diff --git a/ANNOUNCE.txt b/ANNOUNCE.txt
index c54c05f07..87a15d593 100644
--- a/ANNOUNCE.txt
+++ b/ANNOUNCE.txt
@@ -154,19 +154,27 @@ Known bugs
Description
-----------
-phpMyAdmin is intended to handle the administration of MySQL over the WWW.
+ phpMyAdmin is intended to handle the administration of MySQL over the WWW. It
+ can manage a whole MySQL server as well as a single database.
+
Currently it can:
- create and drop databases
- - create, copy, drop and alter tables
+ - create, copy, drop, rename and alter tables
+ - do table maintenance
- delete, edit and add fields
- execute any SQL-statement, even batch-queries
- manage keys on fields
- load text files into tables
- create and read dumps of tables
- - export and import CSV data
- - support single- and multi-user configuration
- - add, delete and edit MySQL users
- - communicate in more than 42 different languages
+ - export data to CSV, XML and Latex formats
+ - administer multiple servers
+ - manage MySQL users and privileges
+ - check referential integrity
+ - using Query-by-example (QBE), create complex queries automatically
+ connecting required tables
+ - create PDF graphics of your Database layout
+ - search globally in a database or a subset of it
+ - communicate in 42 different languages
Author & Copyright
diff --git a/ChangeLog b/ChangeLog
index 680c924ea..89ac0f0a5 100755
--- a/ChangeLog
+++ b/ChangeLog
@@ -10,6 +10,10 @@ $Source$
2003-02-17 Alexander M. Turek
- phpMyAdmin can manage a whole MySQL-server (needs a super-user)
- but also a single database. To accomplish the latter you'll need
- a properly set up MySQL-user who can read/write only the desired
- database. It's up to you to look up the appropriate part in the
- MySQL manual. Currently phpMyAdmin can:
+ phpMyAdmin can manage a whole MySQL server (needs a super-user) as well as
+ a single database. To accomplish the latter you'll need a properly set up
+ MySQL user who can read/write only the desired database. It's up to you to
+ look up the appropriate part in the MySQL manual.Introduction
+ Currently phpMyAdmin can:
@@ -103,13 +103,14 @@
@@ -129,7 +130,7 @@
NOTE: phpMyAdmin does not apply any special security
methods to the MySQL database server. It is still the sysadmin's job to
grant permissions on the MySQL databases properly. phpMyAdmin's
- "Users" page can be used for this.
+ "Privileges" page can be used for this.
@@ -152,7 +153,7 @@ extension (.php3 or .php) depending on the way your web/PHP server interprets those extensions.
There are some known php bugs with output buffering and compression.
@@ -1488,7 +1489,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
You should first try the latest versions of Apache (and possibly MySQL). @@ -1502,7 +1503,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This is a known PHP bug (see this @@ -1514,7 +1515,8 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
You just forgot to read the install.txt file from the php distribution. Have a look at the last message in this @@ -1524,7 +1526,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This is a known problem with the php ISAPI filter: it's not so stable. For @@ -1546,8 +1548,8 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
These features are based on the gzencode() and @@ -1562,7 +1564,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Your uploaded file is saved by PHP in the "upload dir", as @@ -1585,7 +1587,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
It's not really phpMyAdmin related but RedHat 7.0. You have a RedHat 7.0 @@ -1609,7 +1611,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
As suggested by "Rob M" in the phpWizard forum, add this line to @@ -1620,7 +1622,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Since version 2.2.4, phpMyAdmin supports servers with open_basedir @@ -1632,7 +1634,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
The MySql manual explains how to @@ -1641,8 +1643,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
If PHP does not have read/write access to its upload_tmp_dir, it @@ -1651,7 +1652,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Check the post_max_size directive from your php configuration file @@ -1659,7 +1660,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
In older MySQL versions, the User and Password fields @@ -1667,7 +1668,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://' names to align with current standards.
The first things to check (or ask your host provider to check) are the @@ -1680,7 +1681,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Because of a major change in the definition syntax of string field types, @@ -1694,7 +1695,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://' lower_case_table_names set to 1. If I create a new table with a capital letter in its name it is changed to lowercase as it should. But if I try to DROP this table MySQL is unable to find the corresponding - file + file.
This is a bug of MySQL <= 4.0.1. Please upgrade to at least @@ -1704,7 +1705,8 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
The "FPDF" library we're using for this feature requires some
special files to use font faces.
@@ -1716,7 +1718,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
To connect to a MySQL server, PHP needs a set of MySQL functions called @@ -1731,7 +1733,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
In php.ini, set mysql.max_links higher than 1. @@ -1739,7 +1741,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This is most likely because in php.ini, your file_uploads @@ -1748,7 +1750,8 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This happens because the MySQL directive lower_case_table_names defaults to 1 (ON) in the Win32 version of MySQL. You can change @@ -1763,7 +1766,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This is a @@ -1772,7 +1775,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
A tip from Jose Fandos: put a comment on the following two lines @@ -1797,7 +1800,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This is a PHP bug that occur when @@ -1806,12 +1809,24 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://' in PHP 5.0.0.
++ This can happen due to a MySQL bug when having database / table names with + upper case characters although lower_case_table_names. + To fix this, turn off this directive, convert all database and table names + to lower case and turn it on again. Alternatively, there's a bugfix + available starting with MySQL 3.23.56 / 4.0.11-gamma. +
+Edit your config.inc.php or .php3 file and ensure there is nothing @@ -1821,7 +1836,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Either there is an error with your PHP setup or your username/password is @@ -1833,7 +1848,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
For RedHat users, Harald Legner suggests this on the mailing list:
@@ -1878,7 +1893,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Try to set the $cfg['OBGZip'] directive to FALSE in the @@ -1891,7 +1906,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Check the value you set for the $cfg['PmaAbsoluteUri'] directive
@@ -1904,7 +1919,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This is related to the authentication mechanism (protocol) used by @@ -1916,7 +1931,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
As of version 2.2.4, we build the compressed dump in memory, so large @@ -1928,7 +1943,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This seems to be a InnoDB bug (fixed in MySQL 3.23.50?). However, keep in @@ -1937,7 +1952,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
The problem is that mysqldump creates invalid comments like this: @@ -1970,7 +1985,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Since version 2.0.3, you can setup a central copy of phpMyAdmin for all @@ -1983,7 +1998,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This depends on your system.
@@ -2012,7 +2027,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Check php.ini, or ask your sysadmin to check it. The @@ -2022,7 +2037,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This could happen for several reasons: @@ -2043,7 +2058,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Starting with 2.2.5, in the user management page, you can enter a wildcard @@ -2053,7 +2068,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
If you have existing rules from an old .htaccess file, you can take them @@ -2085,7 +2100,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
We could reproduce this problem only under Win98/98SE. Testing under @@ -2096,7 +2111,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This is not a phpMyAdmin problem but a Xitami known bug: you'll face it @@ -2105,8 +2120,8 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
With Konqueror 2.1.1: plain dumps, zip and gzip dumps work ok, except that the proposed file name for the dump is always 'tbl_dump.php'. Bzip2 dumps @@ -2121,7 +2136,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
MS Internet Explorer seems to be really buggy about cookies, at least till @@ -2134,10 +2149,10 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
- Upgrade to at least Internet Explorer 5.5SP2.
+ Upgrade to at least Internet Explorer 5.5 SP2.
Some browsers support right-clicking into the frame you want to refresh, @@ -2163,7 +2178,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Looks like a Mozilla bug: 0.9.6 was ok. We will keep an eye on future @@ -2172,7 +2187,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This is a Mozilla bug (see bug #26882 at @@ -2181,7 +2196,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This is a known Netscape 4.75 bug: it adds some line feeds when exporting @@ -2191,7 +2206,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Please ensure that you have set your browser's charset to the one of the @@ -2202,7 +2217,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This issue has been reported by a OS X user, who adds that Chimera, @@ -2223,7 +2238,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Examine the SQL error with care. Often the problem is caused by @@ -2241,7 +2256,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
In phpMyAdmin 2.2.0 and 2.2.1, this is the way to create a multi-fields @@ -2251,7 +2266,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Since version 2.2.3, you have a checkbox for each field that can be null. @@ -2260,7 +2275,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Click on a database or table name in the left frame, the properties will be @@ -2279,7 +2294,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Click on a database name in the left frame, the properties will be @@ -2291,7 +2306,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Here is an example with the tables persons, towns and countries, all
@@ -2360,7 +2375,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Starting from the previous example, create the PMA_table_info as explained
@@ -2370,7 +2385,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
First you have to fill the "relation", "table_coords" @@ -2413,7 +2428,8 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
No, it's MySQL that is doing silent column type changing. @@ -2423,7 +2439,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This is normal and means that the grant is done only for this database. If @@ -2436,7 +2452,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
It means "average".
@@ -2444,7 +2460,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
"Complete inserts" adds the column names on every INSERT command, @@ -2456,7 +2472,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
This is a bad idea, because in MySQL the syntax "database.table"
@@ -2467,7 +2483,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
To use it, you need a very recent version of PHP, 4.3.0 recommended, with @@ -2485,7 +2501,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
The right way to do this, is to create the field without any indexes, @@ -2497,7 +2513,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
You can use Ctrl+arrows for moving on most pages with plenty editing
@@ -2549,7 +2565,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Please note that we try not to use html entities like é in
the translations, since we define the right character set in the file.
- With html entities, the text on javascript messages would not
+ With html entities, the text on javascript messages would not
display correctly.
However there are some entities that need to be there, for quotes
,non-breakable spaces, ampersands, less than, greater than.