Translation Issues w/unsigned

Translation Issues w/unsigned

Postby jeffs » Wed 20 Nov 2013 18:04

Hi,

I'm trying to get database-first modeling working with the latest version of Entity Developer Pro and dotConnect for MySql.

We had a version created with LinqConnect in the past which worked fine, but upgrading to the latest versions of the above products is causing us fits.

When we create a new LinqConnect model for the database in ED and pull in the classes for the tables the first time, many of the unsigned types are coming across with "UNSIGNeD" doubled in their Server Data Type field. For example: "FLOAT UNSIGNED UNSIGNED NOT NULL".

The entity developer does;t know how to deal with this, and somas it to System.Object when it should map to double in C#.

For some reason, our database has a ton of weird types like "TINYINT(3) UNSIGNED NOT NULL", which is mapping to System.Byte in C# where it should be a short.

I'm not free to change the DB at all.

Is there any way to hint the mapper as to what to map certain types to if it's guessing wrong?
jeffs
 
Posts: 7
Joined: Fri 15 Oct 2010 13:42

Re: Translation Issues w/unsigned

Postby MariiaI » Thu 21 Nov 2013 10:26

many of the unsigned types are coming across with "UNSIGNeD" doubled in their Server Data Type field. For example: "FLOAT UNSIGNED UNSIGNED NOT NULL"
We couldn't reproduce this issue with the latest build of dotConnect for MySQL 8.1.36. Please send us the model and DDL scripts for database objects, with which this behavior is reproducible so that we are able to investigate it in more details.

Is there any way to hint the mapper as to what to map certain types to if it's guessing wrong?
It is possible to change the default mapping before creating a LinqConnect model via the Database-First approach. You can do it by opening Tools -> Entity Developer -> Options -> Server Options -> MySQL and making the necessary changes.
MariiaI
Devart Team
 
Posts: 1472
Joined: Mon 13 Feb 2012 08:17


Return to dotConnect for MySQL