nettika/phpmyadmin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

typos

Browse Source
This commit is contained in:
Alexander M. Turek
2003-02-27 23:07:43 +00:00
parent 916133f63b
commit 529e28b153
3 changed files with 101 additions and 100 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
ChangeLog
View File

@@ -5,17 +5,19 @@ phpMyAdmin - Changelog
$Id$
$Source$
2003-02-17 Michal Cihar <nijel@users.sourceforge.net>
2003-02-27 Michal Cihar <nijel@users.sourceforge.net>
* lang/czech: Updated.
* lang/english: Resorted.
2003-02-25 Alexander M. Turek <rabus@users.sourceforge.net>
2003-02-27 Alexander M. Turek <rabus@users.sourceforge.net>
* libraries/common.lib.php3, libraries/config_import.lib.php3:
- Backwards compatibility;
- Removed some unnecessary code;
- Added a small HOWTO.
* config.inc.php3: The tab settings don't fit into the 'left frame' part.
* lang/german-*.inc.php3: Grammar.
* Documentation.html: Fixed some dead links.
* scripts/create_tables.sql: Adjusted table comments.
2003-02-27 Garvin Hicking <me@supergarv.de>
* libraries/common.lib.php3, tbl_properties_links.php3, db_details_links.php3,

190
Documentation.html
View File

