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.
Goal of the Infrastructure
These metadata tables contain, for all storage engines, information to support the
special phpMyAdmin's features like bookmarks and transformations. Moreover, for
non-InnoDB tables, relations between tables are kept in this infrastructure.
???
???
Chapter 11
[ 173 ]
Location of the Infrastructure
There are two possible places to store these tables:
In a user's database.
Pages:
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171