Difference between MysqlDirect.net 2.80 and 3.55.

Difference between MysqlDirect.net 2.80 and 3.55.

Postby Amish » Thu 12 Apr 2007 04:46

hi
sorry for late reply...
i cant send u my whole project but we are doing some research and developement and getting some good results.it seems that it may be problem in database server(mysql server).i will send you the final report after some days.

thanks
Amish
 
Posts: 20
Joined: Thu 05 Apr 2007 12:04
Location: INDIA

Postby Alexey » Thu 12 Apr 2007 08:12

I will be looking forward.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby Amish » Sun 15 Apr 2007 09:15

Hi,
After Doing Some Tests,We Have Finally Reached The Conclusion:
The Database Server Info We Are Using In Our Main Application:

Name:phpMyadmin
Version:2.6.0-pl3

Now We Have The Same Application On Two Systems.On One System We Are Using MysqlDirect.net(3.55) and On Another System We Are Using MysqlDirect.net(2.80).

After Stopping And Restarting The Mysql Server (phpMyadmin),If We Start The First Application with 3.55 it Will Start Normally But The Other One with 2.80 Is Showing Error like "Method Not Supported".

If We Restart The Server Further and Run The Second Application With 2.80 It Will Start Normally But The Other One Is Showing An Error "Index Out Of Range".

Hope You Will Get The Problem.

(In addition,We Have Made A Test Application Which Is Running Normally Using Both Version of Mysqldirect.net And The Same Server; On Two Different System.)

Thanks
Amish
 
Posts: 20
Joined: Thu 05 Apr 2007 12:04
Location: INDIA

Postby Alexey » Mon 16 Apr 2007 14:37

(In addition,We Have Made A Test Application Which Is Running Normally Using Both Version of Mysqldirect.net And The Same Server; On Two Different System.)
What does this mean? The problem occurs only with your production program and cannot be reproduced in a test application? Please explain.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby Amish » Tue 17 Apr 2007 04:49

Hi.
Yes ,you are correct.we are not able to generate this error in our test application.
Amish
 
Posts: 20
Joined: Thu 05 Apr 2007 12:04
Location: INDIA

Postby Alexey » Tue 17 Apr 2007 06:47

Is it possible for you to test this with MySQLDirect .NET 4.0?
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Postby Amish » Thu 03 May 2007 07:31

hi,

We have solved the problem arised earlier as, i think,you may remember.

Now There Is another Problem.

We are using pgmysqldirect.net and mysqldirect.net in the same applicaton providing the facility that user can use any of the connection.In which we have to add two licenses.Now There Is The Problem that We can not add two license file with same name.


What we can do now?

Thanks
Amish
 
Posts: 20
Joined: Thu 05 Apr 2007 12:04
Location: INDIA

Postby Serious » Thu 03 May 2007 08:40

You should add one file with two lines (this behaviour is correct for all products that use .NET component licensing). Example:
Code: Select all
CoreLab.MySql.MySqlConnection, CoreLab.MySql
CoreLab.PostgreSql.PgSqlConnection, CoreLab.PostgreSql
Serious
 

Postby Amish » Thu 03 May 2007 08:46

Thanks A Lot.Now It Is Working.
Amish
 
Posts: 20
Joined: Thu 05 Apr 2007 12:04
Location: INDIA

Postby Amish » Fri 04 May 2007 06:46

Hi

Currently I m Using PgsqlDirect.net and Mysqldirect.net.

I want to use Corelab.Common.Dbconnection namespace because of multiple server connection.But It Is showinf an error as i stated below.

"Dbconnection is ambiguous in the namespace Corelab.common."

May I have any Help regarding this problem?

Thanks
Amish
 
Posts: 20
Joined: Thu 05 Apr 2007 12:04
Location: INDIA

Postby Serious » Fri 04 May 2007 09:55

Use the IDbConnection interface or install MySQLDirect .NET 4.0 and PostgreSQLDirect .NET 3.0. These products have common assembly CoreLab.Data, which will solve the ambiguous references problem.
Serious
 


Return to dotConnect for MySQL