$mysqldump not defined
ryan_courtnage - September 2, 2008 - 20:16
| Project: | Database Scripts |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | ceardach |
| Status: | closed |
Jump to:
Description
several functions run mysql dump with a command like:
exec("$mysqldump $dump_options $db_connection_settings $filter > $file_path/$dump_file");
However, $mysqldump is not defined anywhere. I assume that this should be defined in config.inc.
#1
If you have updated dbscripts from an earlier version, you may not have updated your customized config.inc file.
Ensure that you have these lines, and they are pointing to the appropriate locations:
// Location of mysql binaries (needs to be set if not in your path)
$mysql = 'mysql';
$mysqldump = 'mysqldump';
// Charset location
$charsets = '/usr/mysql/share/mysql/charsets';
If the binaries are not in your path, you will have to list their entire path, ie: $mysqldump = '/usr/local/mysql/bin/mysqldump'
If this is a new install of dbscripts, ensure that you have copied config.inc.example to config.inc
#2
It's a new install. config.inc.example is missing the $mysqldump var. I downloaded the tarball.
#3
Huh. This is the second time what I've committed hasn't gone through entirely. I'll look into it.
#4
Thanks.
Incidentally, I noticed that the README is also not updated to reflect the new script names, etc.
#5
Seriously? Damn. Ok, I need to go over my commit-to-drupal workflow because I know I meticulously went over all the documentation.
temp
Automatically closed -- issue fixed for two weeks with no activity.
#6
Automatically closed -- issue fixed for two weeks with no activity.
#7
This really should be fixed now.