2.3.0-rc3
This commit is contained in:
Marc Delisle
@@ -5,14 +5,15 @@ phpMyAdmin - Changelog
|
||||
$Id$
|
||||
$Source$
|
||||
|
||||
2002-07-14 Alexander M. Turek <rabus@users.sourceforge.net>
|
||||
* config.inc.php3, libraries/common.lib.php3: Fixed bug #576018.
|
||||
* lang/german-*.inc.php3: Clarification.
|
||||
|
||||
2002-07-14 Marc Delisle <lem9@users.sourceforge.net>
|
||||
* Documentation.html, db_details_exports.php3, tbl_properties_export.php3:
|
||||
add a link to a new faq entry explaining some dump options
|
||||
* libraries/relation.lib.php3: bug 575868 Unitialized string offset
|
||||
* 2.3.0-rc3 released
|
||||
|
||||
2002-07-14 Alexander M. Turek <rabus@users.sourceforge.net>
|
||||
* config.inc.php3, libraries/common.lib.php3: Fixed bug #576018.
|
||||
* lang/german-*.inc.php3: Clarification.
|
||||
|
||||
2002-07-13 Marc Delisle <lem9@users.sourceforge.net>
|
||||
* libraries/common.lib.php3: bug 580929: do not EXPLAIN if this is
|
||||
|
||||
@@ -7,8 +7,8 @@
|
||||
+ Version history: ChangeLog
|
||||
+ General notes: README
|
||||
+ License: LICENSE
|
||||
* Documentation version: $Id: Documentation.html,v 1.273 2002/06/29
|
||||
20:32:13 lem9 Exp $
|
||||
* Documentation version: $Id: Documentation.html,v 1.282 2002/07/14
|
||||
15:04:15 lem9 Exp $
|
||||
______________________________________________________________________
|
||||
|
||||
Top - Requirements - Introduction - Installation -
|
||||
@@ -46,7 +46,7 @@ Introduction
|
||||
* export (*) and import data to CSV values
|
||||
* administer multiple servers and single databases
|
||||
* check referential integrity
|
||||
* create complex Queries automatically connecting required tables
|
||||
* create complex queries automatically connecting required tables
|
||||
* create PDF graphics of your Database layout
|
||||
* communicate in more than 38 different languages
|
||||
|
||||
@@ -312,18 +312,19 @@ CRIPT_NAME'], '/')+1);
|
||||
example.
|
||||
|
||||
$cfg['Servers'][$i]['pmadb'] string
|
||||
Starting with Version 2.3.0 phpMyAdmin offers a lot of Features
|
||||
to work with Master / Foreign - Tables. To use those as well as
|
||||
Starting with version 2.3.0 phpMyAdmin offers a lot of features
|
||||
to work with master / foreign - tables. To use those as well as
|
||||
the bookmark feature you will need to create a new db.
|
||||
To use this functionality as superuser create a new database:
|
||||
|
||||
+ create a new database for phpmyadmin: CREATE database
|
||||
phpmyadmin; Note that controluser must have SELECT, INSERT
|
||||
and DELETE privileges on the bookmark table. Here is a query
|
||||
to set up those privileges (using "pma" as the controluser):
|
||||
GRANT SELECT,INSERT,DELETE ON to 'pma'@localhost; do not
|
||||
give any other user rights on this db.
|
||||
+ Enter the databasename in $cfg['Servers'][$i]['pmadb']
|
||||
+ create a new database for phpmyadmin:
|
||||
CREATE DATABASE phpmyadmin;
|
||||
Note that "controluser" must have SELECT, INSERT and DELETE
|
||||
privileges on the bookmark table. Here is a query to set up
|
||||
those privileges (using "pma" as the controluser):
|
||||
GRANT SELECT,INSERT,DELETE ON <pmadb> to 'pma'@localhost;
|
||||
do not give any other user rights on this database.
|
||||
+ enter the databasename in $cfg['Servers'][$i]['pmadb']
|
||||
|
||||
$cfg['Servers'][$i]['bookmarktable'] string
|
||||
Since release 2.2.0 phpMyAdmin allows to bookmark queries. This
|
||||
@@ -332,7 +333,7 @@ CRIPT_NAME'], '/')+1);
|
||||
|
||||
+ set up a PMA database as described above
|
||||
+ within this database create a table following this scheme:
|
||||
CREATE TABLE bookmark (
|
||||
CREATE TABLE `PMA_bookmark` (
|
||||
id int(11) DEFAULT '0' NOT NULL auto_increment,
|
||||
dbase varchar(255) NOT NULL,
|
||||
user varchar(255) NOT NULL,
|
||||
@@ -340,13 +341,14 @@ CRIPT_NAME'], '/')+1);
|
||||
query text NOT NULL,
|
||||
PRIMARY KEY (id)
|
||||
) TYPE=MyISAM COMMENT='Bookmarks';
|
||||
+ Enter the tablename in $cfg['Servers'][$i]['bookmarktable']
|
||||
+ enter the tablename in $cfg['Servers'][$i]['bookmarktable']
|
||||
|
||||
Note that controluser must have SELECT, INSERT and DELETE
|
||||
Note that "controluser" must have SELECT, INSERT and DELETE
|
||||
privileges on the bookmark table. Here is a query to set up
|
||||
those privileges (using "pma" as the controluser and phpmyadmin
|
||||
as databasename:
|
||||
GRANT SELECT,INSERT,DELETE ON <phpmyadmin> to 'pma'@localhost;
|
||||
as databasename):
|
||||
GRANT SELECT,INSERT,DELETE ON <phpmyadmin> to
|
||||
'pma'@localhost;
|
||||
|
||||
$cfg['Servers'][$i]['relation'] string
|
||||
Since release 2.2.4 you can describe, in a special 'relation'
|
||||
@@ -371,16 +373,16 @@ CRIPT_NAME'], '/')+1);
|
||||
|
||||
+ set up a PMA database as described above
|
||||
+ within this database create a table following this scheme:
|
||||
CREATE TABLE `relation` (
|
||||
CREATE TABLE `PMA_relation` (
|
||||
`master_db` varchar(64) NOT NULL default '',
|
||||
`master_table` varchar(64) NOT NULL default '',
|
||||
`master_field` varchar(64) NOT NULL default '',
|
||||
`foreign_db` varchar(64) NOT NULL default '',
|
||||
`foreign_table` varchar(64) NOT NULL default '',
|
||||
`foreign_field` varchar(64) NOT NULL default '',
|
||||
PRIMARY KEY
|
||||
(`master_db`,`master_table`,`master_field`),
|
||||
KEY foreign_field (foreign_db,foreign_table)
|
||||
PRIMARY KEY (`master_db`, `master_table`,
|
||||
`master_field`),
|
||||
KEY foreign_field (foreign_db, foreign_table)
|
||||
) TYPE=MyISAM COMMENT='Relation table';
|
||||
+ put the relation table name in
|
||||
$cfg['Servers'][$i]['relation']
|
||||
@@ -389,8 +391,8 @@ CRIPT_NAME'], '/')+1);
|
||||
view/" and choose foreign fields.
|
||||
|
||||
Please note that in the current (2.3.0) version, master_db must
|
||||
be the same as foreign_db. Those fields have been put in place
|
||||
for a future development of the cross-db relations.
|
||||
be the same as foreign_db. Those fields have been put in future
|
||||
development of the cross-db relations.
|
||||
|
||||
$cfg['Servers'][$i]['table_info'] string
|
||||
Since release 2.3.0 you can describe, in a special 'table_info'
|
||||
@@ -406,7 +408,7 @@ CRIPT_NAME'], '/')+1);
|
||||
`db_name` varchar(64) NOT NULL default '',
|
||||
`table_name` varchar(64) NOT NULL default '',
|
||||
`display_field` varchar(64) NOT NULL default '',
|
||||
PRIMARY KEY (`db_name`,`table_name`)
|
||||
PRIMARY KEY (`db_name`, `table_name`)
|
||||
) TYPE=MyISAM COMMENT='Table information for
|
||||
phpMyAdmin';
|
||||
+ put the table name in $cfg['Servers'][$i]['table_info']
|
||||
@@ -418,35 +420,33 @@ CRIPT_NAME'], '/')+1);
|
||||
|
||||
$cfg['Servers'][$i]['table_coords'] string
|
||||
$cfg['Servers'][$i]['pdf_pages'] string
|
||||
Since release 2.3.0 you can have phpMyAdmin create PDF Pages
|
||||
Since release 2.3.0 you can have phpMyAdmin create PDF pages
|
||||
showing the relations between your tables. To do this it needs
|
||||
two tables 'pdf_pages' (storing information about the available
|
||||
pdf Pages) and 'table_coords' (storing coordinates where each
|
||||
two tables "pdf_pages" (storing information about the available
|
||||
pdf pages) and "table_coords" (storing coordinates where each
|
||||
table will be placed on a PDF schema output).
|
||||
PDF output is supported under PHP4, and you must be using also
|
||||
the 'relation' feature and have a table of PDF Pages (see
|
||||
$cfg['Servers'][$i]['pdf_pages']). Also, we used the fpdf
|
||||
library which currently only supports iso-8859 (Latin1)
|
||||
character sets in PDF.
|
||||
You must be using the "relation" feature and have a table of
|
||||
PDF pages (see $cfg['Servers'][$i]['pdf_pages']) to create PDF
|
||||
output.
|
||||
To allow the usage of this functionality the superuser has to:
|
||||
|
||||
+ set up a PMA database as described above
|
||||
+ within this database create a table following this scheme:
|
||||
CREATE TABLE `table_coords` (
|
||||
CREATE TABLE `PMA_table_coords` (
|
||||
`db_name` varchar(64) NOT NULL default '',
|
||||
`table_name` varchar(64) NOT NULL default '',
|
||||
`pdf_page_number` int NOT NULL default '0',
|
||||
`x` float unsigned NOT NULL default '0',
|
||||
`y` float unsigned NOT NULL default '0',
|
||||
PRIMARY KEY (`db_name`,`table_name`,
|
||||
PRIMARY KEY (`db_name`, `table_name`,
|
||||
`pdf_page_number`)
|
||||
) TYPE=MyISAM COMMENT='Table coordinates for phpMyAdmin
|
||||
PDF output';
|
||||
+ also within this database create: CREATE TABLE pdf_pages
|
||||
(
|
||||
+ also within this database create:
|
||||
CREATE TABLE `PMA_pdf_pages` (
|
||||
`db_name` varchar(64) NOT NULL default '',
|
||||
page_nr int(10) unsigned NOT NULL auto_increment,
|
||||
page_descr varchar(50) NOT NULL default '',
|
||||
`page_nr` int(10) unsigned NOT NULL auto_increment,
|
||||
`page_descr` varchar(50) NOT NULL default '',
|
||||
PRIMARY KEY (page_nr),
|
||||
KEY (db_name)
|
||||
) TYPE=MyISAM COMMENT='PDF Relationpages for PMA';
|
||||
@@ -459,19 +459,19 @@ CRIPT_NAME'], '/')+1);
|
||||
$cfg['Servers'][$i]['column_comments'] string
|
||||
Since release 2.3.0 you can store comments to describe each
|
||||
column for each table. These will then be shown on the
|
||||
printview. To allow the usage of this functionality the
|
||||
superuser has to:
|
||||
"printview".
|
||||
To allow the usage of this functionality the superuser has to:
|
||||
|
||||
+ set up a PMA database as described above
|
||||
+ within this database create a table following this scheme:
|
||||
CREATE TABLE column_comments (
|
||||
CREATE TABLE `PMA_column_comments` (
|
||||
id int(5) unsigned NOT NULL auto_increment,
|
||||
db_name varchar(64) NOT NULL default '',
|
||||
table_name varchar(64) NOT NULL default '',
|
||||
column_name varchar(64) NOT NULL default '',
|
||||
comment varchar(255) NOT NULL default '',
|
||||
PRIMARY KEY (id),
|
||||
UNIQUE KEY db_name (db_name,table_name,column_name)
|
||||
UNIQUE KEY db_name (db_name, table_name, column_name)
|
||||
) TYPE=MyISAM COMMENT='Comments for Columns';
|
||||
+ put the table name in $cfg['Servers'][$i]['column_comments']
|
||||
|
||||
@@ -644,14 +644,14 @@ CRIPT_NAME'], '/')+1);
|
||||
when creating a dump file or not.
|
||||
|
||||
$cfg['DefaultTabDatabase'] string
|
||||
Defines the Tab displayed by default on database view. Possible
|
||||
values: 'db_details_structure.php3', 'db_details.php3', or
|
||||
'db_search.php3'.
|
||||
Defines the tab displayed by default on database view. Possible
|
||||
values: "db_details_structure.php3", "db_details.php3" or
|
||||
"db_search.php3".
|
||||
|
||||
$cfg['DefaultTabTable'] string
|
||||
Defines the Tab displayed by default on table view. Possible
|
||||
values: 'tbl_properties_structure.php3', 'tbl_properties.php3',
|
||||
'tbl_select.php3', 'tbl_change.php3'.
|
||||
Defines the tab displayed by default on table view. Possible
|
||||
values: "tbl_properties_structure.php3", "tbl_properties.php3",
|
||||
"tbl_select.php3" or "tbl_change.php3".
|
||||
|
||||
$cfg['ManualBaseShort'] string
|
||||
If set to an URL which points to the MySQL documentation (on
|
||||
@@ -670,7 +670,8 @@ CRIPT_NAME'], '/')+1);
|
||||
$cfg['DefaultCharset'] string
|
||||
Default charset to use for recoding of MySQL queries. This must
|
||||
be enabled and it's described by $cfg['AllowAnywhereRecoding']
|
||||
option. You can give here any charset which is in
|
||||
option.
|
||||
You can give here any charset which is in
|
||||
$cfg['AvailableCharsets'] array and this is just default
|
||||
choice, user can select any of them.
|
||||
|
||||
@@ -750,32 +751,33 @@ CRIPT_NAME'], '/')+1);
|
||||
Repeat the headers every X cells, or 0 to deactivate.
|
||||
|
||||
$cfg['UseSyntaxColoring'] boolean
|
||||
Introduced in 2.3.0 PhpMyAdmin is now able to show SQL in
|
||||
Syntaxcoloring. To use this feature set this value to TRUE (the
|
||||
default). If not everything you want is colored or to influence
|
||||
where a newline is inserted see the Configurationarrays
|
||||
$cfg['keywords'] and $cfg['additional']. Note: for version
|
||||
2.3.0-rc1, syntax coloring is non functional.
|
||||
Introduced in 2.3.0, phpMyAdmin is now able to show SQL in
|
||||
syntax coloring.
|
||||
To use this feature set this value to TRUE (the default). If
|
||||
not everything you want is colored or to influence where a
|
||||
newline is inserted see the configuration arrays
|
||||
$cfg['keywords'] and $cfg['additional'].
|
||||
Note: for version 2.3.0, syntax coloring is non functional.
|
||||
|
||||
$cfg['colorFunctions'] string [HTML color]
|
||||
If you use Syntaxcoloring then this defines the Color of
|
||||
Functionnames. e.g. all that are found in $cfg['Functions'].
|
||||
If you use syntax coloring then this defines the color of
|
||||
function names. e.g. all that are found in $cfg['Functions'].
|
||||
|
||||
$cfg['colorKeywords'] string [HTML color]
|
||||
If you use Syntaxcoloring then this defines the Color of
|
||||
Keywords. e.g. all that are found in $cfg['keywords'].
|
||||
If you use syntax coloring then this defines the color of
|
||||
keywords. e.g. all that are found in $cfg['keywords'].
|
||||
|
||||
$cfg['colorStrings'] string [HTML color]
|
||||
If you use Syntaxcoloring then this defines the Color of
|
||||
Strings. e.g. all that are between ' or "
|
||||
If you use syntax coloring then this defines the color of
|
||||
strings. e.g. all that are between ' or "
|
||||
|
||||
$cfg['colorColType'] string [HTML color]
|
||||
If you use Syntaxcoloring then this defines the Color of
|
||||
ColumnTypes. e.g. all that are found in $cfg['ColumnTypes'].
|
||||
If you use syntax coloring then this defines the color of
|
||||
column types. e.g. all that are found in $cfg['ColumnTypes'].
|
||||
|
||||
$cfg['colorAdd'] string [HTML color]
|
||||
If you use Syntaxcoloring then this defines the Color of
|
||||
additional Keywords that do not get a newline. e.g. all that
|
||||
If you use syntax coloring then this defines the color of
|
||||
additional keywords that do not get a newline. e.g. all that
|
||||
are found in $cfg['additional'].
|
||||
|
||||
$cfg['ColumnTypes'] array
|
||||
@@ -791,14 +793,16 @@ CRIPT_NAME'], '/')+1);
|
||||
need to edit this.
|
||||
|
||||
$cfg['keywords'] array
|
||||
A list of Keywords that is used for Syntaxcoloring. All
|
||||
Keywords that are in this list will also get a new line before
|
||||
them. Usually you won't need to change those.
|
||||
A list of keywords that is used for syntax coloring. All
|
||||
keywords that are in this list will also get a new line before
|
||||
them.
|
||||
Usually you won't need to change those.
|
||||
|
||||
$cfg['additional'] array
|
||||
A list of additional Keywords that is used for Syntaxcoloring.
|
||||
All Keywords that are in this list will not get a new line
|
||||
before them. Usually you won't need to change those.
|
||||
A list of additional keywords that is used for syntax coloring.
|
||||
All keywords that are in this list will not get a new line
|
||||
before them.
|
||||
Usually you won't need to change those.
|
||||
______________________________________________________________________
|
||||
|
||||
Top - Requirements - Introduction - Installation -
|
||||
@@ -808,7 +812,7 @@ CRIPT_NAME'], '/')+1);
|
||||
FAQ - Frequently Asked Questions
|
||||
|
||||
Server - Configuration - Limitations - Multi-user - Browsers
|
||||
- Usage tips - Project - Syntax Coloring
|
||||
- Usage tips - Project
|
||||
|
||||
[Server]
|
||||
|
||||
@@ -950,15 +954,12 @@ FAQ - Frequently Asked Questions
|
||||
to bugs in MySQL 4. MySQL 4 is still an alpha release and should be
|
||||
used for test purposes only!
|
||||
|
||||
I'm running MySQL 4.0.1 on a Windows NT machine. Each time I create a
|
||||
table the table name is changed to lowercase.
|
||||
This seems to be a bug of MySQL 4.0.1 because it also appears when
|
||||
using the MySQL commandline. Currently we only know about its
|
||||
appearance on Windows NT systems, but it is possible that it appears
|
||||
on other systems, too.
|
||||
If you encounter this bug together with another OS and/or MySQL
|
||||
version or you know how to work around it, please post a message into
|
||||
our bug tracker at SourceForge.
|
||||
I'm running MySQL <= 4.0.1 having 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.
|
||||
This is a bug of MySQL <= 4.0.1. Please upgrade to at least
|
||||
MySQL 4.0.2 or turn off your lower_case_table_names directive.
|
||||
|
||||
I can't run the "display relations" feature because the script seems
|
||||
not to know the font face I'm using!
|
||||
@@ -1163,6 +1164,12 @@ FAQ - Frequently Asked Questions
|
||||
whitespace in the SQL-Query edit area: the page scrolls down.
|
||||
This is a Mozilla bug (see bug #26882 at Bugzilla).
|
||||
|
||||
With Netscape 4.75 I get empty rows between each row of data in a CSV
|
||||
exported file.
|
||||
This is a known Netscape 4.75 bug: it adds some line feeds when
|
||||
exporting data in octet-stream mode. Since we can't detect the
|
||||
specific Netscape version, we cannot workaround this bug.
|
||||
|
||||
[Using phpMyAdmin]
|
||||
|
||||
I can't insert new rows into a table - MySQL brings up a SQL-error.
|
||||
@@ -1233,8 +1240,8 @@ FAQ - Frequently Asked Questions
|
||||
) TYPE=MyISAM;
|
||||
INSERT INTO towns VALUES ('S', 'Sherbrooke');
|
||||
INSERT INTO towns VALUES ('M', 'Montr<74>al');
|
||||
INSERT INTO `PMA_relation` VALUES ('mydb','persons', 'town_code',
|
||||
'mydb', 'towns', 'town_code');
|
||||
INSERT INTO `PMA_relation` VALUES ('mydb', 'persons',
|
||||
'town_code', 'mydb', 'towns', 'town_code');
|
||||
INSERT INTO `PMA_relation` VALUES ('mydb', 'persons',
|
||||
'country_code', 'mydb', 'countries', 'country_code');
|
||||
Then test like this:
|
||||
@@ -1256,7 +1263,7 @@ FAQ - Frequently Asked Questions
|
||||
table, and move the mouse over a town code or country code.
|
||||
|
||||
How can I produce a PDF schema of my database?
|
||||
First you have to fill the 'relation', 'table_coords' and 'pdf_pages'
|
||||
First you have to fill the "relation", "table_coords" and "pdf_pages"
|
||||
configuration variables.
|
||||
Then, think about your schema layout: which tables will go on which
|
||||
pages.
|
||||
@@ -1283,25 +1290,25 @@ FAQ - Frequently Asked Questions
|
||||
left frame again
|
||||
* Now, again at the bottom of the page you should be able to choose
|
||||
"Display PDF schema"
|
||||
For testing it might be useful to show the Grid as well, so you
|
||||
can see the coordinates used
|
||||
maybe also choose Color and submit.
|
||||
For testing it might be useful to show the grid as well, so you
|
||||
can see the coordinates used.
|
||||
Maybe also choose color and submit.
|
||||
* Save the file he will offer you to something like Schema.pdf
|
||||
(Internet Explorer has some Bug there which might make it offer it
|
||||
(Internet Explorer has some bug there which might make it offer it
|
||||
without an extension. Under Windows it is important to have the
|
||||
Extension .pdf, in under OS you should be fine just saving the
|
||||
file under the name it offers) in the navigation on top
|
||||
extension ".pdf", under other OSes you should be fine just saving
|
||||
the file under the name it offers).
|
||||
|
||||
I don't like the way syntaxcoloring displays my query
|
||||
There is two things about the way how the Syntaxcoloring works that
|
||||
I don't like the way syntax coloring displays my query!
|
||||
There is two things about the way how the syntax coloring works that
|
||||
you can easily change yourself:
|
||||
* number of newlines within your statement
|
||||
All Words that are in $cfg['keywords'] will get a newline in front
|
||||
of them, all words in $cfg['additional'] don't. So say you don't
|
||||
All words that are in $cfg['keywords'] will get a newline in front
|
||||
of them, all words in $cfg['additional'] won't. So say you don't
|
||||
like to have a newline in front of every WHERE, you need to remove
|
||||
it from the $cfg['keywords'] array and enter it in the
|
||||
$cfg['additional'] array instead.
|
||||
* Colors
|
||||
* colors
|
||||
The colors are easily changed using the variables
|
||||
+ $cfg['colorFunctions']
|
||||
+ $cfg['colorKeywords']
|
||||
@@ -1323,6 +1330,17 @@ FAQ - Frequently Asked Questions
|
||||
If you really want to grant using a wildcard, there is a dialog box "
|
||||
Database (wildcards allowed)" for this.
|
||||
|
||||
What is the curious symbol <20> in the table statistics?
|
||||
It means "average".
|
||||
|
||||
I want to understand some Export options.
|
||||
"Complete inserts" adds the column names on every INSERT command, for
|
||||
better documentation (but resulting file is bigger).
|
||||
"Extended inserts" provides a shorter dump file by using only once the
|
||||
INSERT verb and the table name.
|
||||
"Enclose table and field names with backquotes" ensures that field and
|
||||
table names formed with special characters are protected.
|
||||
|
||||
[phpMyAdmin project]
|
||||
|
||||
I have found a bug. How do I inform developers?
|
||||
@@ -1336,6 +1354,9 @@ FAQ - Frequently Asked Questions
|
||||
Always use the current cvs version of your language file. For a new
|
||||
language, start from english.inc.php3. If you don't know how to get
|
||||
the cvs version, please ask one of the developers.
|
||||
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 buttons would not display correctly.
|
||||
You can then put your translations, as a zip file to avoid losing
|
||||
special characters, on the sourceforge.net translation tracker.
|
||||
It would be a good idea to subscribe to the phpmyadmin-translators
|
||||
|
||||
Reference in New Issue
Block a user