Devart Forums

In evaluating dbForge to switch from MySQL Workbench, I've encountered a visual issue where the product draws all table connection lines in FRONT of the tables. In a large-scale complex Architecture, this is visually "unacceptable". MySQL Workbench properly draws these connections behind the tables.

I can't seem to find any way to turn this off, and while there is a "bring shape (forward/backward)" option, that doesn't even seem to work properly. And re-route only works half of the time.

Here's an example of the issue. Note the use of Containers.


Any help on this would be appreciated.

We were not able to reproduce this issue.

Could you please let us know what version of dbForge you are using?

You could also try the 'Shape -> Send to Back' option invoked by right-clicking the object entity rather than the connection link.

Very concerned at this response. This issue is easily reproducible by importing a sizable table structure and then manually arranging the tables in containers. Additionally, setting the Z-order of the table has no impact on the lines. I believe you are also overlooking the fact that there should be a "draw lines behind tables" option (which should be enabled by default), which doesn't seem to exist. Also note by default dbForge draws an imported table design schema by placing the tables so none of the connection routes draw over anything. MySQL Workbench handles this issue easily by drawing the lines in a dark grey color and always behind tables. Note I can reproduce this issue 100% of the time and with ease. As you can visually see, it's quite a problem. Version 8.2.23.

Hello Ryan,

Thank you for the reply.

Sorry for that question. I just sent you another e-mail the same day (Ticket #302902) to let you know that we were finally able to reproduce the issue happening with containers on the diagram.

Our developers team will fix it in one of the next product versions.

alexa wrote: ↑Mon 16 Dec 2019 18:00 Our developers team will fix it in one of the next product versions.

Thank you. Are you able to provide more information as to when the fix will be released? Are we look at weeks or months?

Any update on this?

Sorry for the delay on this.

It's more likely it will take months since we have lots of other fixes to do that were reported earlier.

Sounds like Devart needs new project managers/developers. It shouldn't take months to fix this issue, and if your backlog is that heavy, there's other factors that need to be addressed. While I appreciate the update, the timeframe is very disappointing and reflects poorly on your company's development abilities.

BTW one VERY easy way to address this problem quickly until the routing code is updated is to add a simple "Draw Lines Behind Tables" option that the user could toggle (and turn it on by default). That'd solve the problem for now.

Please note this problem is also in the dbForge Studio 2020 BETA that was just released, so it doesn't appear it was fixed/addressed. I looked in the Option settings for Diagram and didn't notice any new options to "draw lines behind objects" or anything similar.

This is still in the queue for fixing.

Thanks for the update - Is this supposed to be fixed by the release of 2020? If not, how long?

Unfortunately, we don't have a time frame for this.

Any update? Now that the new version is out and it's been patches, this QOL issue is continuing to be an impediment; along with the crazy connector problems.

It's still in the queue for fixing.

Unfortunately, we don't have a time frame for this.