Data Compare for MySQL - some bugs?

[aasat77]

Data Compare for MySQL it's very good and useful tool for comparing
MySQL schemas. Although we found some problems, below I describe it:

1. When we moving stored procedure to other database (e.g. moving from
dev to production version) new line characters on parameters list are
removed from procedure body.

2. Could you tell us if it's possible to implement(use) interactive mode
for MySQL connection?
We have short timeouts on production enviroment and Data Compare
permanent disconnects from database servers

[Alexz]

Data Compare for MySQL it's very good and useful tool for comparing

Did you mean Schema Compare tool or maybe I missed anything?

1. When we moving stored procedure to other database (e.g. moving from
dev to production version) new line characters on parameters list are
removed from procedure body.

Yeah, we've fixed this bug in the last build of dbForge Studio for MySQL v3.60. So, the fix will be available in the next build of Schema Compare for MySQL.

2. Could you tell us if it's possible to implement(use) interactive mode
for MySQL connection?

We've added your suggestion to in our development plan

[aasat77]

Thank you, I use Schema Comparer

[mscal]

.... We have short timeouts on production enviroment and Data Compare
permanent disconnects from database servers

Try to select Keep connection alive on the Advanced tab of the Database Connection Properties dialog box and set ping timeout value less than "wait_timeout" variable of the server.

[aasat77]

Yeah, we've fixed this bug in the last build of dbForge Studio for MySQL v3.60. So, the fix will be available in the next build of Schema Compare for MySQL.

We have version 1.0.292, When will the next version be released?

[Alexz]

We're working to release of dbForge Studio for MySQL v4.0 now and after that we'll plan to update other products.