MySQL Bugs: #21140: Not able to define drivers for other databases

Bug #21140	Not able to define drivers for other databases
Submitted:	19 Jul 2006 9:12	Modified:	19 Jul 2006 10:52
Reporter:	Alf Christophersen	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench Preview	Severity:	S1 (Critical)
Version:	1.0.6 Beta	OS:	Windows (Win XP)
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	Database synchronisation

Description:
I wanted to synchronize my model with a MS SQL 2000 Server (to be used for reverse engineering in BDS 2006 ECO III which today don't support MySQL yet).

First problem was, I had to install jtds-1.0.2.jar which doesn't exist anymore. Only available version today is jtds-1.2.jar. But in order to read it, I had to rename to jtds-1.0.2.jar
When saying ok, I get a message about restart program. (The application needs to be restarted. Please click on [Close] to close the appplication.

After restarting and trying to synchronize the model, the database driver is forgotten.

With some other databases, the possibility to download is even disabled, and hitting the button to define driver just displays the message to restart, and everything is forgotten.

How to repeat:
Start program
Press Database
Press Database synchronisation
Choose MS SQL
Downloaded driver which now isn't 1.0.2 anymore, but 1.2 (The program should not be static about file name giving, otherwise users quickly end up in problems)
Click Locate Driver on Harddisk and choose the renamed jtds-1.2.jar file (renamed to fit)
Accept the file and Press close.

After restart, nothing is stored.

If trying to use Access, the menu for downloading a new driver disappear, and pressing Locate driver on Harddisk just ask for closing down application.

The same happens if trying to use Generic driver

Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicates bug #18061