We
can ascertain the exact impact by examining the query timing that phpMyAdmin
displays on each results page and comparing with or without the index:
However, the difference in time can be minimal if we only have limited test data
compared to a real table in production.
Detection of Index Problems
Since version 2.6.1, phpMyAdmin tries to detect some common index problems. For
example, let's access the book table and add an index on the isbn column. When we
display this table's structure, we get a warning:
Changing Table Structures
[ 114 ]
The intention here is to warn us about an inefficient index structure when
considering the whole table. We don't need to have two indexes on the same column.
We should consider this feature as work in progress.
Summary
In this chapter, we saw how to add fields, including special field types like TEXT,
BLOB, ENUM, and SET, how to use a calendar popup for DATE, DATETIME,
and TIMESTAMP fields, and how to upload binary data into a BLOB field. We
also learned how to manage indexes (multi-field and full-text) and get feedback
from MySQL about which indexes are used in a specific query.
Exporting Structure and Data
Keeping good backups is crucial to a project. Backups consist of up-to-date backups
and intermediary snapshots taken during development and production phases. The
export feature of phpMyAdmin can generate backups and can also be used to send
data to other applications.
Pages:
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124