MySQL Bugs: #7528: Mysql Connection

Bug #7528	Mysql Connection
Submitted:	24 Dec 2004 14:17	Modified:	5 Jan 2005 18:42
Reporter:	Hasan Raihan	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	4.1.8	OS:	Windows (Windows XP)
Assigned to:	Reggie Burnett	CPU Architecture:	Any

Description:
I am using .net connector 1.0 to connect MySql  database. when I use
MySql 4.1.7 then there is no problem. But when I try to use MySql 4.1.8
and run my application i got this error message :
Item has already been added. Key in dictionary: "innodb_max_purge_lag" Key being added: "innodb_max_purge_lag" 
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.ArgumentException: Item has already been added. Key in dictionary: "innodb_max_purge_lag" Key being added: "innodb_max_purge_lag"

Source Error: 

Line 119:					String sqlMax = "SELECT Max(ordernummer) FROM verkooporder";
Line 120:					MySql.Data.MySqlClient.MySqlCommand cmdMaxOrdernummer = new MySql.Data.MySqlClient.MySqlCommand(sqlMax,mySqlConnection);
Line 121:					mySqlConnection.Open();
Line 122:					_ordernummer = (int)cmdMaxOrdernummer.ExecuteScalar();
Line 123:					_ordernummer = _ordernummer + 1;
 

How to repeat:
Using .net connector 1.1 and connect to mysql 4.1.8

Suggested fix:
I want to connect and work with MySql 4.1.8 version

same problem here.  also changed to 4.1.7. and it works again. If you look at the system variables  (SHOW VARIABLES LIKE 'innodb_max_purge_lag';) after a fresh installation of mysql, you'll see that innodb_max_purge_lag is inserted twice. This is not the case in 4.1.7. 

Greetz
Sivard

What version of the connector are you using?  We had a problem with early versions where duplicate variables would cause this but not anymore.  Try 1.0.3

Not enough information was provided for us to be able
to handle this bug. Please re-read the instructions at
http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it
to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Have the same problem here on WindowsXP-SP1, mysql 5.0.2 alpha.
The command SHOW VARIABLES LIKE 'innodb_max_purge_lag' shows 2 variables, as stated by Sivard.
Nothing special done during installation, just rolled the installer and got this error message (while trying to connect with nHibernate):

NHibernate.TransactionException: Begin failed with SQL exception ---> NHibernate.ADOException: cannot open connection ---> NHibernate.ADOException: Could not create connection from Driver ---> System.ArgumentException: Item has already been added.  Key in dictionary: "innodb_max_purge_lag"  Key being added: "innodb_max_purge_lag"
   at MySql.Data.MySqlClient.InternalConnection.Configure(MySqlConnection connection)
   at MySql.Data.MySqlClient.MySqlConnection.Open()
   at NHibernate.Connection.DriverConnectionProvider.GetConnection()
   --- End of inner exception stack trace ---
   at NHibernate.Connection.DriverConnectionProvider.GetConnection()
   at NHibernate.Impl.SessionFactoryImpl.OpenConnection()
   --- End of inner exception stack trace ---
   at NHibernate.Impl.SessionFactoryImpl.OpenConnection()
   at NHibernate.Impl.SessionImpl.get_Connection()
   at NHibernate.Transaction.Transaction.Begin()
   --- End of inner exception stack trace ---
   at NHibernate.Transaction.Transaction.Begin()
   at NHibernate.Transaction.TransactionFactory.BeginTransaction(ISessionImplementor session)
   at NHibernate.Impl.SessionImpl.BeginTransaction()

Hope this helps...

Allright, solved it!
Needed the latest version of the MySQL Connector Net (version 1.0.3).
old version that was giving problems was 1.0.0.22708 btw.