MySQL Bugs: #39086: forward and synchronise my model

Bug #39086	forward and synchronise my model
Submitted:	28 Aug 2008 8:59	Modified:	12 Oct 2008 11:32
Reporter:	servian frederic	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.0.24	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	forward and synchronise my model

Description:
i work with mysql.
i have two problem, when i try to synchronise  my model or forward it.

First Problem: if i added an index into the model, when i go synchronise with the live database, in the sql code generated, there are an error he miss two small quotes  'nameofindex' " around the name  of index

The seconde problem;
during synchronisation or forwarding my model.

unknown exception caught in c:\documents and settinds\tax\my\documents\visual studio 2005\projects\wb 5.0\workbench\backend\windows\wb.wr\src\wb.h at line 1010

I can not use the software that I just buy.
I lost many many time, with this bugs

How to repeat:
for probleme of index
if i take the sql code, and i try to execute it on sql command, i have an error.
So if i add the quote, the sql query works perfectly

For the second problem 
i don't understand

Suggested fix:
  

wrong sql code
INDEX historique_mouvement_index2922 

right solution
  INDEX 'historique_mouvement_index2922'

bug description

Attachment: erreur sql.JPG (image/jpeg, text), 49.83 KiB.

Thank you for the bug report. Could you please provide the project file attaching it here (private if you want)?. Thanks in advance.

my problem is solved, it came from my pattern.
I imported a scheme DBdesigner 4 and it created a lot of errors. it makes a week that I sought.
I solved the problem of indices. And it has corrected the bug in the application. For against a very annoying bug, if there is an error in the code of creation, the software will crash, and one is forced to restart

thanks for your attention,

Please, check if newer version, 5.0.25, also crashes for you in this situation.

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".