Entering SQL Commands - Mastering phpMyAdmin 2.8 for Effective MySQL Management - page 179

If we want another tab to be the default active tab, we can replace sql with files or
history . Another value, full , shows the contents of all the three tabs at once.
In the query window, we see a checkbox for the Do not overwrite this query from
outside the window choice. Normally this is not checked, and the changes we make
while navigating generating queries are reflected in the query window. (This is
called synchronization .) For example, choosing a different database or table from
the left or right panel would update the query window accordingly. But if we start
to type a query directly in this window, the checkbox will get checked in order to
protect its contents and remove synchronization. This way, the query composed here
will be locked and protected.
JavaScript-Based SQL History
This feature collects all the successful SQL queries we execute and modifies the
Query window to make them available. If we close the window, they will be lost.
This default type of history is temporary, since $cfg['QueryHistoryDB'] is set to
FALSE by default.
JavaScript-based history works in Opera, Mozilla-based browsers, and Internet
Explorer.
Database-Based SQL History (Permanent)
Since we installed the linked-tables infrastructure (see Chapter 11), a more powerful
history mechanism is available and is triggered by setting $cfg['QueryHistoryDB']
to TRUE .
After we try some queries from the query box (the one located in the query window)
a history is built:
We see (in the reverse order) the last successful queries and the database on which
they were made. Only the queries typed from the query box are kept in this history,
not queries generated by phpMyAdmin itself (for example, by clicking on Browse ).