For example, a server may have more than one
name, or we may be trying to use the IP address instead of the name.
Column Size Changed by phpMyAdmin
MySQL itself sometimes decides to change the column type and size, for a more
efficient column definition. This happens mostly with CHAR and VARCHAR.
Seeing Many Databases that Are Not Ours
This problem occurs mostly after an upgrade to MySQL 4. The automatic server
upgrade procedure gives the global privileges CREATE TEMPORARY TABLES,
SHOW DATABASES, and LOCK TABLES to all users. These privileges also enable
users to see the names of all the databases (but not their tables) until we upgrade
the grant tables, as described in the MySQL manual. If the users do not need these
privileges, we can revoke them, and they will only see the databases to which they
are entitled.
Not Being Able to Store a Value Greater Than 127
This is normal if we have defined a column of type TINYINT, since 127 is the
maximum value for this column type. Similar problems may arise with other numeric
column types. Changing the type to INT, expands the available range of values.
Troubleshooting and Support
[ 304 ]
Seeking Support
The starting point for support is the home page http://www.phpmyadmin.net,
which has sections about documentation and support (feedback). There you will find
links to the discussion forums, and to various trackers such as:
Bugs tracker
Feature requests tracker
Translations tracker
Patches tracker
Support tracker
FAQs
The Documentation.
Pages:
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276