server does not support persistent

[molino]

Hello

I'm working with the latest MariaDB version and using a table with persistent virtual columns.
When trying to synchronize the project with the database I'm getting the inconsistent warning "server does not support persistent". Because of this message it's not possible to create the project table file (only option in synchronization was drop and none ... and now after dropping only none ^^).
Is there a way to to tell dbForge that MariaDB is supporting virtual columns? I'm new to dbForge and currently testing it, so there may be an easy way I haven't seen.

Greetings

Edit:
I have now reconstructed the deleted files and added them via "Add existing file..." to the table folder. When comparing project and database files/tables I'm getting the message "project 'project_name.mydev' build failed". There are some entries reporting false file position in build order. But why build order? I only want to compare tables. And why is the error list cleared as soon as I close the modal error message window? So I will not be able to see all error message entries because the modal window prevents scrolling.

[alexa]

Unfortunately, there is no such a possibility. However, we will try supporting this in the next product version.

[molino]

is there a timeline for the next version? I really like the tool and was planing a purchase but I need the synchronization of different databases.

[alexa]

Unfortunately, we don't have a timeframe for this.

[molino]

Hello,

I'm currently a bit irritated. Just found this new feature release note for v.6.1:

MariaDB Virtual Columns are supported in:

Data Export/Import wizards
Data/Schema Comparison tools

https://www.devart.com/news/2014/dbforg ... sql61.html

Please can you clarify it?

Best regards

[alexa]

MariaDB Virtual Columns are supported in Data Export/Import wizards and Data/Schema Comparison tools, but not in Database Projects.