Devart Forums

We have analyzed the problem. This is MS DataSet restriction. MySQL-specific features are not supported in it and we cannot overcome this in present.

Please describe the problem in detail. Where do you expect primary key to appear? Provide your database table definition.

Please specify your hardware platform, operating system, and send me your project.
I'll need all this to reproduce the problem.

Try to execute Make sure that connection string is the same for both MyDirect .NET and Navicat.
If the problem persists, please specify your hardware platform, operating system, version of MySQL server and send your test project to the address provided in the Readme.html file.

This task appears to be quite involved, so finding a solution may take a lot of time.
Thanks for your patience.

We will investigate the problem you described.

Yes, the latest version is 3.55.25.
The error is MySQL server's error. Try to execute your SQL query in any other client.

Unfortunately, we don't know any.

Dear users,

New build of OraDirect .NET version 4.25.24 is available for download now.
This version includes:

• Fixed bug with schema generator for .NET Entity Framework
• Fixed bug with case sensitive names in DbDataTable.ParentRelation

Core Lab development team
http://www.crlab.com/oranet

Dear users,

New build of PostgreSQLDirect .NET version 3.25.20 is available for download now.

This version includes:

• Fixed bug with schema generator for .NET Entity Framework
• Fixed bug with case sensitive names in DbDataTable.ParentRelation

We're looking forward to your comments and suggestions.

Core Lab development team
http://www.crlab.com/pgsqlnet

Dear users,

New build of MyDirect .NET version 4.25.21 is available for download now.
This version includes:

• Fixed bug with schema generator for .NET Entity Framework
• Fixed bug with case sensitive names in DbDataTable.ParentRelation

Core Lab development team
http://www.crlab.com/mysqlnet

teofilo, do you also have 64bit platform? I'm asking because I can't reproduce any problem on my clean virtual PC with only VS2008 Beta2 installed.

We have never experienced such problems.
Maybe there is some obsolete parts from another client on your PC. This can be verified if you attach to your application in unmanaged mode and see what DLLs and from what paths are loaded.
Alternatively, you can work around tnsnames.ora if you set your connection string like this:

This is a known Oracle bug.
Types from packages cannot be described.

You're welcome