As we only have
two (small) tables, we select them both.
As the search will be done on each row of every table selected, we might
hit some time limits if the number of rows or tables is too big. Thus, this
feature can be deactivated by setting $cfg['UseDbSearch'] to FALSE.
(It is set to TRUE by default).
Clicking Go finds the following for us:
Searching Data
[ 160 ]
This is an overview of the number of matches and the relevant tables. We might get
some matches in tables in which we are not interested. However, for the matches that
look promising, we can Browse the results page, or we can Delete the unwanted rows.
Summary
In this chapter, we have covered single-table searches with query by example criteria
and additional criteria specification, selecting displayed values, and ordering results.
We also took a look at wildcard searches and full database search.
Table and Database
Operations
In the previous chapters, we dealt mostly with table fields. In this chapter, we
will learn how to perform some operations that influence tables or databases as a
whole. We will cover table attributes and how to modify them, and also discuss
multi-table operations.
Various links that enable table operations have been put together on one sub-page of
the Table view: Operations. Here is an overview of this sub-page:
Table and Database Operations
[ 162 ]
Table Maintenance
During the lifetime of a table, it repeatedly gets modified, and so grows and shrinks.
Pages:
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162