Closed GoogleCodeExporter closed 8 years ago
as an extra info, with the mysqldump , i use this options:
-Q -R -K --add-drop-database --add-drop-table --complete-insert
--create-options --add-locks
Original comment by dtri...@gmail.com
on 20 Nov 2012 at 4:26
Great. What's the error?
Original comment by shlomi.n...@gmail.com
on 20 Nov 2012 at 4:39
The backup gives an error. Tomorrow i'll show you the error.
Original comment by dtri...@gmail.com
on 20 Nov 2012 at 6:42
You say the backup gives the error, yet you say HeidiSQL provides same error:
HeidiSQL is not a backup tool.
Does the mysqldump provide the error, or does the import provide the error?
Original comment by shlomi.n...@gmail.com
on 20 Nov 2012 at 7:09
I mean, i load the .sql in Heidi, but i got the same error.
tomorrow at office i will give you more details!
Original comment by dtri...@gmail.com
on 20 Nov 2012 at 10:17
Cool, thank you :)
Original comment by shlomi.n...@gmail.com
on 21 Nov 2012 at 5:16
Here you have the sql file created with mysqldump.
Maybe it's the way i created what it's giving the error!
Original comment by dtri...@gmail.com
on 21 Nov 2012 at 7:23
Attachments:
The error!
I can attach the bat files I created to make the backup, and the restore!
Original comment by dtri...@gmail.com
on 21 Nov 2012 at 7:34
Attachments:
Something in your export went wrong:
in line 7752, see:
end; */;;
I don;t know how the ";" got to be there. It should read:
end */;;
I've tested with 5.1 and 5.5 dumps on my machine: nothing of the sort. I have
no idea why your export went like that.
At any case, this is not a common_schema bug.
Original comment by shlomi.n...@gmail.com
on 21 Nov 2012 at 8:05
Yes, that's the same i though, but i have to tell you.
I sometimes have problems with mysqldump and routines! Maybe it's
mysqldump.exe, that need to be "updated" for this issues!
Keep on touch!
Original comment by dtri...@gmail.com
on 21 Nov 2012 at 8:23
Original issue reported on code.google.com by
dtri...@gmail.com
on 20 Nov 2012 at 4:25