Multiple new bugs with data migration tool

The other day I reported problems with updating the database after running the data migration tool on an existing SQL server database instance, (see Update Database: problems with scripts). I haven’t head back on this so I figured I’d see if I can nail down the issue to either the data migration tool or the SQL database by running the migration tool tutorial: https://github.com/cuba-platform/cuba-vision-clinic/wiki, results follow using VisionClinic database created by following the steps in the tutorial

The following are bugs/tutorial inconsistancies that surfaced with platform-6.9.4. The SQL server verion is SQL server 2017 developer edition:
* Table and columns names surrounded by escaped double quotes, (ie. “Product”), primary key inconsistently displayed with a probable side effect when system determines if database changes needed.
* When running the application, the system advises that the “database scheme does not conform to the data mode” with instructions to run scripts to update the database.
* Extra plurals are in the menu items, (ie. “Patientses”).

See below screen dumps

Cuba%20DataMigration%20Backslashes3

Cuba%20DataMigration%20First%20Run%20Step%204b

Cuba%20DataMigration%20Extra%20plural

Hi,

Table and columns names surrounded by escaped double quotes, (ie. “Product”), primary key inconsistently displayed with a probable side effect when system determines if database changes needed.

Studio wrapped column and table if it contains mix cases literals. Incorrect “database changes” will be fixed in the next version (https://youtrack.cuba-platform.com/issue/STUDIO-4697).

When running the application, the system advises that the “database scheme does not conform to the data mode” with instructions to run scripts to update the database.

This will also be fixed in https://youtrack.cuba-platform.com/issue/STUDIO-4697