We can do this from
the Operations sub-page in the Table view. We start by doing this for the author table:
A problem might arise when changing the storage engine of book table to InnoDB.
We have a full-text index in this table, and some versions of MySQL do not support
it for the InnoDB engine. We have to remove the full-text index if we receive the
following error message.
Chapter 11
[ 181 ]
To get rid of this error message, we go back to Structure for the book table and
remove the full-text index on the description field. While we are on this screen,
let's also remove the combined index we created on author_id and language. This
is because we want to see the consequences of a missing index later in this chapter.
At this point, we are able to switch the book table to InnoDB.
The foreign key system in InnoDB maintains integrity between the related tables, so
we cannot add a non-existent author ID to the book table. In addition, actions are
programmable when DELETE or UPDATE operations are performed on the master table
(in our case, book).
Opening the book table and entering the Relation view now displays a different page:
The Relational System
[ 182 ]
This page tells us that:
We have an internal relation defined for author_id to the author table.
We don't yet have any InnoDB relations defined.
We will be able to remove the internal relation, when the same relation has
been defined in InnoDB.
Pages:
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180