MySQL Bugs: #34619: Couldn't import the create sql file after an export.

Bug #34619	Couldn't import the create sql file after an export.
Submitted:	16 Feb 2008 15:08	Modified:	17 Mar 2008 14:50
Reporter:	Peter Veres	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.0.13 OSS Beta	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
Hi,

I lost my workbench file, because a little hdd damage. I found an sql create file what i maked with workbench an earlier time. I tried to import it but it has a lot of problem at the import. It says syntax problems.

And it says the import successfull but in my products table columns is missing. (I see the columns in the sql!)

How to repeat:
Try to import my sql create file. And see the errors in the ouput log and the missing columns in the tables (for ex. products).

I can fixed by replace (``) with (`id`) but why it is missed?

Thank you for a problem report. Sorry, but I do not see `` in the file uploaded, ad  was able to import this file withoput any obvious problems.

Anyway, I'd need original Workbench file to load and export as SQL to verify this bug.

Ahh. I said i lost the workbench file. I had only the create sql, because it is my last dump. The workbench file couldn't opened by workbench. I don't understand why. Hmm. I upload it. But i think you can't open it / repair too.

Yes, I can not open the file you uploaded. But I need a repeatable test case. For this bug it means normal .mwb file to open and export as .sql that can not be imported then.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".