Databases Reference
In-Depth Information
Internally, phpMyAdmin can call the
information_schema
, instead of the
corresponding
SHOW
statements to retrieve metadata. This behavior is controlled
by the
$cfg['Servers'][$i]['DisableIS']
directive. Some
SELECT
operations
involving a
WHERE
clause on
information_schema
are really slow (many minutes of
wait time) when the server hosts hundreds of databases or tables, and this is yet to
be fixed by the MySQL team; this is why this directive is set to
true
by default, thus
avoiding the use of
information_schema
.
The
$cfg['Servers'][$i]['hide_db']
parameter can be used to hide this
"database" to users who might be confused by the sudden appearance of a database
that they know nothing about. It will probably depend on their level of expertise in
MySQL. On a multi-user installation of phpMyAdmin, we cannot please everyone
about this parameter's value.
Partitioning
User-defined partitioning (refer to
http://dev.mysql.com/doc/refman/5.1/en/
partitioning.html
) is offered in MySQL 5.1. It allows us to "distribute portions of
individual tables across a file system according to rules which you can set largely
as needed". Using this feature in phpMyAdmin requires knowledge of its syntax as
there are many partition types. Also, for each partition type, the number of partitions
and the values associated with each partition are too random to be easily represented
on a web interface.
Creating a table with partitions
Let us try it by creating a table named
test
with one column
id
. On the table
creation panel, if connected to a MySQL 5.1 server, phpMyAdmin shows a
PARTITION definition
dialog, as shown in the following screenshot:
Search WWH ::
Custom Search