-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR 1064 (42000) at line 1: You have an error in your SQL syntax #18
Comments
This is the code from inside the bash: -c: line 0: syntax error near unexpected token `)' bash: -c: line 0: `mysqldump -h{host} -u{user} -p{password} {database}' |
Dunno if you solved this one, but I had the same trouble locally (OSX running MAMP) The Grunt task wasn't able to use 'mysqldump' because it wasn't in my bash profile. If that's the case...
this is assuming MAMP is in the default location. After adding the path line, save/exit/reset terminal. Now you have access to the command anywhere.. so that should put grunt in a position to execute properly. |
I use the built in apache which is already in my bash profile. Haven't solved this yet. |
Hrm, does it get as far as generating a .sql file in your backup folder? If so, what does that file contain? |
I get the following error in terminal
The local backup contains a full SQL dump but the remote backup contains
Where {host} {user} {password} and {database} are sensitive data. |
my pull command output looks like this: Pulling database from 'staging' into Local
Operations completed Done, without errors. What I notice different is yours has a line about 'Warning: Using a password on the command line..." then it throws an error. Can you try suppressing that warning? Maybe that's interfering with the rest of execution. Just a theory. |
How do I suppress it? Is #12 related? |
Suppressing it, here's some info on that: |
See #6 |
When I run the task I get the following error:
Not sure if this is due to my system configuration or the plugin.
The error appears in the the staging .sql dumps but the grunt task says everything completes successfully. So it fails silently unless you add the flags
--verbose --debug
when calling the command.The local db dump file shows correct SQL information.
The text was updated successfully, but these errors were encountered: