| Bug #61135 | Connector MXJ unable to unzip MySQL databases if target directory is not empty | ||
|---|---|---|---|
| Submitted: | 11 May 2011 14:52 | Modified: | 13 Sep 2012 14:19 |
| Reporter: | Aurélien Thieriot | Email Updates: | |
| Status: | Unsupported | Impact on me: | |
| Category: | Connector / MXJ | Severity: | S2 (Serious) |
| Version: | 5.0.11 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[12 May 2011 7:19]
Tonci Grgin
Hi Aurélien and thanks for your report. c/MXJ is a wrapper around c/J that installs, starts and stops MySQL server. I am not sure it was intended for something like this but will check.
[13 Sep 2012 14:19]
Tonci Grgin
We do not support/develop c/MXJ any more.
Description: On first time the users launch the application, the MXJ Connector try to unzip the MySQL database. Unfortunately, when the configured target directory contain an existing database (a personal one wich can be used by our application), MXJ refuse to launch himself. How to repeat: Easy to repeat, take an existing application that use MXJ, paste an existing MySQL database in the ${datadir} directory and try to launch this application. The issue has most be seen on Windows operating systems. Suggested fix: It will be great if we can launch our application with an already deploy database in the skeleton of our installers. In any ways. Ideally in the ${datadir} directory, but if we need to configure a "companion" path, that will be great too.