-none- 2007-10-05 - By Jesse
Back
> Are you sure that's the exact query and error message? The query has a
> backtick; the error message has none, which is unusual for a purely
> syntactic error. It makes me suspicious that the error is coming from
> something else: maybe a subtly mangled file.
I found the problem. When I ran the MySQL Administrator to start the
restore, I didn't notice that I was connected to another server. In face, I
was connecting to the server from which the backup came from originally, but
from another machine. Once I caught this, and changed it to the local
machine, the restore (and the DROP TRIGGER command) went through fine. It
may simply be that the user I used to connect to the other server didn't
have access rights to do that, I'm not sure, but the error message indicated
a syntactical error (as you noted), not an access error. So, it's a mystery
to me why the message didn't seem to indicate it properly, but I've got it
working now.
Thanks,
Jesse
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=mysql@(protected)
|
|
