Databases Reference
In-Depth Information
InnoDB
A new MySQL storage engine
(InnoDB)
became available during phpMyAdmin's
development. The InnoDB sub-system has its own web page at
http://www.innodb.com
.
Since the InnoDB sub-system must be made active by a system administrator, it may
not be available on every MySQL server. Here are the benefits of using the InnoDB
storage engine for a table:
•
It supports referential integrity based on foreign keys, which are the
keys in a foreign (or reference) table. By contrast, using only phpMyAdmin's
internal relations (discussed later) brings no automatic referential
integrity verification.
InnoDB tables exported definitions containing the defined relations, so they
are easily imported back for better cross-server interoperability.
•
InnoDB's foreign key feature can effectively replace (for InnoDB tables only) the
part of phpMyAdmin's infrastructure that deals with relations. We will see how
phpMyAdmin interfaces to the InnoDB foreign key system.
The other parts of phpMyAdmin's infrastructure (for
example, bookmarks) have no equivalent in InnoDB
or MySQL, and thus they are still needed to access
the complete phpMyAdmin feature set. However, in
MySQL 5, views are supported and have similarities with
phpMyAdmin's bookmarks.
Linked-Tables Infrastructure
The relational system's infrastructure is stored in tables that follow a predetermined
structure. The data in these tables is generated and maintained by phpMyAdmin on
the basis of our actions from the interface.
Location of the Infrastructure
There are two possible places to store these tables:
•
In a user's database. Thus every web developer owning a database can
benefit from these features.
Search WWH ::
Custom Search