Error in mapping

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Post Reply
Posts: 4
Joined: Fri 25 Mar 2011 19:42

Error in mapping

Post by fernando.tellfree » Mon 11 Jul 2011 12:50


My database has 410 tables each. With version 5.8 I have this error, only with version 6.30. What should I do to be able to map my database?

Follow the image:


Devart Team
Posts: 8088
Joined: Thu 14 Aug 2008 12:44

Post by Shalex » Mon 11 Jul 2011 14:47

Please give us the following information:
1) which ORM (Entity Framework, LinqConnect, or NHibernate) are you using?
2) the exact version of your MySQL server;
fernando.tellfree wrote:With version 5.8 I have this error, only with version 6.30.
tell us the exact version ( of dotConnect for MySQL where the problem persists. Have you tried the latest (6.30.185) version?

Posts: 4
Joined: Fri 25 Mar 2011 19:42

Post by fernando.tellfree » Wed 13 Jul 2011 20:36

1) ORM = Entity Framework (Devart Entity Model)

2) 5.1.38-community

3) the problem persists with version =

I think this problem is because the amount of characters of the name of my foreign key is equal to 59, but I'm not sure because the error message is very generic. If this is really, is possible to increase the character limit.

Devart Team
Posts: 2919
Joined: Mon 07 Jul 2008 13:16

Post by AndreyR » Thu 14 Jul 2011 10:26

There is no problem with the long constraint names, I have checked this.
Could you please provide us the call stack of the exception?
Here are the steps:
- Open 2 instances of Visual Studio.
- In the first instance, open the project in which you wish to add the model.
- In the second instance, go to Tools->Attach to process...
- Select the first instance of Visual Studio(devenv.exe with an opened project) in the process list.
- Go to Debug->Exceptions and check the Common Language Runtime Exceptions checkbox.
- Ensure that the Enable Just My Code checkbox (Tools->Options->Debugging) is unchecked.
- Perform the steps to get the error in the first instance of Visual Studio.
If the error was catched, please provide us the type of the exception and the call stack.

Post Reply