Arun
9-29-05, 04:22 AM
I get the error quoted below when I tried to import a mysql dumb I collected yesterday from my db (using phpMyAdmin) here. I tried to import it to another db here itself.
I had repaired and optimised all tables in it before exporting this dump from my parent db. Will changing some data export parameters in phpMyadmin export window help resolve this bug? I'm left clueless here.Some help is really appreciated.
(The OPS db backup of yesterday is corrupt so I chose phpMyADmin export - and after I have repaired the table today there has not been any backup taken by OPS)
There is a chance that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if the parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below:
I had repaired and optimised all tables in it before exporting this dump from my parent db. Will changing some data export parameters in phpMyadmin export window help resolve this bug? I'm left clueless here.Some help is really appreciated.
(The OPS db backup of yesterday is corrupt so I chose phpMyADmin export - and after I have repaired the table today there has not been any backup taken by OPS)
There is a chance that you may have found a bug in the SQL parser. Please examine your query closely, and check that the quotes are correct and not mis-matched. Other possible failure causes may be that you are uploading a file with binary outside of a quoted text area. You can also try your query on the MySQL command line interface. The MySQL server error output below, if there is any, may also help you in diagnosing the problem. If you still have problems or if the parser fails where the command line interface succeeds, please reduce your SQL query input to the single query that causes problems, and submit a bug report with the data chunk in the CUT section below: