diff --git a/ChangeLog b/ChangeLog
index 160d5f8f1..1c34496e8 100755
--- a/ChangeLog
+++ b/ChangeLog
@@ -88,6 +88,12 @@ $Id$
- bug #2998889 [import] Import button does not work in Catalan
- [browse] Fix handling of sort order if only column is specified.
+ [lang] Greek update, thanks to Panagiotis Papazoglou - panos78
++ [lang] Updated lot of translation based on work done in master branch.
+- bug #3008411 [databases] Last dropped database remains active in navi
+- bug #2986383 [parser] Not all data being shown / counted
+- bug [synchronize] Rows were deleted in target table regardless of the
+ "Would you like to delete..." option
+- bug [privileges] List of tables not shown when the db name has a wildcard
3.3.3.0 (2010-05-10)
- patch #2982480 [navi] Do not group if there would be one table in group,
diff --git a/Documentation.html b/Documentation.html
index bbb7dfbf0..659cd68c7 100755
--- a/Documentation.html
+++ b/Documentation.html
@@ -101,8 +101,8 @@ vim: expandtab ts=4 sw=4 sts=4 tw=78
Currently phpMyAdmin can:
-
browse and drop databases, tables, views, fields and indexes
-
create, copy, drop, rename and alter databases, tables, fields and
+
browse and drop databases, tables, views, columns and indexes
+
create, copy, drop, rename and alter databases, tables, columns and
indexes
maintenance server, databases and tables, with proposals on server
configuration
For a whole set of new features (bookmarks, comments,
SQL-history,
tracking mechanism,
- PDF-generation, field contents
+ PDF-generation, column contents
transformation, etc.) you need to create a set of special tables. Those
tables can be located in your own database, or in a central database for a
multi-user installation (this database would then be accessed by the
@@ -893,17 +893,17 @@ since this link provides funding for phpMyAdmin.
$cfg['Servers'][$i]['relation'] string
Since release 2.2.4 you can describe, in a special 'relation' table,
- which field is a key in another table (a foreign key). phpMyAdmin
+ which column is a key in another table (a foreign key). phpMyAdmin
currently uses this to
make clickable, when you browse the master table, the data values
that point to the foreign table;
-
display in an optional tool-tip the "display field"
+
display in an optional tool-tip the "display column"
when browsing the master table, if you move the mouse to a column
containing a foreign key (use also the 'table_info' table);
(see
FAQ 6.7)
in edit/insert mode, display a drop-down list of possible foreign
- keys (key value and "display field" are shown)
+ keys (key value and "display column" are shown)
(see
FAQ 6.21)
display links on the table properties page, to check referential
@@ -925,12 +925,13 @@ since this link provides funding for phpMyAdmin.
$cfg['Servers'][$i]['relation']
now as normal user open phpMyAdmin and for each one of your
tables where you want to use this feature, click
- "Structure/Relation view/" and choose foreign fields.
+ "Structure/Relation view/" and choose foreign
+ columns.
Please note that in the current version, master_db
- must be the same as foreign_db. Those fields have been put in
+ must be the same as foreign_db. Those columns have been put in
future development of the cross-db relations.
@@ -939,7 +940,7 @@ since this link provides funding for phpMyAdmin.
Since release 2.3.0 you can describe, in a special 'table_info'
- table, which field is to be displayed as a tool-tip when moving the
+ table, which column is to be displayed as a tool-tip when moving the
cursor over the corresponding key.
This configuration variable will hold the name of this special
table. To allow the usage of this functionality:
@@ -947,10 +948,10 @@ since this link provides funding for phpMyAdmin.
put the table name in
$cfg['Servers'][$i]['table_info']
then for each table where you want to use this feature,
- click "Structure/Relation view/Choose field to display"
- to choose the field.
+ click "Structure/Relation view/Choose column to display"
+ to choose the column.
$cfg['Servers'][$i]['table_coords'] string
@@ -997,7 +998,7 @@ since this link provides funding for phpMyAdmin.
based on the following table structure. See
Transformations for further information. To use the
MIME-transformation system, your column_info table has to have the three
- new fields 'mimetype', 'transformation', 'transformation_options'.
+ new columns 'mimetype', 'transformation', 'transformation_options'.
To allow the usage of this functionality:
@@ -1154,7 +1155,7 @@ CREATE DATABASE,ALTER DATABASE,DROP DATABASE
$cfg['Servers'][$i]['verbose_check'] boolean
Because release 2.5.0 introduced the new MIME-transformation support, the
- column_info table got enhanced with three new fields. If the above variable
+ column_info table got enhanced with three new columns. If the above variable
is set to TRUE (default) phpMyAdmin will check if you have the
latest table structure available. If not, it will emit a warning to the
superuser.
@@ -1531,9 +1532,9 @@ CREATE DATABASE,ALTER DATABASE,DROP DATABASE
contains more rows, "Previous" and "Next" links will be shown.
$cfg['Order'] string [DESC|ASC|SMART]
-
Defines whether fields are displayed in ascending (ASC) order,
+
Defines whether columns are displayed in ascending (ASC) order,
in descending (DESC) order or in a "smart"
- (SMART) order - I.E. descending order for fields of type TIME,
+ (SMART) order - I.E. descending order for columns of type TIME,
DATE, DATETIME and TIMESTAMP, ascending order else- by default.
$cfg['DisplayBinaryAsHex'] boolean
@@ -1541,12 +1542,12 @@ CREATE DATABASE,ALTER DATABASE,DROP DATABASE
option is ticked by default.
$cfg['ProtectBinary'] boolean or string
-
Defines whether BLOB or BINARY fields are protected
+
Defines whether BLOB or BINARY columns are protected
from editing when browsing a table's content. Valid values are:
-
FALSE to allow editing of all fields;
-
'blob' to allow editing of all fields except BLOBS;
+
FALSE to allow editing of all columns;
+
'blob' to allow editing of all columns except BLOBS;
'all' to disallow editing of all BINARY or
- BLOB fields.
There are 3 display modes: horizontal, horizontalflipped and vertical.
Define which one is displayed by default. The first mode displays each
row on a horizontal line, the second rotates the headers by 90
- degrees, so you can use descriptive headers even though fields only
+ degrees, so you can use descriptive headers even though columns only
contain small values and still print them out. The vertical mode sorts
each row on a vertical lineup.
@@ -1903,9 +1904,9 @@ $cfg['TrustedProxies'] =
'vertical' you can have each field lined up vertically beneath each
other. You can save up a lot of place on the horizontal direction and
no longer have to scroll. If you set this to integer, editing of fewer
- columns will appear in 'vertical' mode, while editing of more fields
+ columns will appear in 'vertical' mode, while editing of more columns
still in 'horizontal' mode. This way you can still effectively edit
- large number of fields, while having full view on few of them.
+ large number of columns, while having full view on few of them.
$cfg['ShowBrowseComments'] boolean $cfg['ShowPropertyComments'] boolean
@@ -1914,7 +1915,7 @@ $cfg['TrustedProxies'] =
display of column comments in Browse or Property display. In browse
mode, the comments are shown inside the header. In property mode,
comments are displayed using a CSS-formatted dashed-line below the
- name of the field. The comment is shown as a tool-tip for that field.
+ name of the column. The comment is shown as a tool-tip for that column.
Default queries that will be displayed in query boxes when user didn't
specify any. Use %d for database name, %t for table name and %f for a
- comma separated list of field names. Note that %t and %f are only
+ comma separated list of column names. Note that %t and %f are only
applicable to $cfg['DefaultQueryTable'].
Operators available for search operations on numeric and date fields.
+
Operators available for search operations on numeric and date columns.
$cfg['TextOperators'] array
-
Operators available for search operations on character fields.
+
Operators available for search operations on character columns.
Note that we put LIKE by default instead of
LIKE %...%, to avoid unintended performance problems
in case of huge tables.
$cfg['EnumOperators'] array
-
Operators available for search operations on enum fields.
+
Operators available for search operations on ENUM columns.
$cfg['NullOperators'] array
Additional operators available for search operations when the
- field can be null.
+ column can be null.
@@ -2375,14 +2376,14 @@ setfacl -d -m "g:www-data:rwx" tmp
and the proper directives. Please see the Configuration
section on how to do so.
-
You can apply different transformations to the contents of each field. The
- transformation will take the content of each field and transform it with
+
You can apply different transformations to the contents of each column. The
+ transformation will take the content of each column and transform it with
certain rules defined in the selected transformation.
-
Say you have a field 'filename' which contains a filename. Normally you would
+
Say you have a column 'filename' which contains a filename. Normally you would
see in phpMyAdmin only this filename. Using transformations you can transform
that filename into a HTML link, so you can click inside of the phpMyAdmin
- structure on the field's link and will see the file displayed in a new browser
+ structure on the column's link and will see the file displayed in a new browser
window. Using transformation options you can also specify strings to
append/prepend to a string or the format you want the output stored in.
Go to your tbl_structure.php page (i.e. reached through
clicking on the 'Structure' link for a table). There click on
- "Change" (or change icon) and there you will see three new fields at
+ "Change" (or change icon) and there you will see three new
+ fields at
the end of the line. They are called 'MIME-type', 'Browser transformation' and
'Transformation options'.
One can, however, use empty mime-types and global transformations which should work
for many mimetypes. You can also use transforms on a different mimetype they where built
for, but pay attention to option usage as well as what the transformation does to your
- field.
+ column.
There is a basic file called 'global.inc.php'. This function can be included by
any other transform function and provides some basic functions.
Please see the libraries/transformations/TEMPLATE file for adding your own transform
function. See the libraries/transformations/TEMPLATE_MIMETYPE for adding a mimetype
- without a transform function. Also note the introduction of a function description in
- the language files. For each function a $strTransformation_[filename without .inc.php]
- has to exist.
-
-
You can use the template generator to generate new functions and entries in the
- language file.
+ without a transform function.
To create a new transform function please see
libraries/transformations/template_generator.sh.
@@ -2565,15 +2562,15 @@ setfacl -d -m "g:www-data:rwx" tmp
you want to transform.
$options - Contains any user-passed options to a transform function
as an array.
-
$meta - Contains an object with field information to your column.
+
$meta - Contains an object with information about your column.
The data is drawn from the output of the
mysql_fetch_field()
function. This means, all object properties described on the
manual page are
- available in this variable and can be used to transform a field accordingly
+ available in this variable and can be used to transform a column accordingly
to unsigned/zerofill/not_null/... properties.
The $meta->mimetype variable contains the original MIME-type of the
- field (i.e. 'text/plain', 'image/jpeg' etc.)
+ column (i.e. 'text/plain', 'image/jpeg' etc.)
Additionally you should also provide additional function to provide
@@ -2773,11 +2770,11 @@ setfacl -d -m "g:www-data:rwx" tmp
and try to increase it.
In previous MySQL versions, the User and Password fields
- were named user and password. Please modify your field
+
In previous MySQL versions, the User and Passwordcolumns
+ were named user and password. Please modify your column
names to align with current standards.
+ a new table the table and column names are changed to lowercase!
This happens because the MySQL directive lower_case_table_names
defaults to 1 (ON) in the Win32 version of MySQL. You can change
@@ -2975,8 +2972,8 @@ setfacl -d -m "g:www-data:rwx" tmp
available starting with MySQL 3.23.56 / 4.0.11-gamma.
Suhosin configuration might lead to malfunction in some cases and it can
not be fully avoided as phpMyAdmin is kind of application which needs to
- transfer big amounts of fields in single HTTP request, what is something
+ transfer big amounts of columns in single HTTP request, what is something
what Suhosin tries to prevent. Generally all
suhosin.request.*, suhosin.post.* and
suhosin.get.* directives can have negative effect on
@@ -3435,13 +3432,13 @@ have either the APC extension
3.6 What is currently not supported in phpMyAdmin about InnoDB?
In Relation view, being able to choose a table in another database,
- or having more than one index field in the foreign key.
+ or having more than one index column in the foreign key.
In Query-by-example (Query), automatic generation of the query
LEFT JOIN from the foreign table.
We could reproduce this problem only under Win98/98SE. Testing under
- WinNT4 or Win2K, we could easily create more than 60 fields.
+ WinNT4 or Win2K, we could easily create more than 60 columns.
- A workaround is to create a smaller number of fields, then come back to
- your table properties and add the other fields.
+ A workaround is to create a smaller number of columns, then come back to
+ your table properties and add the other columns.
Your table neither have a primary key nor an unique one, so we must use a
@@ -3876,7 +3874,7 @@ $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
Examine the SQL error with care. Often the problem is caused by
- specifying a wrong field-type.
+ specifying a wrong column-type.
Common errors include:
- This is the way to create a multi-fields
+ This is the way to create a multi-columns
index. If you want two indexes, create the first one when creating the
table, save, then display the table properties and click the Index link to
create the other index.
@@ -3902,11 +3901,11 @@ $cfg['Servers'][$i]['AllowDeny']['rules'] = array(
- Since version 2.2.3, you have a checkbox for each field that can be null.
+ Since version 2.2.3, you have a checkbox for each column that can be null.
Before 2.2.3, you had to enter "null", without the quotes, as the
- field's value. Since version 2.5.5, you have to use the checkbox to get
+ column's value. Since version 2.5.5, you have to use the checkbox to get
a real NULL value, so if you enter "NULL" this means you want
- a literal NULL in the field, and not a NULL value (this works in PHP4).
+ a literal NULL in the column, and not a NULL value (this works in PHP4).
@@ -3988,7 +3987,7 @@ INSERT INTO REL_towns VALUES ('M', 'Montréal');
in Links, for "town_code" choose "REL_towns->code"
in Links, for "country_code" choose "REL_countries->country_code"
on table "REL_towns" click Structure, then Relation view
-
in "Choose field to display", choose "description"
+
in "Choose column to display", choose "description"
repeat the two previous steps for table "REL_countries"
@@ -3998,7 +3997,7 @@ INSERT INTO REL_towns VALUES ('M', 'Montréal');
Choose "Query"
Use tables: persons, towns, countries
Click "Update query"
-
In the fields row, choose persons.person_name and click the
+
In the columns row, choose persons.person_name and click the
"Show" tickbox
Do the same for towns.description and countries.descriptions in the
other 2 columns
@@ -4008,13 +4007,13 @@ INSERT INTO REL_towns VALUES ('M', 'Montréal');
Starting from the previous example, create the pma_table_info as explained
in the configuration section, then browse your persons table,
and move the mouse over a town code or country code.
- See also FAQ 6.21 for an additional feature that "display field"
+ See also FAQ 6.21 for an additional feature that "display column"
enables: drop-down list of possible values.
@@ -4098,8 +4097,8 @@ INSERT INTO REL_towns VALUES ('M', 'Montréal');
different structure.
"Add AUTO_INCREMENT value" ensures that AUTO_INCREMENT value
(if any) will be included in backup.
-
"Enclose table and field names with backquotes" ensures that
- field and table names formed with special characters are protected.
+
"Enclose table and column names with backquotes" ensures that
+ column and table names formed with special characters are protected.
"Add into comments" includes column comments, relations, and MIME
types set in the pmadb in the dump as
SQL comments (/* xxx */).
@@ -4156,15 +4155,15 @@ INSERT INTO REL_towns VALUES ('M', 'Montréal');
We utilize it as free SOAP service.
The right way to do this, is to create the field without any indexes,
+
The right way to do this, is to create the column without any indexes,
then display the table structure and use the "Create an index"
- dialog. On this page, you will be able to choose your BLOB field, and
+ dialog. On this page, you will be able to choose your BLOB column, and
set a size to the index, which is the condition to create an index on
- a BLOB field.
Slow down :). Defining mimetypes is of no use, if you can't put transformations
- on them. Otherwise you could just put a comment on the field. Because entering
+ on them. Otherwise you could just put a comment on the column. Because entering
your own mimetype will cause serious syntax checking issues and validation,
this introduces a high-risk false-user-input situation. Instead you have to
initialize mimetypes using functions or empty mimetype definitions.
@@ -4273,17 +4272,17 @@ INSERT INTO REL_towns VALUES ('M', 'Montréal');
+ possible values for a column, based on some foreign table?
You have to setup appropriate links between the tables, and also
- setup the "display field" in the foreign table. See
+ setup the "display column" in the foreign table. See
FAQ
6.6 for an example. Then, if there are 100 values or less in the
foreign table, a drop-down list of values will be available.
You will see two lists of values, the first list containing the key
- and the display field, the second list containing the display field
+ and the display column, the second list containing the display column
and the key. The reason for this is to be able to type the first
- letter of either the key or the display field.
+ letter of either the key or the display column.
For 100 values or more, a distinct window will appear, to browse foreign
key values and choose one. To change the default limit of 100, see
@@ -4867,7 +4866,7 @@ Jakub Wilk, Thomas Michael Winningham, Vilius Zigmantas, "Manuzhai".
also contributed the French translation.
Alexandr Bravo <abravo_at_hq.admiral.ru> who contributed
- tbl_select.php3, a feature to display only some fields from a table.
+ tbl_select.php3, a feature to display only some columns from a table.
Chris Jackson <chrisj_at_ctel.net> added support for MySQL
functions in tbl_change.php3. He also added the
diff --git a/db_datadict.php b/db_datadict.php
index a38b35b16..7af533c94 100755
--- a/db_datadict.php
+++ b/db_datadict.php
@@ -125,9 +125,9 @@ while ($row = PMA_DBI_fetch_assoc($rowset)) {
/**
- * Gets fields properties
+ * Gets columns properties
*/
- $result = PMA_DBI_query('SHOW FIELDS FROM ' . PMA_backquote($table) . ';', null, PMA_DBI_QUERY_STORE);
+ $result = PMA_DBI_query('SHOW COLUMNS FROM ' . PMA_backquote($table) . ';', null, PMA_DBI_QUERY_STORE);
$fields_cnt = PMA_DBI_num_rows($result);
if (PMA_MYSQL_INT_VERSION < 50025) {
@@ -171,7 +171,7 @@ while ($row = PMA_DBI_fetch_assoc($rowset)) {
?>
-
+
*/ ?>
diff --git a/db_operations.php b/db_operations.php
index 8ba13a28b..40ec65272 100755
--- a/db_operations.php
+++ b/db_operations.php
@@ -121,7 +121,7 @@ if (strlen($db) && (! empty($db_rename) || ! empty($db_copy))) {
if ($this_what != 'nocopy') {
// keep the triggers from the original db+table
- // (third param is empty because delimiters are only intended
+ // (third param is empty because delimiters are only intended
// for importing via the mysql client or our Import feature)
$triggers = PMA_DBI_get_triggers($db, $each_table, '');
@@ -141,7 +141,7 @@ if (strlen($db) && (! empty($db_rename) || ! empty($db_copy))) {
}
unset($trigger);
}
- unset($triggers);
+ unset($triggers);
// this does not apply to a rename operation
if (isset($GLOBALS['add_constraints']) && !empty($GLOBALS['sql_constraints_query'])) {
@@ -380,6 +380,8 @@ if (!$is_information_schema) {
+
+
@@ -422,6 +424,8 @@ if (!$is_information_schema) {
echo 'INSERT INTO ... SELECT';
//}
echo ')'; ?>
+
+
@@ -599,6 +603,8 @@ if (!$is_information_schema) {
. ' ' . "\n"
. PMA_generateCharsetDropdownBox(PMA_CSDROPDOWN_COLLATION,
'db_collation', 'select_db_collation', $db_collation, false, 3)
+ . ''
+ . '' . "\n"
@@ -631,79 +637,15 @@ if ($cfgRelation['pdfwork'] && $num_tables > 0) { ?>
WHERE db_name = \'' . PMA_sqlAddslashes($db) . '\'';
$test_rs = PMA_query_as_controluser($test_query, null, PMA_DBI_QUERY_STORE);
- if ($test_rs && PMA_DBI_num_rows($test_rs) > 0) { ?>
-
-
- 0) {
+ include('./libraries/display_pdf_schema.lib.php');
} // end if
- echo ' ';
+ echo '';
} // end if
/**
diff --git a/db_printview.php b/db_printview.php
index d1ed79c17..a6d66f7b5 100755
--- a/db_printview.php
+++ b/db_printview.php
@@ -102,7 +102,7 @@ else {