Merge remote-tracking branch 'origin/master'
This commit is contained in:
Weblate
commit
a773dea5b6
157
doc/config.rst
157
doc/config.rst
@ -7,8 +7,8 @@ Configuration
|
||||
|
||||
.. warning::
|
||||
|
||||
:abbr:`Mac (Apple Macintosh)` users should note that PHP does not seem to
|
||||
like :abbr:`Mac (Apple Macintosh)` end of lines character (``\r``). So
|
||||
:term:`Mac` users should note that PHP does not seem to
|
||||
like :term:`Mac` end of lines character (``\r``). So
|
||||
ensure you choose the option that allows to use the \*nix end of line
|
||||
character (``\n``) in your text editor before saving a script you have
|
||||
modified.
|
||||
@ -33,10 +33,10 @@ Basic settings
|
||||
:type: string
|
||||
:default: ``''``
|
||||
|
||||
Sets here the complete :abbr:`URL (Uniform Resource Locator)` (with
|
||||
Sets here the complete :term:`URL` (with
|
||||
full path) to your phpMyAdmin installation's directory. E.g.
|
||||
``http://www.example.net/path_to_your_phpMyAdmin_directory/``.
|
||||
Note also that the :abbr:`URL (Uniform Resource Locator)` on some web
|
||||
Note also that the :term:`URL` on some web
|
||||
servers are case–sensitive. Don’t forget the trailing slash at the
|
||||
end.
|
||||
|
||||
@ -128,7 +128,7 @@ Server connection settings
|
||||
:type: string
|
||||
:default: ``'localhost'``
|
||||
|
||||
The hostname or :abbr:`IP (Internet Protocol)` address of your $i-th
|
||||
The hostname or :term:`IP` address of your $i-th
|
||||
MySQL-server. E.g. ``localhost``.
|
||||
|
||||
.. config:option:: $cfg['Servers'][$i]['port']
|
||||
@ -216,10 +216,10 @@ Server connection settings
|
||||
This special account is used for 2 distinct purposes: to make possible all
|
||||
relational features (see :config:option:`$cfg['Servers'][$i]['pmadb']`) and,
|
||||
for a MySQL server running with ``--skip-show-database``, to enable a
|
||||
multi-user installation (:abbr:`HTTP (HyperText Transfer Protocol)` or cookie
|
||||
multi-user installation (:term:`HTTP` or cookie
|
||||
authentication mode).
|
||||
|
||||
When using :abbr:`HTTP (HyperText Transfer Protocol)` or
|
||||
When using :term:`HTTP` or
|
||||
cookie authentication modes (or 'config' authentication mode since phpMyAdmin
|
||||
2.2.1), you need to supply the details of a MySQL account that has ``SELECT``
|
||||
privilege on the *mysql.user (all columns except "Password")*, *mysql.db (all
|
||||
@ -237,7 +237,7 @@ Server connection settings
|
||||
:type: string
|
||||
:default: ``'cookie'``
|
||||
|
||||
Whether config or cookie or :abbr:`HTTP (HyperText Transfer Protocol)`
|
||||
Whether config or cookie or :term:`HTTP`
|
||||
or signon authentication should be used for this server.
|
||||
|
||||
* 'config' authentication (``$auth_type = 'config'``) is the plain old
|
||||
@ -271,12 +271,11 @@ Server connection settings
|
||||
:type: string
|
||||
:default: ``''``
|
||||
|
||||
When using auth\_type = ':abbr:`HTTP (HyperText Transfer Protocol)`',
|
||||
this field allows to define a custom :abbr:`HTTP (HyperText Transfer
|
||||
Protocol)` Basic Auth Realm which will be displayed to the user. If
|
||||
not explicitly specified in your configuration, a string combined of
|
||||
"phpMyAdmin " and either :config:option:`$cfg['Servers'][$i]['verbose']`
|
||||
or :config:option:`$cfg['Servers'][$i]['host']` will be used.
|
||||
When using auth\_type = ``http``, this field allows to define a custom
|
||||
:term:`HTTP` Basic Auth Realm which will be displayed to the user. If not
|
||||
explicitly specified in your configuration, a string combined of
|
||||
"phpMyAdmin " and either :config:option:`$cfg['Servers'][$i]['verbose']` or
|
||||
:config:option:`$cfg['Servers'][$i]['host']` will be used.
|
||||
|
||||
.. _servers_auth_swekey_config:
|
||||
.. config:option:: $cfg['Servers'][$i]['auth_swekey_config']
|
||||
@ -301,7 +300,7 @@ Server connection settings
|
||||
When using :config:option:`$cfg['Servers'][$i]['auth_type']` set to
|
||||
'config', this is the user/password-pair which phpMyAdmin will use to
|
||||
connect to the MySQL server. This user/password pair is not needed when
|
||||
:abbr:`HTTP (HyperText Transfer Protocol)` or cookie authentication is used
|
||||
:term:`HTTP` or cookie authentication is used
|
||||
and should be empty.
|
||||
|
||||
.. _servers_nopassword:
|
||||
@ -445,7 +444,7 @@ Server connection settings
|
||||
* display links on the table properties page, to check referential
|
||||
integrity (display missing foreign keys) for each described key;
|
||||
* in query-by-example, create automatic joins (see :ref:`faq6_6`)
|
||||
* enable you to get a :abbr:`PDF (Portable Document Format)` schema of
|
||||
* enable you to get a :term:`PDF` schema of
|
||||
your database (also uses the table\_coords table).
|
||||
|
||||
The keys can be numeric or character.
|
||||
@ -496,13 +495,11 @@ Server connection settings
|
||||
:type: string
|
||||
:default: ``''``
|
||||
|
||||
Since release 2.3.0 you can have phpMyAdmin create :abbr:`PDF
|
||||
(Portable Document Format)` pages showing the relations between your
|
||||
tables. To do this it needs two tables "pdf\_pages" (storing
|
||||
information about the available :abbr:`PDF (Portable Document Format)`
|
||||
pages) and "table\_coords" (storing coordinates where each table will
|
||||
be placed on a :abbr:`PDF (Portable Document Format)` schema output).
|
||||
You must be using the "relation" feature.
|
||||
Since release 2.3.0 you can have phpMyAdmin create :term:`PDF` pages
|
||||
showing the relations between your tables. To do this it needs two tables
|
||||
"pdf\_pages" (storing information about the available :term:`PDF` pages)
|
||||
and "table\_coords" (storing coordinates where each table will be placed on
|
||||
a :term:`PDF` schema output). You must be using the "relation" feature.
|
||||
|
||||
To allow the usage of this functionality:
|
||||
|
||||
@ -559,10 +556,10 @@ Server connection settings
|
||||
:type: string
|
||||
:default: ``''``
|
||||
|
||||
Since release 2.5.0 you can store your :abbr:`SQL (structured query
|
||||
language)` history, which means all queries you entered manually into
|
||||
the phpMyAdmin interface. If you don't want to use a table-based
|
||||
history, you can use the JavaScript-based history.
|
||||
Since release 2.5.0 you can store your :term:`SQL` history, which means all
|
||||
queries you 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.
|
||||
Using :config:option:`$cfg['QueryHistoryMax']` you can specify an amount of
|
||||
@ -627,7 +624,7 @@ Server connection settings
|
||||
:default: ``''``
|
||||
|
||||
Since release 3.3.x a tracking mechanism is available. It helps you to
|
||||
track every :abbr:`SQL (structured query language)` command which is
|
||||
track every :term:`SQL` command which is
|
||||
executed by phpMyAdmin. The mechanism supports logging of data
|
||||
manipulation and data definition statements. After enabling it you can
|
||||
create versions of tables.
|
||||
@ -782,7 +779,7 @@ Server connection settings
|
||||
:type: string
|
||||
:default: ``''``
|
||||
|
||||
If your rule order is empty, then :abbr:`IP (Internet Protocol)`
|
||||
If your rule order is empty, then :term:`IP`
|
||||
authorization is disabled.
|
||||
|
||||
If your rule order is set to
|
||||
@ -841,16 +838,16 @@ Server connection settings
|
||||
from all'`` if your rule order is set to ``'allow,deny'`` or
|
||||
``'explicit'``.
|
||||
|
||||
For the :abbr:`IP (Internet Protocol)` matching
|
||||
For the :term:`IP` matching
|
||||
system, the following work:
|
||||
|
||||
* ``xxx.xxx.xxx.xxx`` (an exact :abbr:`IP (Internet Protocol)` address)
|
||||
* ``xxx.xxx.xxx.[yyy-zzz]`` (an :abbr:`IP (Internet Protocol)` address range)
|
||||
* ``xxx.xxx.xxx.xxx/nn`` (CIDR, Classless Inter-Domain Routing type :abbr:`IP (Internet Protocol)` addresses)
|
||||
* ``xxx.xxx.xxx.xxx`` (an exact :term:`IP` address)
|
||||
* ``xxx.xxx.xxx.[yyy-zzz]`` (an :term:`IP` address range)
|
||||
* ``xxx.xxx.xxx.xxx/nn`` (CIDR, Classless Inter-Domain Routing type :term:`IP` addresses)
|
||||
|
||||
But the following does not work:
|
||||
|
||||
* ``xxx.xxx.xxx.xx[yyy-zzz]`` (partial :abbr:`IP (Internet Protocol)` address range)
|
||||
* ``xxx.xxx.xxx.xx[yyy-zzz]`` (partial :term:`IP` address range)
|
||||
|
||||
Also IPv6 addresses are not supported.
|
||||
|
||||
@ -909,7 +906,7 @@ Server connection settings
|
||||
:type: string
|
||||
:default: ``''``
|
||||
|
||||
:abbr:`URL (Uniform Resource Locator)` where user will be redirected
|
||||
:term:`URL` where user will be redirected
|
||||
to log in for signon authentication method. Should be absolute
|
||||
including protocol.
|
||||
|
||||
@ -918,7 +915,7 @@ Server connection settings
|
||||
:type: string
|
||||
:default: ``''``
|
||||
|
||||
:abbr:`URL (Uniform Resource Locator)` where user will be redirected
|
||||
:term:`URL` where user will be redirected
|
||||
after logout (doesn't affect config authentication method). Should be
|
||||
absolute including protocol.
|
||||
|
||||
@ -1020,12 +1017,11 @@ Generic settings
|
||||
:type: integer
|
||||
:default: 1000
|
||||
|
||||
The maximum number of characters when a :abbr:`SQL (structured query
|
||||
language)` query is displayed. The default limit of 1000 should be correct
|
||||
to avoid the display of tons of hexadecimal codes that represent BLOBs, but
|
||||
some users have real :abbr:`SQL (structured query language)` queries that
|
||||
are longer than 1000 characters. Also, if a query's length exceeds this
|
||||
limit, this query is not saved in the history.
|
||||
The maximum number of characters when a :term:`SQL` query is displayed. The
|
||||
default limit of 1000 should be correct to avoid the display of tons of
|
||||
hexadecimal codes that represent BLOBs, but some users have real
|
||||
:term:`SQL` queries that are longer than 1000 characters. Also, if a
|
||||
query's length exceeds this limit, this query is not saved in the history.
|
||||
|
||||
.. config:option:: $cfg['PersistentConnections']
|
||||
|
||||
@ -1094,7 +1090,7 @@ Generic settings
|
||||
:type: boolean
|
||||
:default: true
|
||||
|
||||
Defines whether :abbr:`SQL (structured query language)` queries
|
||||
Defines whether :term:`SQL` queries
|
||||
generated by phpMyAdmin should be displayed or not.
|
||||
|
||||
.. config:option:: $cfg['RetainQueryBox']
|
||||
@ -1102,7 +1098,7 @@ Generic settings
|
||||
:type: boolean
|
||||
:default: false
|
||||
|
||||
Defines whether the :abbr:`SQL (structured query language)` query box
|
||||
Defines whether the :term:`SQL` query box
|
||||
should be kept displayed after its submission.
|
||||
|
||||
.. config:option:: $cfg['CodemirrorEnable']
|
||||
@ -1121,16 +1117,15 @@ Generic settings
|
||||
:default: false
|
||||
|
||||
Defines whether normal users (non-administrator) are allowed to delete
|
||||
their own database or not. If set as false, the link :guilabel:`Drop Database`
|
||||
will not be shown, and even a ``DROP DATABASE mydatabase`` will be
|
||||
rejected. Quite practical for :abbr:`ISP (Internet service
|
||||
provider)`'s with many customers.
|
||||
their own database or not. If set as false, the link :guilabel:`Drop
|
||||
Database` will not be shown, and even a ``DROP DATABASE mydatabase`` will
|
||||
be rejected. Quite practical for :term:`ISP` 's with many customers.
|
||||
|
||||
.. note::
|
||||
|
||||
This limitation of :abbr:`SQL (structured query language)` queries is not
|
||||
This limitation of :term:`SQL` queries is not
|
||||
as strict as when using MySQL privileges. This is due to nature of
|
||||
:abbr:`SQL (structured query language)` queries which might be quite
|
||||
:term:`SQL` queries which might be quite
|
||||
complicated. So this choice should be viewed as help to avoid accidental
|
||||
dropping rather than strict privilege limitation.
|
||||
|
||||
@ -1231,7 +1226,7 @@ Cookie authentication options
|
||||
.. note::
|
||||
|
||||
Please use this carefully, as this may allow users access to MySQL servers
|
||||
behind the firewall where your :abbr:`HTTP (HyperText Transfer Protocol)`
|
||||
behind the firewall where your :term:`HTTP`
|
||||
server is placed.
|
||||
|
||||
Navigation panel setup
|
||||
@ -1303,7 +1298,7 @@ Navigation panel setup
|
||||
:type: string
|
||||
:default: ``'index.php'``
|
||||
|
||||
Enter :abbr:`URL (Uniform Resource Locator)` where logo in the
|
||||
Enter :term:`URL` where logo in the
|
||||
navigation panel will point to. For use especially with self made
|
||||
theme which changes this.
|
||||
|
||||
@ -1717,7 +1712,7 @@ Documentation
|
||||
:type: string
|
||||
:default: ``'http://dev.mysql.com/doc/refman'``
|
||||
|
||||
If set to an :abbr:`URL (Uniform Resource Locator)` which points to
|
||||
If set to an :term:`URL` which points to
|
||||
the MySQL documentation (type depends on
|
||||
:config:option:`$cfg['MySQLManualType']`), appropriate help links are
|
||||
generated.
|
||||
@ -1826,7 +1821,7 @@ Web server settings
|
||||
:default: ``'auto'``
|
||||
|
||||
Defines whether to use GZip output buffering for increased speed in
|
||||
:abbr:`HTTP (HyperText Transfer Protocol)` transfers. Set to
|
||||
:term:`HTTP` transfers. Set to
|
||||
true/false for enabling/disabling. When set to 'auto' (string),
|
||||
phpMyAdmin tries to enable output buffering and will automatically
|
||||
disable it if your browser has some problems with buffering. IE6 with
|
||||
@ -1882,11 +1877,9 @@ Web server settings
|
||||
:type: integer
|
||||
:default: 1000
|
||||
|
||||
Limit for length of :abbr:`URL (Uniform Resource Locator)` in links.
|
||||
When length would be above this limit, it is replaced by form with
|
||||
button. This is required as some web servers (:abbr:`IIS (Internet
|
||||
Information Services)`) have problems with long :abbr:`URL (Uniform
|
||||
Resource Locator)`.
|
||||
Limit for length of :term:`URL` in links. When length would be above this
|
||||
limit, it is replaced by form with button. This is required as some web
|
||||
servers (:term:`IIS`) have problems with long :term:`URL` .
|
||||
|
||||
.. config:option:: $cfg['DisableMultiTableMaintenance']
|
||||
|
||||
@ -2160,8 +2153,8 @@ Text fields
|
||||
:default: 2
|
||||
|
||||
Number of columns and rows for the textareas. This value will be
|
||||
emphasized (\*2) for :abbr:`SQL (structured query language)` query
|
||||
textareas and (\*1.25) for :abbr:`SQL (structured query language)`
|
||||
emphasized (\*2) for :term:`SQL` query
|
||||
textareas and (\*1.25) for :term:`SQL`
|
||||
textareas inside the query window.
|
||||
|
||||
The Char\* values are used for CHAR
|
||||
@ -2234,10 +2227,10 @@ Web server upload/save/import directories
|
||||
:type: string
|
||||
:default: ``''``
|
||||
|
||||
The name of the directory where :abbr:`SQL (structured query
|
||||
language)` files have been uploaded by other means than phpMyAdmin
|
||||
(for example, ftp). Those files are available under a drop-down box
|
||||
when you click the database or table name, then the Import tab.
|
||||
The name of the directory where :term:`SQL` files have been uploaded by
|
||||
other means than phpMyAdmin (for example, ftp). Those files are available
|
||||
under a drop-down box when you click the database or table name, then the
|
||||
Import tab.
|
||||
|
||||
If
|
||||
you want different directory for each user, %u will be replaced with
|
||||
@ -2248,7 +2241,7 @@ Web server upload/save/import directories
|
||||
enabled).
|
||||
|
||||
This feature is useful when your file is too big to be
|
||||
uploaded via :abbr:`HTTP (HyperText Transfer Protocol)`, or when file
|
||||
uploaded via :term:`HTTP`, or when file
|
||||
uploads are disabled in PHP.
|
||||
|
||||
.. note::
|
||||
@ -2306,7 +2299,7 @@ Web server upload/save/import directories
|
||||
chmod 700 tmp
|
||||
|
||||
If you cannot change owner of the directory, you can achieve a similar
|
||||
setup using :abbr:`ACL (Access Control List)`:
|
||||
setup using :term:`ACL`:
|
||||
|
||||
.. code-block:: sh
|
||||
|
||||
@ -2366,12 +2359,11 @@ Various display setting
|
||||
:type: integer
|
||||
:default: 25
|
||||
|
||||
All those variables affect the query window feature. A :abbr:`SQL
|
||||
(structured query language)` link or icon is always displayed in the
|
||||
navigation panel. If JavaScript is enabled in your browser, a click on
|
||||
this opens a distinct query window, which is a direct interface to
|
||||
enter :abbr:`SQL (structured query language)` queries. Otherwise, the
|
||||
right panel changes to display a query box.
|
||||
All those variables affect the query window feature. A :term:`SQL` link or
|
||||
icon is always displayed in the navigation panel. If JavaScript is enabled
|
||||
in your browser, a click on this opens a distinct query window, which is a
|
||||
direct interface to enter :term:`SQL` queries. Otherwise, the right panel
|
||||
changes to display a query box.
|
||||
|
||||
The size of this query window can be customized with
|
||||
:config:option:`$cfg['QueryWindowWidth']` and
|
||||
@ -2382,7 +2374,7 @@ Various display setting
|
||||
If :config:option:`$cfg['EditInWindow']` is set to true, a click on [Edit]
|
||||
from the results page (in the :guilabel:`Showing Rows` section) opens the
|
||||
query window and puts the current query inside it. If set to false,
|
||||
clicking on the link puts the :abbr:`SQL (structured query language)` query
|
||||
clicking on the link puts the :term:`SQL` query
|
||||
in the right panel's query box.
|
||||
|
||||
If :config:option:`$cfg['QueryHistoryDB']` is set to ``true``, all your
|
||||
@ -2556,8 +2548,8 @@ SQL parser settings
|
||||
:type: string
|
||||
:default: ``'html'``
|
||||
|
||||
The main use of the new :abbr:`SQL (structured query language)` Parser
|
||||
is to pretty-print :abbr:`SQL (structured query language)` queries. By
|
||||
The main use of the new :term:`SQL` Parser
|
||||
is to pretty-print :term:`SQL` queries. By
|
||||
default we use HTML to format the query, but you can disable this by
|
||||
setting this variable to ``'none'``.
|
||||
|
||||
@ -2577,7 +2569,7 @@ SQL parser settings
|
||||
:type: string
|
||||
:default: ``'em'``
|
||||
|
||||
For the pretty-printing of :abbr:`SQL (structured query language)` queries,
|
||||
For the pretty-printing of :term:`SQL` queries,
|
||||
under some cases the part of a query inside a bracket is indented. By
|
||||
changing :config:option:`$cfg['SQP']['fmtInd']` you can change the amount
|
||||
of this indent.
|
||||
@ -2599,7 +2591,7 @@ SQL parser settings
|
||||
:default:
|
||||
|
||||
This array is used to define the colours for each type of element of
|
||||
the pretty-printed :abbr:`SQL (structured query language)` queries.
|
||||
the pretty-printed :term:`SQL` queries.
|
||||
The tuple format is *class* => [*HTML colour code* | *empty string*]
|
||||
|
||||
|
||||
@ -2629,8 +2621,7 @@ SQL parser settings
|
||||
attribute
|
||||
* **alpha\_functionName** Identifiers matching a MySQL function name
|
||||
* **alpha\_reservedWord** Identifiers matching any other reserved word
|
||||
* **alpha\_variable** Identifiers matching a :abbr:`SQL (structured
|
||||
query language)` variable ``"@foo"``
|
||||
* **alpha\_variable** Identifiers matching a :term:`SQL` variable ``"@foo"``
|
||||
* **alpha\_identifier** All other identifiers
|
||||
* **quote** Applies to all quotation mark classes
|
||||
* **quote\_double** Double quotes ``"``
|
||||
@ -2652,9 +2643,9 @@ SQL validator settings
|
||||
:type: boolean
|
||||
:default: false
|
||||
|
||||
phpMyAdmin now supports use of the `Mimer :abbr:`SQL (structured query
|
||||
language)` Validator <http://developer.mimer.com/validator/index.htm>`_
|
||||
service, as originally published on `Slashdot
|
||||
phpMyAdmin now supports use of the `Mimer :term:`SQL` Validator
|
||||
<http://developer.mimer.com/validator/index.htm>`_ service, as originally
|
||||
published on `Slashdot
|
||||
<http://developers.slashdot.org/article.pl?sid=02/02/19/1720246>`_. For
|
||||
help in setting up your system to use the service, see the
|
||||
:ref:`faqsqlvalidator`.
|
||||
|
||||
@ -19,7 +19,7 @@ Credits, in chronological order
|
||||
|
||||
* various fixes and improvements
|
||||
|
||||
* :abbr:`SQL (structured query language)` analyser (most of it)
|
||||
* :term:`SQL` analyser (most of it)
|
||||
|
||||
* current project maintainer
|
||||
|
||||
@ -37,9 +37,8 @@ Credits, in chronological order
|
||||
|
||||
* rewrote and optimized javascript, DHTML and DOM stuff
|
||||
|
||||
* rewrote the scripts so they fit the :abbr:`PEAR (PHP Extension and
|
||||
Application Repository)` coding standards and generate XHTML1.0 and
|
||||
CSS2 compliant codes
|
||||
* rewrote the scripts so they fit the :term:`PEAR` coding standards and
|
||||
generate XHTML1.0 and CSS2 compliant codes
|
||||
|
||||
* improved the language detection system
|
||||
|
||||
@ -51,13 +50,13 @@ Credits, in chronological order
|
||||
|
||||
* table type code
|
||||
|
||||
* Host authentication :abbr:`IP (Internet Protocol)` Allow/Deny
|
||||
* Host authentication :term:`IP` Allow/Deny
|
||||
|
||||
* DB-based configuration (Not completed)
|
||||
|
||||
* :abbr:`SQL (structured query language)` parser and pretty-printer
|
||||
* :term:`SQL` parser and pretty-printer
|
||||
|
||||
* :abbr:`SQL (structured query language)` validator
|
||||
* :term:`SQL` validator
|
||||
|
||||
* many bugfixes and improvements
|
||||
|
||||
@ -109,7 +108,7 @@ Credits, in chronological order
|
||||
|
||||
* privileges administration
|
||||
|
||||
* :abbr:`XML (Extensible Markup Language)` exports
|
||||
* :term:`XML` exports
|
||||
|
||||
* various features and fixes
|
||||
|
||||
@ -144,8 +143,7 @@ Credits, in chronological order
|
||||
|
||||
* built the patch for vertical display of table rows
|
||||
|
||||
* built the Javascript based Query window + :abbr:`SQL (structured query
|
||||
language)` history
|
||||
* built the Javascript based Query window + :term:`SQL` history
|
||||
|
||||
* Improvement of column/db comments
|
||||
|
||||
@ -155,8 +153,8 @@ Credits, in chronological order
|
||||
|
||||
* hierarchical/nested table display
|
||||
|
||||
* :abbr:`PDF (Portable Document Format)`-scratchboard for WYSIWYG-
|
||||
distribution of :abbr:`PDF (Portable Document Format)` relations
|
||||
* :term:`PDF`-scratchboard for WYSIWYG-
|
||||
distribution of :term:`PDF` relations
|
||||
|
||||
* new icon sets
|
||||
|
||||
@ -178,14 +176,14 @@ Credits, in chronological order
|
||||
|
||||
* Maxime Delorme <delorme.maxime\_at\_free.fr>
|
||||
|
||||
* :abbr:`PDF (Portable Document Format)` schema output, thanks also to
|
||||
* :term:`PDF` schema output, thanks also to
|
||||
Olivier Plathey for the "FPDF" library (see <http://www.fpdf.org/>), Steven
|
||||
Wittens for the "UFPDF" library (see <http://www.acko.net/node/56>) and
|
||||
Nicola Asuni for the "TCPDF" library (see <http://www.tcpdf.org/>).
|
||||
|
||||
* Olof Edlund <olof.edlund\_at\_upright.se>
|
||||
|
||||
* :abbr:`SQL (structured query language)` validator server
|
||||
* :term:`SQL` validator server
|
||||
|
||||
* Ivan R. Lanin <ivanlanin\_at\_users.sourceforge.net>
|
||||
|
||||
|
||||
196
doc/faq.rst
196
doc/faq.rst
@ -40,7 +40,7 @@ groups.
|
||||
|
||||
.. _faq1_4:
|
||||
|
||||
1.4 Using phpMyAdmin on :abbr:`IIS (Internet Information Services)`, I'm displayed the error message: "The specified :abbr:`CGI (Common Gateway Interface)` application misbehaved by not returning a complete set of :abbr:`HTTP (HyperText Transfer Protocol)` headers ...".
|
||||
1.4 Using phpMyAdmin on :term:`IIS`, I'm displayed the error message: "The specified :term:`CGI` application misbehaved by not returning a complete set of :term:`HTTP` headers ...".
|
||||
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
You just forgot to read the *install.txt* file from the PHP
|
||||
@ -50,12 +50,11 @@ database.
|
||||
|
||||
.. _faq1_5:
|
||||
|
||||
1.5 Using phpMyAdmin on :abbr:`IIS (Internet Information Services)`, I'm facing crashes and/or many error messages with the :abbr:`HTTP (HyperText Transfer Protocol)`.
|
||||
1.5 Using phpMyAdmin on :term:`IIS`, I'm facing crashes and/or many error messages with the :term:`HTTP`.
|
||||
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
This is a known problem with the PHP :abbr:`ISAPI (Internet Server
|
||||
Application Programming Interface)` filter: it's not so stable. Please
|
||||
use instead the cookie authentication mode.
|
||||
This is a known problem with the PHP :term:`ISAPI` filter: it's not so stable.
|
||||
Please use instead the cookie authentication mode.
|
||||
|
||||
.. _faq1_6:
|
||||
|
||||
@ -69,7 +68,7 @@ and :file:`index.php`.
|
||||
|
||||
.. _faq1_7:
|
||||
|
||||
1.7 How can I GZip or Bzip a dump or a :abbr:`CSV (comma separated values)` export? It does not seem to work.
|
||||
1.7 How can I GZip or Bzip a dump or a :term:`CSV` export? It does not seem to work.
|
||||
-------------------------------------------------------------------------------------------------------------
|
||||
|
||||
These features are based on the ``gzencode()`` and ``bzcompress()``
|
||||
@ -120,10 +119,9 @@ It seems to clear up many problems between Internet Explorer and SSL.
|
||||
------------------------------------------------------------------------------------
|
||||
|
||||
Since version 2.2.4, phpMyAdmin supports servers with open\_basedir
|
||||
restrictions. However you need to create temporary directory and
|
||||
configure it as :config:option:`$cfg['TempDir']`. The uploaded files will be
|
||||
moved there, and after execution of your :abbr:`SQL (structured query
|
||||
language)` commands, removed.
|
||||
restrictions. However you need to create temporary directory and configure it
|
||||
as :config:option:`$cfg['TempDir']`. The uploaded files will be moved there,
|
||||
and after execution of your :term:`SQL` commands, removed.
|
||||
|
||||
.. _faq1_12:
|
||||
|
||||
@ -154,7 +152,7 @@ align with current standards.
|
||||
|
||||
.. _faq1_16:
|
||||
|
||||
1.16 I cannot upload big dump files (memory, :abbr:`HTTP (HyperText Transfer Protocol)` or timeout problems).
|
||||
1.16 I cannot upload big dump files (memory, :term:`HTTP` or timeout problems).
|
||||
-------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Starting with version 2.7.0, the import engine has been re–written and
|
||||
@ -252,7 +250,7 @@ or something similar.
|
||||
|
||||
.. _faq1_21:
|
||||
|
||||
1.21 I am running the :abbr:`CGI (Common Gateway Interface)` version of PHP under Unix, and I cannot log in using cookie auth.
|
||||
1.21 I am running the :term:`CGI` version of PHP under Unix, and I cannot log in using cookie auth.
|
||||
------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
In :file:`php.ini`, set ``mysql.max_links`` higher than 1.
|
||||
@ -294,7 +292,7 @@ check the value of this directive using the query
|
||||
|
||||
.. _faq1_25:
|
||||
|
||||
1.25 I am running Apache with mod\_gzip-1.3.26.1a on Windows XP, and I get problems, such as undefined variables when I run a :abbr:`SQL (structured query language)` query.
|
||||
1.25 I am running Apache with mod\_gzip-1.3.26.1a on Windows XP, and I get problems, such as undefined variables when I run a :term:`SQL` query.
|
||||
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
A tip from Jose Fandos: put a comment on the following two lines in
|
||||
@ -311,7 +309,7 @@ PHP scripts. Of course you have to restart Apache.
|
||||
|
||||
.. _faq1_26:
|
||||
|
||||
1.26 I just installed phpMyAdmin in my document root of :abbr:`IIS (Internet Information Services)` but I get the error "No input file specified" when trying to run phpMyAdmin.
|
||||
1.26 I just installed phpMyAdmin in my document root of :term:`IIS` but I get the error "No input file specified" when trying to run phpMyAdmin.
|
||||
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
This is a permission problem. Right-click on the phpmyadmin folder and
|
||||
@ -396,12 +394,11 @@ branch is still maintained.
|
||||
|
||||
.. _faq1_32:
|
||||
|
||||
1.32 Can I use :abbr:`HTTP (HyperText Transfer Protocol)` authentication with :abbr:`IIS (Internet Information Services)`?
|
||||
1.32 Can I use :term:`HTTP` authentication with :term:`IIS`?
|
||||
--------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Yes. This procedure was tested with phpMyAdmin 2.6.1, PHP 4.3.9 in
|
||||
:abbr:`ISAPI (Internet Server Application Programming Interface)` mode
|
||||
under :abbr:`IIS (Internet Information Services)` 5.1.
|
||||
:term:`ISAPI` mode under :term:`IIS` 5.1.
|
||||
|
||||
#. In your :file:`php.ini` file, set ``cgi.rfc2616_headers = 0``
|
||||
#. In ``Web Site Properties -> File/Directory Security -> Anonymous
|
||||
@ -424,13 +421,11 @@ under :abbr:`IIS (Internet Information Services)` 5.1.
|
||||
1.34 Can I access directly to database or table pages?
|
||||
------------------------------------------------------
|
||||
|
||||
Yes. Out of the box, you can use :abbr:`URL (Uniform Resource
|
||||
Locator)` like http://server/phpMyAdmin/index.php?server=X&db=databas
|
||||
Yes. Out of the box, you can use :term:`URL` like http://server/phpMyAdmin/index.php?server=X&db=databas
|
||||
e&table=table&target=script. For ``server`` you use the server number
|
||||
which refers to the order of the server paragraph in
|
||||
:file:`config.inc.php`. Table and script parts are optional. If you want
|
||||
http://server/phpMyAdmin/database[/table][/script] :abbr:`URL (Uniform
|
||||
Resource Locator)`, you need to do some configuration. Following
|
||||
http://server/phpMyAdmin/database[/table][/script] :term:`URL`, you need to do some configuration. Following
|
||||
lines apply only for `Apache <http://httpd.apache.org>`_ web server.
|
||||
First make sure, that you have enabled some features within global
|
||||
configuration. You need ``Options FollowSymLinks`` and ``AllowOverride
|
||||
@ -451,11 +446,11 @@ forget to change directory name inside of it):
|
||||
|
||||
.. _faq1_35:
|
||||
|
||||
1.35 Can I use :abbr:`HTTP (HyperText Transfer Protocol)` authentication with Apache :abbr:`CGI (Common Gateway Interface)`?
|
||||
1.35 Can I use :term:`HTTP` authentication with Apache :term:`CGI`?
|
||||
----------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Yes. However you need to pass authentication variable to :abbr:`CGI
|
||||
(Common Gateway Interface)` using following rewrite rule:
|
||||
Yes. However you need to pass authentication variable to :term:`CGI` using
|
||||
following rewrite rule:
|
||||
|
||||
.. code-block:: apache
|
||||
|
||||
@ -530,7 +525,7 @@ parameters:
|
||||
needs to be disabled (the default)
|
||||
* `suhosin.log.\* <http://www.hardened-
|
||||
php.net/suhosin/configuration.html#logging_configuration>`_ should not
|
||||
include :abbr:`SQL (structured query language)`, otherwise you get big
|
||||
include :term:`SQL`, otherwise you get big
|
||||
slowdown
|
||||
|
||||
You can also disable the warning using the :config:option:`$cfg['SuhosinDisableWarning']`.
|
||||
@ -624,12 +619,11 @@ Configuration
|
||||
------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Edit your :file:`config.inc.php` file and ensure there is nothing (I.E. no
|
||||
blank lines, no spaces, no characters...) neither before the ``<?php``
|
||||
tag at the beginning, neither after the ``?>`` tag at the end. We also
|
||||
got a report from a user under :abbr:`IIS (Internet Information
|
||||
Services)`, that used a zipped distribution kit: the file
|
||||
:file:`libraries/Config.class.php` contained an end-of-line character (hex
|
||||
0A) at the end; removing this character cleared his errors.
|
||||
blank lines, no spaces, no characters...) neither before the ``<?php`` tag at
|
||||
the beginning, neither after the ``?>`` tag at the end. We also got a report
|
||||
from a user under :term:`IIS`, that used a zipped distribution kit: the file
|
||||
:file:`libraries/Config.class.php` contained an end-of-line character (hex 0A)
|
||||
at the end; removing this character cleared his errors.
|
||||
|
||||
.. _faq2_2:
|
||||
|
||||
@ -695,7 +689,7 @@ revision.
|
||||
|
||||
.. _faq2_5:
|
||||
|
||||
2.5 Each time I want to insert or change a row or drop a database or a table, an error 404 (page not found) is displayed or, with :abbr:`HTTP (HyperText Transfer Protocol)` or cookie authentication, I'm asked to log in again. What's wrong?
|
||||
2.5 Each time I want to insert or change a row or drop a database or a table, an error 404 (page not found) is displayed or, with :term:`HTTP` or cookie authentication, I'm asked to log in again. What's wrong?
|
||||
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Check the value you set for the :config:option:`$cfg['PmaAbsoluteUri']` directive in the phpMyAdmin
|
||||
@ -713,7 +707,7 @@ as expected. Erik Wasser explains: The solution is: if your host is
|
||||
tries to use the socket connection for speeding up things. And that
|
||||
doesn't work in this configuration with port forwarding. If you enter
|
||||
"127.0.0.1" as hostname, everything is right and MySQL uses the
|
||||
:abbr:`TCP (Transmission Control Protocol)` connection.
|
||||
:term:`TCP` connection.
|
||||
|
||||
.. _faqthemes:
|
||||
|
||||
@ -804,7 +798,7 @@ Known limitations
|
||||
|
||||
.. _login_bug:
|
||||
|
||||
3.1 When using :abbr:`HTTP (HyperText Transfer Protocol)` authentication, a user who logged out can not log in again in with the same nick.
|
||||
3.1 When using :term:`HTTP` authentication, a user who logged out can not log in again in with the same nick.
|
||||
-------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
This is related to the authentication mechanism (protocol) used by
|
||||
@ -909,11 +903,11 @@ official phpMyAdmin-homepage.
|
||||
---------------------------------------------------------------------------
|
||||
|
||||
When MySQL is running in ANSI-compatibility mode, there are some major
|
||||
differences in how :abbr:`SQL (structured query language)` is structured (see
|
||||
differences in how :term:`SQL` is structured (see
|
||||
<http://dev.mysql.com/doc/mysql/en/ansi-mode.html>). Most important of all, the
|
||||
quote-character (") is interpreted as an identifier quote character and not as
|
||||
a string quote character, which makes many internal phpMyAdmin operations into
|
||||
invalid :abbr:`SQL (structured query language)` statements. There is no
|
||||
invalid :term:`SQL` statements. There is no
|
||||
workaround to this behaviour. News to this item will be posted in `Bug report
|
||||
#816858
|
||||
<https://sourceforge.net/tracker/index.php?func=detail&aid=816858&group_id=23067&atid=377408>`_
|
||||
@ -974,12 +968,11 @@ it's not likely to be solved in the future.
|
||||
|
||||
.. _faq3_18:
|
||||
|
||||
3.18 When I import a :abbr:`CSV (comma separated values)` file that contains multiple tables, they are lumped together into a single table.
|
||||
3.18 When I import a :term:`CSV` file that contains multiple tables, they are lumped together into a single table.
|
||||
-------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
There is no reliable way to differentiate tables in :abbr:`CSV (comma
|
||||
separated values)` format. For the time being, you will have to break
|
||||
apart :abbr:`CSV (comma separated values)` files containing multiple
|
||||
There is no reliable way to differentiate tables in :term:`CSV` format. For the
|
||||
time being, you will have to break apart :term:`CSV` files containing multiple
|
||||
tables.
|
||||
|
||||
.. _faq3_19:
|
||||
@ -1003,14 +996,13 @@ ISPs, multi-user installations
|
||||
|
||||
.. _faq4_1:
|
||||
|
||||
4.1 I'm an :abbr:`ISP (Internet service provider)`. Can I setup one central copy of phpMyAdmin or do I need to install it for each customer.
|
||||
4.1 I'm an :term:`ISP`. Can I setup one central copy of phpMyAdmin or do I need to install it for each customer.
|
||||
--------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Since version 2.0.3, you can setup a central copy of phpMyAdmin for
|
||||
all your users. The development of this feature was kindly sponsored
|
||||
by NetCologne GmbH. This requires a properly setup MySQL user
|
||||
management and phpMyAdmin :abbr:`HTTP (HyperText Transfer Protocol)`
|
||||
or cookie authentication.
|
||||
Since version 2.0.3, you can setup a central copy of phpMyAdmin for all your
|
||||
users. The development of this feature was kindly sponsored by NetCologne GmbH.
|
||||
This requires a properly setup MySQL user management and phpMyAdmin
|
||||
:term:`HTTP` or cookie authentication.
|
||||
|
||||
.. seealso:: :ref:`authentication_modes`
|
||||
|
||||
@ -1019,12 +1011,13 @@ or cookie authentication.
|
||||
4.2 What's the preferred way of making phpMyAdmin secure against evil access.
|
||||
-----------------------------------------------------------------------------
|
||||
|
||||
This depends on your system. If you're running a server which cannot
|
||||
be accessed by other people, it's sufficient to use the directory
|
||||
protection bundled with your webserver (with Apache you can use
|
||||
:term:`.htaccess` files, for example). If other people have telnet access to your
|
||||
server, you should use phpMyAdmin's :abbr:`HTTP (HyperText Transfer
|
||||
Protocol)` or cookie authentication features. Suggestions:
|
||||
This depends on your system. If you're running a server which cannot be
|
||||
accessed by other people, it's sufficient to use the directory protection
|
||||
bundled with your webserver (with Apache you can use :term:`.htaccess` files,
|
||||
for example). If other people have telnet access to your server, you should use
|
||||
phpMyAdmin's :term:`HTTP` or cookie authentication features.
|
||||
|
||||
Suggestions:
|
||||
|
||||
* Your :file:`config.inc.php` file should be ``chmod 660``.
|
||||
* All your phpMyAdmin files should be chown -R phpmy.apache, where phpmy
|
||||
@ -1044,7 +1037,7 @@ normal operation of phpMyAdmin.
|
||||
|
||||
.. _faq4_4:
|
||||
|
||||
4.4 phpMyAdmin always gives "Access denied" when using :abbr:`HTTP (HyperText Transfer Protocol)` authentication.
|
||||
4.4 phpMyAdmin always gives "Access denied" when using :term:`HTTP` authentication.
|
||||
-----------------------------------------------------------------------------------------------------------------
|
||||
|
||||
This could happen for several reasons:
|
||||
@ -1080,7 +1073,7 @@ just add those updated lines into the
|
||||
|
||||
If you want a pre-made sample, you can try this fragment. It stops the
|
||||
'root' user from logging in from any networks other than the private
|
||||
network :abbr:`IP (Internet Protocol)` blocks.
|
||||
network :term:`IP` blocks.
|
||||
|
||||
.. code-block:: php
|
||||
|
||||
@ -1100,11 +1093,10 @@ network :abbr:`IP (Internet Protocol)` blocks.
|
||||
4.7 Authentication window is displayed more than once, why?
|
||||
-----------------------------------------------------------
|
||||
|
||||
This happens if you are using a :abbr:`URL (Uniform Resource Locator)`
|
||||
to start phpMyAdmin which is different than the one set in your
|
||||
:config:option:`$cfg['PmaAbsoluteUri']`. For
|
||||
example, a missing "www", or entering with an :abbr:`IP (Internet
|
||||
Protocol)` address while a domain name is defined in the config file.
|
||||
This happens if you are using a :term:`URL` to start phpMyAdmin which is
|
||||
different than the one set in your :config:option:`$cfg['PmaAbsoluteUri']`. For
|
||||
example, a missing "www", or entering with an :term:`IP` address while a domain
|
||||
name is defined in the config file.
|
||||
|
||||
.. _faq4_8:
|
||||
|
||||
@ -1175,12 +1167,10 @@ Upgrade to at least Internet Explorer 5.5 SP2.
|
||||
5.6 In Internet Explorer 5.0, 5.5 or 6.0, I get an error (like "Page not found") when trying to modify a row in a table with many columns, or with a text column
|
||||
----------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Your table neither have a primary key nor an unique one, so we must
|
||||
use a long :abbr:`URL (Uniform Resource Locator)` to identify this
|
||||
row. There is a limit on the length of the :abbr:`URL (Uniform
|
||||
Resource Locator)` in those browsers, and this not happen in Netscape,
|
||||
for example. The workaround is to create a primary or unique key, or
|
||||
use another browser.
|
||||
Your table neither have a primary key nor an unique one, so we must use a long
|
||||
:term:`URL` to identify this row. There is a limit on the length of the
|
||||
:term:`URL` in those browsers, and this not happen in Netscape, for example.
|
||||
The workaround is to create a primary or unique key, or use another browser.
|
||||
|
||||
.. _faq5_7:
|
||||
|
||||
@ -1200,7 +1190,7 @@ Mozilla versions.
|
||||
|
||||
.. _faq5_9:
|
||||
|
||||
5.9 With Mozilla 0.9.? to 1.0 and Netscape 7.0-PR1 I can't type a whitespace in the :abbr:`SQL (structured query language)`-Query edit area: the page scrolls down.
|
||||
5.9 With Mozilla 0.9.? to 1.0 and Netscape 7.0-PR1 I can't type a whitespace in the :term:`SQL`-Query edit area: the page scrolls down.
|
||||
-------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
This is a Mozilla bug (see bug #26882 at `BugZilla
|
||||
@ -1208,7 +1198,7 @@ This is a Mozilla bug (see bug #26882 at `BugZilla
|
||||
|
||||
.. _faq5_10:
|
||||
|
||||
5.10 With Netscape 4.75 I get empty rows between each row of data in a :abbr:`CSV (comma separated values)` exported file.
|
||||
5.10 With Netscape 4.75 I get empty rows between each row of data in a :term:`CSV` exported file.
|
||||
--------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
This is a known Netscape 4.75 bug: it adds some line feeds when
|
||||
@ -1227,16 +1217,15 @@ by the recent versions of the most browsers.
|
||||
|
||||
.. _faq5_12:
|
||||
|
||||
5.12 :abbr:`Mac (Apple Macintosh)` :abbr:`OS (operating system)` X: Safari browser changes special characters to "?".
|
||||
5.12 :term:`Mac OS X`: Safari browser changes special characters to "?".
|
||||
---------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
This issue has been reported by a :abbr:`OS (operating system)` X
|
||||
user, who adds that Chimera, Netscape and Mozilla do not have this
|
||||
problem.
|
||||
This issue has been reported by a :term:`Mac OS X` user, who adds that Chimera,
|
||||
Netscape and Mozilla do not have this problem.
|
||||
|
||||
.. _faq5_13:
|
||||
|
||||
5.13 With Internet Explorer 5.5 or 6, and :abbr:`HTTP (HyperText Transfer Protocol)` authentication type, I cannot manage two servers: I log in to the first one, then the other one, but if I switch back to the first, I have to log in on each operation.
|
||||
5.13 With Internet Explorer 5.5 or 6, and :term:`HTTP` authentication type, I cannot manage two servers: I log in to the first one, then the other one, but if I switch back to the first, I have to log in on each operation.
|
||||
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
This is a bug in Internet Explorer, other browsers do not behave this
|
||||
@ -1264,13 +1253,12 @@ Please upgrade to at least version 1.2.3.
|
||||
Please check the following points:
|
||||
|
||||
* Maybe you have defined your :config:option:`$cfg['PmaAbsoluteUri']` setting in
|
||||
:file:`config.inc.php` to an :abbr:`IP (Internet Protocol)` address and
|
||||
you are starting phpMyAdmin with a :abbr:`URL (Uniform Resource
|
||||
Locator)` containing a domain name, or the reverse situation.
|
||||
:file:`config.inc.php` to an :term:`IP` address and you are starting phpMyAdmin
|
||||
with a :term:`URL` containing a domain name, or the reverse situation.
|
||||
* Security settings in IE and/or Microsoft Security Center are too high,
|
||||
thus blocking scripts execution.
|
||||
* The Windows Firewall is blocking Apache and MySQL. You must allow
|
||||
:abbr:`HTTP (HyperText Transfer Protocol)` ports (80 or 443) and MySQL
|
||||
:term:`HTTP` ports (80 or 443) and MySQL
|
||||
port (usually 3306) in the "in" and "out" directions.
|
||||
|
||||
.. _faq5_17:
|
||||
@ -1307,10 +1295,10 @@ Using phpMyAdmin
|
||||
|
||||
.. _faq6_1:
|
||||
|
||||
6.1 I can't insert new rows into a table / I can't create a table - MySQL brings up a :abbr:`SQL (structured query language)`-error.
|
||||
6.1 I can't insert new rows into a table / I can't create a table - MySQL brings up a :term:`SQL`-error.
|
||||
------------------------------------------------------------------------------------------------------------------------------------
|
||||
|
||||
Examine the :abbr:`SQL (structured query language)` error with care.
|
||||
Examine the :term:`SQL` error with care.
|
||||
Often the problem is caused by specifying a wrong column-type. Common
|
||||
errors include:
|
||||
|
||||
@ -1348,13 +1336,12 @@ literal NULL in the column, and not a NULL value (this works in PHP4).
|
||||
|
||||
Click on a database or table name in the navigation panel, the properties will
|
||||
be displayed. Then on the menu, click "Export", you can dump the structure, the
|
||||
data, or both. This will generate standard :abbr:`SQL (structured query
|
||||
language)` statements that can be used to recreate your database/table. You
|
||||
will need to choose "Save as file", so that phpMyAdmin can transmit the
|
||||
resulting dump to your station. Depending on your PHP configuration, you will
|
||||
see options to compress the dump. See also the
|
||||
:config:option:`$cfg['ExecTimeLimit']` configuration variable. For additional
|
||||
help on this subject, look for the word "dump" in this document.
|
||||
data, or both. This will generate standard :term:`SQL` statements that can be
|
||||
used to recreate your database/table. You will need to choose "Save as file",
|
||||
so that phpMyAdmin can transmit the resulting dump to your station. Depending
|
||||
on your PHP configuration, you will see options to compress the dump. See also
|
||||
the :config:option:`$cfg['ExecTimeLimit']` configuration variable. For
|
||||
additional help on this subject, look for the word "dump" in this document.
|
||||
|
||||
.. _faq6_5:
|
||||
|
||||
@ -1363,7 +1350,7 @@ help on this subject, look for the word "dump" in this document.
|
||||
|
||||
Click on a database name in the navigation panel, the properties will
|
||||
be displayed. Select "Import" from the list of tabs in the right–hand
|
||||
frame (or ":abbr:`SQL (structured query language)`" if your phpMyAdmin
|
||||
frame (or ":term:`SQL`" if your phpMyAdmin
|
||||
version is previous to 2.7.0). In the "Location of the text file"
|
||||
section, type in the path to your dump filename, or use the Browse
|
||||
button. Then click Go. With version 2.7.0, the import engine has been
|
||||
@ -1448,7 +1435,7 @@ enables: drop-down list of possible values.
|
||||
|
||||
.. _faqpdf:
|
||||
|
||||
6.8 How can I produce a :abbr:`PDF (Portable Document Format)` schema of my database?
|
||||
6.8 How can I produce a :term:`PDF` schema of my database?
|
||||
-------------------------------------------------------------------------------------
|
||||
|
||||
First the configuration variables "relation", "table\_coords" and
|
||||
@ -1457,9 +1444,9 @@ schema layout. Which tables will go on which pages?
|
||||
|
||||
* Select your database in the navigation panel.
|
||||
* Choose "Operations" in the navigation bar at the top.
|
||||
* Choose "Edit :abbr:`PDF (Portable Document Format)` Pages" near the
|
||||
* Choose "Edit :term:`PDF` Pages" near the
|
||||
bottom of the page.
|
||||
* Enter a name for the first :abbr:`PDF (Portable Document Format)` page
|
||||
* Enter a name for the first :term:`PDF` page
|
||||
and click Go. If you like, you can use the "automatic layout," which
|
||||
will put all your linked tables onto the new page.
|
||||
* Select the name of the new page (making sure the Edit radio button is
|
||||
@ -1469,14 +1456,13 @@ schema layout. Which tables will go on which pages?
|
||||
fit the page. When initially placing tables on the page, just pick any
|
||||
coordinates -- say, 50x50. After clicking Save, you can then use the
|
||||
:ref:`wysiwyg` to position the element correctly.
|
||||
* When you'd like to look at your :abbr:`PDF (Portable Document
|
||||
Format)`, first be sure to click the Save button beneath the list of
|
||||
tables and coordinates, to save any changes you made there. Then
|
||||
scroll all the way down, select the :abbr:`PDF (Portable Document
|
||||
Format)` options you want, and click Go.
|
||||
* When you'd like to look at your :term:`PDF`, first be sure to click the Save
|
||||
button beneath the list of tables and coordinates, to save any changes you
|
||||
made there. Then scroll all the way down, select the :term:`PDF` options you
|
||||
want, and click Go.
|
||||
* Internet Explorer for Windows may suggest an incorrect filename when
|
||||
you try to save a generated :abbr:`PDF (Portable Document Format)`.
|
||||
When saving a generated :abbr:`PDF (Portable Document Format)`, be
|
||||
you try to save a generated :term:`PDF`.
|
||||
When saving a generated :term:`PDF`, be
|
||||
sure that the filename ends in ".pdf", for example "schema.pdf".
|
||||
Browsers on other operating systems, and other browsers on Windows, do
|
||||
not have this problem.
|
||||
@ -1526,8 +1512,8 @@ It means "average".
|
||||
* "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 :abbr:`SQL (structured query
|
||||
language)` comments (*/\* xxx \*/*).
|
||||
types set in the pmadb in the dump as :term:`SQL` comments
|
||||
(*/\* xxx \*/*).
|
||||
|
||||
**Data:**
|
||||
|
||||
@ -1555,7 +1541,7 @@ work with it, nor delete it.
|
||||
|
||||
.. _faqsqlvalidator:
|
||||
|
||||
6.14 How do I set up the :abbr:`SQL (structured query language)` Validator?
|
||||
6.14 How do I set up the :term:`SQL` Validator?
|
||||
---------------------------------------------------------------------------
|
||||
|
||||
To use SQL Validator, you need PHP with :term:`XML`, :term:`PCRE` and
|
||||
@ -1566,12 +1552,10 @@ To install :term:`PEAR` :term:`SOAP` module, run :command:`pear install
|
||||
Net_Socket Net_URL HTTP_Request Mail_Mime Net_DIME SOAP` to get the necessary
|
||||
:term:`PEAR` modules for usage.
|
||||
|
||||
If you use the Validator, you should be aware that any :abbr:`SQL
|
||||
(structured query language)` statement you submit will be stored
|
||||
anonymously (database/table/column names, strings, numbers replaced
|
||||
with generic values). The Mimer :abbr:`SQL (structured query
|
||||
language)` Validator itself, is © 2001 Upright Database Technology. We
|
||||
utilize it as free SOAP service.
|
||||
If you use the Validator, you should be aware that any :term:`SQL` statement
|
||||
you submit will be stored anonymously (database/table/column names, strings,
|
||||
numbers replaced with generic values). The Mimer :term:`SQL` Validator itself,
|
||||
is © 2001 Upright Database Technology. We utilize it as free SOAP service.
|
||||
|
||||
.. _faq6_15:
|
||||
|
||||
@ -1730,7 +1714,7 @@ public bookmark, it will be executed.
|
||||
6.23 Export: I heard phpMyAdmin can export Microsoft Excel files?
|
||||
-----------------------------------------------------------------
|
||||
|
||||
You can use :abbr:`CSV (comma separated values)` for Microsoft Excel,
|
||||
You can use :term:`CSV` for Microsoft Excel,
|
||||
which works out of the box. Since phpMyAdmin 3.4.5 support for direct
|
||||
export to Microsoft Excel version 97 and newer was dropped.
|
||||
|
||||
|
||||
@ -12,6 +12,9 @@ From Wikipedia, the free encyclopedia
|
||||
|
||||
.. seealso:: <http://www.wikipedia.org/wiki/.htaccess>
|
||||
|
||||
ACL
|
||||
Access Contol List
|
||||
|
||||
Blowfish
|
||||
a keyed, symmetric block cipher, designed in 1993 by Bruce Schneier.
|
||||
|
||||
@ -94,7 +97,7 @@ From Wikipedia, the free encyclopedia
|
||||
.. seealso:: <http://www.wikipedia.org/wiki/Foreign_key>
|
||||
|
||||
FPDF
|
||||
the free PDF library
|
||||
the free :term:`PDF` library
|
||||
|
||||
.. seealso:: <http://www.fpdf.org/>
|
||||
|
||||
@ -128,10 +131,13 @@ From Wikipedia, the free encyclopedia
|
||||
.. seealso:: <http://www.wikipedia.org/wiki/HyperText_Transfer_Protocol>
|
||||
|
||||
https
|
||||
a :abbr:`HTTP (HyperText Transfer Protocol)`-connection with additional security measures.
|
||||
a :term:`HTTP`-connection with additional security measures.
|
||||
|
||||
.. seealso:: <http://www.wikipedia.org/wiki/Https:_URI_scheme>
|
||||
|
||||
IEC
|
||||
International Electrotechnical Commission
|
||||
|
||||
IIS
|
||||
Internet Information Services is a set of Internet-based services for
|
||||
servers using Microsoft Windows.
|
||||
@ -166,6 +172,9 @@ From Wikipedia, the free encyclopedia
|
||||
|
||||
.. seealso:: <http://www.wikipedia.org/wiki/ISP>
|
||||
|
||||
ISO
|
||||
International Standards Organisation
|
||||
|
||||
JPEG
|
||||
a most commonly used standard method of lossy compression for photographic images.
|
||||
|
||||
|
||||
@ -21,15 +21,12 @@ Currently phpMyAdmin can:
|
||||
indexes
|
||||
* maintenance server, databases and tables, with proposals on server
|
||||
configuration
|
||||
* execute, edit and bookmark any :abbr:`SQL (structured query
|
||||
language)`-statement, even batch-queries
|
||||
* execute, edit and bookmark any :term:`SQL`-statement, even batch-queries
|
||||
* load text files into tables
|
||||
* create [#f1]_ and read dumps of tables
|
||||
* export [#f1]_ data to various formats: :term:`CSV`,
|
||||
:term:`XML`, :term:`PDF`, :abbr:`ISO (International Standards
|
||||
Organisation)`/:abbr:`IEC (International Electrotechnical Commission)`
|
||||
26300 - OpenDocument Text and Spreadsheet, :abbr:`Word (Microsoft Word
|
||||
2000)`, and LATEX formats
|
||||
* export [#f1]_ data to various formats: :term:`CSV`, :term:`XML`, :term:`PDF`,
|
||||
:term:`ISO`/:term:`IEC` 26300 - OpenDocument Text and Spreadsheet, Microsoft
|
||||
Word 2000, and LATEX formats
|
||||
* import data and :term:`MySQL` structures from :term:`OpenDocument` spreadsheets, as
|
||||
well as :term:`XML`, :term:`CSV`, and :term:`SQL` files
|
||||
* administer multiple servers
|
||||
@ -37,7 +34,7 @@ Currently phpMyAdmin can:
|
||||
* check referential integrity in MyISAM tables
|
||||
* using Query-by-example (QBE), create complex queries automatically
|
||||
connecting required tables
|
||||
* create :abbr:`PDF (Portable Document Format)` graphics of your
|
||||
* create :term:`PDF` graphics of your
|
||||
Database layout
|
||||
* search globally in a database or a subset of it
|
||||
* transform stored data into any format using a set of predefined
|
||||
|
||||
@ -10,13 +10,11 @@ page can be used for this.
|
||||
|
||||
.. warning::
|
||||
|
||||
:abbr:`Mac (Apple Macintosh)` users should note that if you are on a
|
||||
:abbr:`Mac (Apple Macintosh)` :abbr:`OS (operating system)` version before
|
||||
:abbr:`OS (operating system)` X, StuffIt unstuffs with :abbr:`Mac (Apple
|
||||
Macintosh)` formats. So you'll have to resave as in BBEdit to Unix style
|
||||
ALL phpMyAdmin scripts before uploading them to your server, as PHP seems
|
||||
not to like :abbr:`Mac (Apple Macintosh)`-style end of lines character
|
||||
("``\r``").
|
||||
:term:`Mac` users should note that if you are on a version before
|
||||
:term:`Mac OS X`, StuffIt unstuffs with :term:`Mac` formats. So you'll have
|
||||
to resave as in BBEdit to Unix style ALL phpMyAdmin scripts before
|
||||
uploading them to your server, as PHP seems not to like :term:`Mac`-style
|
||||
end of lines character ("``\r``").
|
||||
|
||||
.. _quick_install:
|
||||
|
||||
@ -153,7 +151,7 @@ options which the setup script does not provide.
|
||||
for additional information, especially :ref:`faq4_4`.
|
||||
#. Open the `main phpMyAdmin directory <index.php>`_ in your browser.
|
||||
phpMyAdmin should now display a welcome screen and your databases, or
|
||||
a login dialog if using :abbr:`HTTP (HyperText Transfer Protocol)` or
|
||||
a login dialog if using :term:`HTTP` or
|
||||
cookie authentication mode.
|
||||
#. You should deny access to the ``./libraries`` and ``./setup/lib``
|
||||
subfolders in your webserver configuration. For Apache you can use
|
||||
@ -177,14 +175,12 @@ options which the setup script does not provide.
|
||||
phpMyAdmin configuration storage
|
||||
++++++++++++++++++++++++++++++++
|
||||
|
||||
For a whole set of new features (bookmarks, comments, :abbr:`SQL
|
||||
(structured query language)`-history, tracking mechanism, :abbr:`PDF
|
||||
(Portable Document Format)`-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 controluser, so no other user should have rights to
|
||||
it).
|
||||
For a whole set of new features (bookmarks, comments, :term:`SQL`-history,
|
||||
tracking mechanism, :term:`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 controluser, so no other user
|
||||
should have rights to it).
|
||||
|
||||
Please look at your ``./examples/`` directory, where you should find a
|
||||
file called *create\_tables.sql*. (If you are using a Windows server,
|
||||
@ -222,10 +218,9 @@ You should **not** copy :file:`libraries/config.default.php` over
|
||||
:file:`config.inc.php` because the default configuration file is version-
|
||||
specific.
|
||||
|
||||
If you have upgraded your MySQL server from a version previous to
|
||||
4.1.2 to version 5.x or newer and if you use the phpMyAdmin
|
||||
configuration storage, you should run the :abbr:`SQL (structured query
|
||||
language)` script found in
|
||||
If you have upgraded your MySQL server from a version previous to 4.1.2 to
|
||||
version 5.x or newer and if you use the phpMyAdmin configuration storage, you
|
||||
should run the :term:`SQL` script found in
|
||||
:file:`examples/upgrade_tables_mysql_4_1_2+.sql`.
|
||||
|
||||
.. index:: Authentication mode
|
||||
@ -235,16 +230,15 @@ language)` script found in
|
||||
Using authentication modes
|
||||
++++++++++++++++++++++++++
|
||||
|
||||
:abbr:`HTTP (HyperText Transfer Protocol)` and cookie authentication
|
||||
modes are recommended in a **multi-user environment** where you want
|
||||
to give users access to their own database and don't want them to play
|
||||
around with others. Nevertheless be aware that MS Internet Explorer
|
||||
seems to be really buggy about cookies, at least till version 6. Even
|
||||
in a **single-user environment**, you might prefer to use :abbr:`HTTP
|
||||
(HyperText Transfer Protocol)` or cookie mode so that your
|
||||
user/password pair are not in clear in the configuration file.
|
||||
:term:`HTTP` and cookie authentication modes are recommended in a **multi-user
|
||||
environment** where you want to give users access to their own database and
|
||||
don't want them to play around with others. Nevertheless be aware that MS
|
||||
Internet Explorer seems to be really buggy about cookies, at least till version
|
||||
6. Even in a **single-user environment**, you might prefer to use :term:`HTTP`
|
||||
or cookie mode so that your user/password pair are not in clear in the
|
||||
configuration file.
|
||||
|
||||
:abbr:`HTTP (HyperText Transfer Protocol)` and cookie authentication
|
||||
:term:`HTTP` and cookie authentication
|
||||
modes are more secure: the MySQL login information does not need to be
|
||||
set in the phpMyAdmin configuration file (except possibly for the
|
||||
:config:option:`$cfg['Servers'][$i]['controluser']`).
|
||||
@ -257,22 +251,18 @@ stored, encrypted with the blowfish algorithm, in a temporary cookie.
|
||||
This section is only applicable if your MySQL server is running
|
||||
with ``--skip-show-database``.
|
||||
|
||||
For ':abbr:`HTTP (HyperText Transfer
|
||||
Protocol)`' and 'cookie' modes, phpMyAdmin needs a controluser that
|
||||
has **only** the ``SELECT`` privilege on the *`mysql`.`user` (all
|
||||
columns except `Password`)*, *`mysql`.`db` (all columns)*,
|
||||
*`mysql`.`host` (all columns)* and *`mysql`.`tables\_priv` (all
|
||||
columns except `Grantor` and `Timestamp`)* tables. You must specify
|
||||
the details for the controluser in the :file:`config.inc.php` file under the
|
||||
:config:option:`$cfg['Servers'][$i]['controluser']` and
|
||||
:config:option:`$cfg['Servers'][$i]['controlpass']`
|
||||
settings. The following example assumes you want to use ``pma`` as the
|
||||
controluser and ``pmapass`` as the controlpass, but **this is only an
|
||||
example: use something else in your file!** Input these statements
|
||||
from the phpMyAdmin :abbr:`SQL (structured query language)` Query
|
||||
window or mysql command–line client. Of course you have to replace
|
||||
``localhost`` with the webserver's host if it's not the same as the
|
||||
MySQL server's one.
|
||||
For ':term:`HTTP`' and 'cookie' modes, phpMyAdmin needs a controluser that has
|
||||
**only** the ``SELECT`` privilege on the *`mysql`.`user` (all columns except
|
||||
`Password`)*, *`mysql`.`db` (all columns)*, *`mysql`.`host` (all columns)* and
|
||||
*`mysql`.`tables\_priv` (all columns except `Grantor` and `Timestamp`)* tables.
|
||||
You must specify the details for the controluser in the :file:`config.inc.php`
|
||||
file under the :config:option:`$cfg['Servers'][$i]['controluser']` and
|
||||
:config:option:`$cfg['Servers'][$i]['controlpass']` settings. The following
|
||||
example assumes you want to use ``pma`` as the controluser and ``pmapass`` as
|
||||
the controlpass, but **this is only an example: use something else in your
|
||||
file!** Input these statements from the phpMyAdmin :term:`SQL` Query window or
|
||||
mysql command–line client. Of course you have to replace ``localhost`` with the
|
||||
webserver's host if it's not the same as the MySQL server's one.
|
||||
|
||||
If you want to use the many new relation and bookmark features: (this of
|
||||
course requires that your :ref:`linked-tables` be set up).
|
||||
@ -322,15 +312,13 @@ user/password fields inside the :config:option:`$cfg['Servers']`.
|
||||
HTTP authentication mode
|
||||
------------------------
|
||||
|
||||
* Uses :abbr:`HTTP (HyperText Transfer Protocol)` Basic authentication
|
||||
* Uses :term:`HTTP` Basic authentication
|
||||
method and allows you to log in as any valid MySQL user.
|
||||
* Is supported with most PHP configurations. For :abbr:`IIS (Internet
|
||||
Information Services)` (:abbr:`ISAPI (Internet Server Application
|
||||
Programming Interface)`) support using :abbr:`CGI (Common Gateway
|
||||
Interface)` PHP see :ref:`faq1_32`, for using with Apache :abbr:`CGI
|
||||
(Common Gateway Interface)` see :ref:`faq1_35`.
|
||||
* Is supported with most PHP configurations. For :term:`IIS` (:term:`ISAPI`)
|
||||
support using :term:`CGI` PHP see :ref:`faq1_32`, for using with Apache
|
||||
:term:`CGI` see :ref:`faq1_35`.
|
||||
* See also :ref:`faq4_4` about not using the :term:`.htaccess` mechanism along with
|
||||
':abbr:`HTTP (HyperText Transfer Protocol)`' authentication mode.
|
||||
':term:`HTTP`' authentication mode.
|
||||
|
||||
.. index:: pair: Cookie; Authentication mode
|
||||
|
||||
@ -339,9 +327,8 @@ HTTP authentication mode
|
||||
Cookie authentication mode
|
||||
--------------------------
|
||||
|
||||
* You can use this method as a replacement for the :abbr:`HTTP
|
||||
(HyperText Transfer Protocol)` authentication (for example, if you're
|
||||
running :abbr:`IIS (Internet Information Services)`).
|
||||
* You can use this method as a replacement for the :term:`HTTP` authentication
|
||||
(for example, if you're running :term:`IIS`).
|
||||
* Obviously, the user must enable cookies in the browser, but this is
|
||||
now a requirement for all authentication modes.
|
||||
* With this mode, the user can truly log out of phpMyAdmin and log in
|
||||
|
||||
Loading…
Reference in New Issue
Block a user
