Databases Reference
In-Depth Information
Not Being Able to Create a Database
No privileges
appears next to the
Create database
dialog on the
Home
page if
phpMyAdmin detects that the account used to log in does not have the permissions
to create a database. This situation occurs frequently on hosted servers where the
system administrator prefers to create one database for each customer.
If we are not on a hosted server, this message simply reflects the fact that we do
not have the global
CREATE
privilege, nor any
CREATE
privilege on a wildcard
database specification.
Problems Importing Large Files or Uploading Large
BLOB Files
Usually, these problems indicate that we have hit a limit during the transfer. Chapter
8 explains these limits and the recommended course of action. As a last resort solution,
we might have to split our large text files. (Search the Internet for
file splitters
.)
MySQL Root Password Lost
The MySQL manual explains the general solution at
http://www.mysql.com/doc/en/Resetting_permissions.html
.
The solution involves stopping the MySQL server, restarting it with the special option,
skip-grant-tables
(that basically starts the server without security). The way to stop
and restart the server depends on the server platform used. Then, we can connect to
the server from phpMyAdmin as a superuser (like root), and any password. The next
step is to change root's password. (See Chapter 17.) Then we can stop the MySQL
server and restart it using normal procedures. (Security will become active again.)
Duplicate Field Names when Creating a Table
Here is a curious symptom: when we try to create a table containing, for example,
one field named
FIELD1
of type
VARCHAR(15)
, it looks like phpMyAdmin has sent
a command to create two identical fields named
FIELD1
. The problem is not caused
by phpMyAdmin, but by the environment. In this case, the Apache web server seems
well configured to run PHP scripts, when in fact, it is not. However, this bug only
appears for some scripts.
Search WWH ::
Custom Search