Devart Forums

Recently I renew a license and I'm using:
dotConnect for MySql Pro 8.8.862 last version.
I tried Entity Developer to add a SSH new model, I tried LinqConnect Model, Entity Model, EF Core Model, all the same...

File-New model-Select any model-Wizard-Database First
I set:
1.-Host:localhost
2.-Port:3306
3.-UserId: ****
4.-Password: ****
5.-Check: Allow saving password
6.-Select Advanced button and here I set:
6.1.-SSH Host:187.216.**.***
6.2.-SSH Port:5050
6.3.-SSH User: ****
6.4.-SSH Password:****

Textbox of final connection string shows something like:
user id=root;password=********;host=localhost;persist security info=True;ssh host=187.216.***.***;ssh port=5050;ssh user=******;ssh password=******

Tried test connection or next button throws:
Can't connect to MySQL server on ' localhost' (10061)

Same connection settings are successfully in DbForge for Mysql standalone but connection string property a bit different:
User Id=root;Host=localhost;Protocol=Ssh;Character Set=utf8;SSH Host=187.216.***.***;SSH Port=5050;SSH User=****;SSH Authentication Type=Password

Note that in Entity Developer missed:
'Protocol=Ssh' and 'SSH Authentication Type=Password'
I reset default SSH Authentication Type value in entity developer and adds to connection string but still throws error, still missed 'Protocol=Ssh' in Entity Developer...

I missing set something?

I have MariaDb running on Debian Jessie last version 10.1.22 and shows:
5.5.5-10.1.22-MariaDB-1~jessie

Thanks in advance!

Fixed connection I missed set 'Protocol' property (in another property group), maybe more intuitive if you set some ssh properties, that entity developer auto set Protocol=ssh or notify incorrect settings in some way

But now throws some errors in model, seems to need spatial types support....

1 Invalid class '****': The property 'Geom' is not valid. Type '****' is not supported by Entity Framework Core. DataModel1.efml

2 Invalid class '****': The property 'PolyDef' is not valid. Type '****' is not supported by Entity Framework Core. DataModel1.efml

3 Invalid class '****': The property 'GeomDef' is not valid. Server type '****' is not supported by Entity Framework Core. DataModel1.efml

Thanks in advance!

idem84 wrote:Fixed connection I missed set 'Protocol' property (in another property group), maybe more intuitive if you set some ssh properties, that entity developer auto set Protocol=ssh or notify incorrect settings in some way

Thank you for your suggestion. We will add "To use SSH, set Protocol=Ssh." to the description of all properties in the SSH section of the connection editor.

idem84 wrote:But now throws some errors in model, seems to need spatial types support....

Please refer to http://blog.devart.com/entity-framework ... imitations:

Some of the features present in EF6 providers are also not supported in EF Core providers because Entity Framework Core itself does not support many of Entity Framework 6 features. For example, these features include spatials or stored procedure support, etc. You can find more information about not supported features in another our blog article, Migration of Entity Framework 6 projects to Entity Framework Core 1 (Entity Framework 7)".