@@ -110,7 +110,7 @@
<li>using Query-by-example (QBE), create complex queries automatically connecting required tables</li>
<li>create PDF graphics of your Database layout</li>
<li>search globally in a database or a subset of it</li>
<li>transform stored data into any format using a set of predefined functions,
<li>transform stored data into any format using a set of predefined functions,
like displaying BLOB-data as image or download-link or ...</li>
<li>
communicate in
@@ -179,13 +179,13 @@
in your browser. phpMyAdmin should now display a welcome screen
and your databases, or a login dialog if using http or cookie
authentication mode.</li>
<li> For a whole set of new features (bookmarks, comments, sql-history, pdf-generation)
<li> For a whole set of new features (bookmarks, comments, sql-history, pdf-generation)
you need to create a set of tables in your database. Please look at your scripts/
directory, where you should find a file called <i>create_tables.sql</i>.
You can already use your phpMyAdmin to create the tables for you. Please be
aware that you may have to have special (adminstrator) privileges to create
the database and tables. After having imported the <i>create_tables.sql</i> file,
you should specify the table names in your config.inc.php3 file. The directives
you should specify the table names in your config.inc.php3 file. The directives
used for that can be found in the <a href="#config">Configuration section</a>.</li>
</ol>
@@ -772,13 +772,13 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
Since release 2.3.0 you can store comments to describe each column
for each table. These will then be shown on the &quot;printview&quot;.
<br /><br />
Starting with release 2.5.0, comments are consequently used on the table property
Starting with release 2.5.0, comments are consequently used on the table property
pages and table browse view, showing up as tooltips above the column name (properties page)
or embedded withing the header of table in browse view. They can also be shown
in a table dump. Please see the relevant configuration directives later on.
<br /><br />
Also new in release 2.5.0 is a mime-transformation system which is also based on
the following table structure. See <a href="transformations">Transformations</a>
the following table structure. See <a href="#transformations">Transformations</a>
for further information. To use the mime-transformation system, your column_info
table has to have the three new fields 'mimetype', 'transformation', 'transformation_options'.
<br /><br />
@@ -819,15 +819,15 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
entered manually into the phpMyAdmin interface. If you don't want to use a table-
based history, you can use the JavaScript-based history. Using that, all your
history items are deleted when closing the window.<br /><br />
Using <b>$cfg['QueryHistoryMax']</b> you can specify an amount of history items
you want to have on hold. On every login, this list gets cut to the maximum amount.
<br /><br />
The query history is only available if you use the JavaScript-based query window,
see <b>$cfg['QueryFrame']</b>.
<br /><br />
To allow the usage of this functionality the superuser has to:
<ul>
<li>set up &quot;pmadb&quot; as described above</li>
@@ -863,14 +863,14 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
column_info table got enhanced with thre new fields. 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.<br /><br />
You can disable this checking behavior by setting the variable to false, which
should offer a performance increase.<br /><br />
Recommended to set to FALSE, when you are sure, your table structure is up to date.
<br /><br />
</dd>
<dt>
<b>$cfg['Servers'][$i]['AllowDeny']['order']</b> string
</dt>
@@ -1183,7 +1183,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
&quot;server_processlist.php3&quot;.
<br /><br />
</dd>
<dt><b>$cfg['DefaultTabDatabase'] </b>string</dt>
<dd>
Defines the tab displayed by default on database view. Possible
@@ -1403,7 +1403,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
<b>$cfg['HeaderFlipType'] </b>string
</dt>
<dd>
There are 3 display modes: horizontal, horizontalflipped and vertical. Define
There are 3 display modes: horizontal, horizontalflipped and vertical. Define
which one is displayed by default. The first mode displays each row on a
horiztonal line, the second rotates the headers by 90 degrees, so you can use
descriptive headers even though fields only contain small values and still
@@ -1424,7 +1424,7 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
</dd>
<dt><b>$cfg['ShowBrowseComments'] </b>boolean<br />
<b>$cfg['ShowPropertyComments'] </b>boolean<br />
<b>$cfg['ShowPropertyComments'] </b>boolean<br />
</dt>
<dd>
By setting the corresponding variable to TRUE you can enable the display of
@@ -1492,14 +1492,14 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
variable $cfg['QueryWindowDefTab'] you can specify the default tab to be used
when opening the query window. It can be set to either 'sql', 'files', 'history'
or 'full'.<br /><br />
The variable $cfg['QueryFrameDebug'] can be used by developers for easier future
The variable $cfg['QueryFrameDebug'] can be used by developers for easier future
feature integration.
<br /><br />
</dd>
<dt><b>$cfg['BrowseMIME'] </b>boolean</dt>
<dd>
Enable <a href="transformations">MIME-transformations</a>.
Enable <a href="#transformations">MIME-transformations</a>.
<br /><br />
</dd>
@@ -1660,22 +1660,22 @@ $cfg['PmaAbsoluteUri'] = (!empty($_SERVER['HTTPS']) ? 'https' : 'http') . '://'
<a name="transformationsintro"></a><br />
<h3>[1. Introduction]</h3>
<p>To enable transformations, you have to setup the column_info table and the proper
<p>To enable transformations, you have to setup the column_info table and the proper
directives. Please see the <a href="#config">Configuration section</a> on how to do so.</p>
<br />
<p>You can apply different transformations to the contents of each field. The
transformation will take the content of each field and transform it with
<p>You can apply different transformations to the contents of each field. The
transformation will take the content of each field and transform it with
certain rules defined in the selected transformation.</p><br />
<p>Say you have a field 'filename' which contains a filename. Normale 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
<p>Say you have a field 'filename' which contains a filename. Normale 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 window. Using transformation
options you can also specify strings to append/prepend to a string or the format you
options you can also specify strings to append/prepend to a string or the format you
want the output stored in.</p><br />
<p>For a general overview of all available transformations and their options, you can
<p>For a general overview of all available transformations and their options, you can
consult your <i>&lt;www.your-host.com&gt;/&lt;your-install-dir&gt;/libraries/transformations/overview.php3</i>
installation.</p><br />
<br />
@@ -1683,161 +1683,161 @@ installation.</p><br />
<a name="transformationshowto"></a><br />
<h3>[2. Usage]</h3>
<p>Go to your tbl_properties.inc.php3 page (i.e. reached through clicking on the
'properties' link for a table). There you will see three new fields at the end of the
<p>Go to your tbl_properties.inc.php3 page (i.e. reached through clicking on the
'properties' link for a table). There you will see three new fields at the end of the
line. They are called 'MIME-type', 'Browser transformation' and 'Transformation options'.</p>
<br />
<ul>
<li>The field 'MIME-type' is a dropdown field. You have the options to leave that field
empty or to use 'auto' [this feature is not yet available]. Please note that
<li>The field 'MIME-type' is a dropdown field. You have the options to leave that field
empty or to use 'auto' [this feature is not yet available]. Please note that
transformations are inactive as long as no mimetype is selected.</li><br /><br />
<li>The field 'Browser transformation' is a dropdown field. You can choose from a
hopefully growing amount of pre-defined transformations. See below for information on
<li>The field 'Browser transformation' is a dropdown field. You can choose from a
hopefully growing amount of pre-defined transformations. See below for information on
how to build your own transformation.<br /><br />
There are global transformations and mimetype-bound transformations. Global transformations
can be used for any mimetype. They will take the mimetype, if neccessary, into regard.
Mimetype-bound transformations usually only operate on a certain mimetype. There are
transformations which operate on the main mimetype (like 'image'), which will most likely
take the subtype into regard, and those who only operate on a
There are global transformations and mimetype-bound transformations. Global transformations
can be used for any mimetype. They will take the mimetype, if neccessary, into regard.
Mimetype-bound transformations usually only operate on a certain mimetype. There are
transformations which operate on the main mimetype (like 'image'), which will most likely
take the subtype into regard, and those who only operate on a
specific subtype (like 'image/jpeg').<br /><br />
You can use transformations on mimetypes for which the function was not defined for. There
is no security check for you selected the right transformation, so take care of what the
You can use transformations on mimetypes for which the function was not defined for. There
is no security check for you selected the right transformation, so take care of what the
output will be like.</li><br /><br />
<li>The field 'Transformation options' is a free-type textfield. You have to enter
transform-function specific options here. Usually the transforms can operate with default
options, but it is generally a good idea to look up the overview to see which options are
<li>The field 'Transformation options' is a free-type textfield. You have to enter
transform-function specific options here. Usually the transforms can operate with default
options, but it is generally a good idea to look up the overview to see which options are
neccessary.<br /><br />
Much like the ENUM/SET-Fields, you have to split up several options using the format
'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
Much like the ENUM/SET-Fields, you have to split up several options using the format
'a','b','c',...(NOTE THE MISSING BLANKS). This is because internally the options will be
parsed as an array, leaving the first value the first element in the array, and so
forth.<br /><br />
If you want to specify a MIME charset you can define it in the transformation_options.
You have to put that outside of the pre-defined options of the specific mime-transform,
as the last value of the set. Use the format "'; charset=XXX'". If you use a transform,
for which you can specify 2 options and you want to append a charset, enter "'first
parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
If you want to specify a MIME charset you can define it in the transformation_options.
You have to put that outside of the pre-defined options of the specific mime-transform,
as the last value of the set. Use the format "'; charset=XXX'". If you use a transform,
for which you can specify 2 options and you want to append a charset, enter "'first
parameter','second parameter','charset=us-ascii'". You can, however use the defaults for
the parameters: "'','','charset=us-ascii'".</li><br /><br />
</ul>
<a name="transformationsfiles"></a><br />
<h3>[3. File structure]</h3>
<p>All mimetypes and their transformations are defined through single files in
<p>All mimetypes and their transformations are defined through single files in
the directory 'libraries/transformations/'.</p><br />
<p>They are stored in files to ease up customization and easy adding of new
<p>They are stored in files to ease up customization and easy adding of new
transformations.</p><br />
<p>Because the user cannot enter own mimetypes, it is kept sure that transformations
always work. It makes no sense to apply a transformation to a mimetype, the
<p>Because the user cannot enter own mimetypes, it is kept sure that transformations
always work. It makes no sense to apply a transformation to a mimetype, the
transform-function doesn't know to handle.</p><br />
<p>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
<p>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.</p><br />
<p>There is a basic file called 'global.inc.php3'. This function can be included by
<p>There is a basic file called 'global.inc.php3'. This function can be included by
any other transform function and provides some basic functions.</p><br />
<p>There are 5 possible file names:</p>
<ol>
<li>A mimetype+subtype transform:<br /><br />
[mimetype]_[subtype]__[transform].inc.php3<br /><br />
Please not that mimetype and subtype are seperated via '_', which shall not be
contained in their names. The transform function/filename may contain only
characters which cause no problems in the file system as well as the PHP function
Please not that mimetype and subtype are seperated via '_', which shall not be
contained in their names. The transform function/filename may contain only
characters which cause no problems in the file system as well as the PHP function
naming convention.<br /><br />
The transform function will the be called 'PMA_transform_[mimetype]_[subtype]__[transform]()'.<br /><br />
<b>Example:</b><br /><br />
text_html__formatted.inc.php3<br />
PMA_transform_text_html__formatted()</li><br /><br />
<li>A mimetype (w/o subtype) transform:<br /><br />
[mimetype]__[transform].inc.php3<br /><br />
Please note that there are no single '_' characters.
The transform function/filename may contain only characters which cause no problems
The transform function/filename may contain only characters which cause no problems
in the file system as well as the PHP function naming convention.<br /><br />
The transform function will the be called 'PMA_transform_[mimetype]__[transform]()'.<br /><br />
<b>Example:</b><br /><br />
text__formatted.inc.php3<br />
PMA_transform_text__formatted()</li><br /><br />
<li>A mimetype+subtype without specific transform function<br /><br />
[mimetype]_[subtype].inc.php3<br /><br />
Please note that there are no '__' characters in the filename. Do not use special
Please note that there are no '__' characters in the filename. Do not use special
characters in the filename causing problems with the file system.<br /><br />
No transformation function is defined in the file itself.<br /><br />
<b>Example:</b><br /><br />
text_plain.inc.php3<br />
(No function)</li><br /><br />
<li>A mimetype (w/o subtype) without specific transform function<br /><br />
[mimetype].inc.php3<br /><br />
Please note that there are no '_' characters in the filename. Do not use special
Please note that there are no '_' characters in the filename. Do not use special
characters in the filename causing problems with the file system.<br /><br />
No transformation function is defined in the file itself.<br /><br />
<b>Example:</b><br /><br />
text.inc.php3<br />
(No function)</li><br /><br />
<li>A global transform function with no specific mimetype<br /><br />
global__[transform].inc.php3<br /><br />
The transform function will the be called 'PMA_transform_global__[transform]()'.<br /><br />
<b>Example:</b><br /><br />
global__formatted<br />
PMA_transform_global__formatted()</li>
</ol>
<br />
<p>So generally use '_' to split up mimetype and subtype, and '__' to provide a
<p>So generally use '_' to split up mimetype and subtype, and '__' to provide a
transform function.</p><br />
<p>All filenames containing no '__' in themselves are not shown as valid transform
<p>All filenames containing no '__' in themselves are not shown as valid transform
functions in the dropdown.</p><br />
<p>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.php3]
<p>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.php3]
has to exist.</p><br />
<p>You can use the template generator to generate new functions and entries in the
<p>You can use the template generator to generate new functions and entries in the
language file.</p><br />
<p>To create a new transform function please see libraries/transformations/template_generator.sh.
<p>To create a new transform function please see libraries/transformations/template_generator.sh.
To create a new, empty mimetype please see libraries/transformations/template_generator_mimetype.sh.</p><br />
<!-- FAQ -->
@@ -2910,7 +2910,7 @@ To create a new, empty mimetype please see libraries/transformations/template_ge
</p>
<h4>
[6.17] Transformations: I can't enter my own mimetype! WTF is this feature
[6.17] Transformations: I can't enter my own mimetype! WTF is this feature
then useful for?
</h4>
<p>
@@ -2918,7 +2918,7 @@ To create a new, empty mimetype please see libraries/transformations/template_ge
Otherwise you could just put a comment on the field. 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.
<br />
<br />
Plus, you have a whole overview of available mimetypes. Who knows all those mimetypes by heart so
he/she can enter it at will?
<br />

5
scripts/create_tables.sql
View File

@@ -45,7 +45,7 @@ CREATE TABLE `PMA_table_info` (
`table_name` varchar(64) NOT NULL default '',
`display_field` varchar(64) NOT NULL default '',
PRIMARY KEY (`db_name`, `table_name`)
) TYPE=MyISAM COMMENT='Table information for phpMyAdmin';
) TYPE=MyISAM COMMENT='Table information for phpMyAdmin';
CREATE TABLE `PMA_table_coords` (
`db_name` varchar(64) NOT NULL default '',
@@ -73,10 +73,9 @@ CREATE TABLE `PMA_column_info` (
mimetype varchar(255) NOT NULL default '',
transformation varchar(255) NOT NULL default '',
transformation_options varchar(255) NOT NULL default '',
PRIMARY KEY (id),
UNIQUE KEY db_name (db_name, table_name, column_name)
) TYPE=MyISAM COMMENT='Comments for Columns';
) TYPE=MyISAM COMMENT='Column Information for phpMyAdmin';
CREATE TABLE `PMA_history` (
`id` BIGINT UNSIGNED NOT NULL AUTO_INCREMENT,