MySQL Bugs: #31467: problem when using MySQL Connector Net 5.1.3 in asp.net with ajax

Bug #31467	problem when using MySQL Connector Net 5.1.3 in asp.net with ajax
Submitted:	8 Oct 2007 20:24	Modified:	7 Nov 2008 3:58
Reporter:	Brian McCormick	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	5.1.3	OS:	Windows (xp sp 2)
Assigned to:	Bogdan Degtyariov	CPU Architecture:	Any

Description:
On Asp.net pages with an updatepanel/scriptmanager (ajax) when I replace the mySQL ODBC connector v 3.51 with the .net connector in any sqldatasource object, and controls that use that datasource (at least all dropdownlist controls) quit firing the SelectedIndexChanged event. Since it works with the ODBC connector and I have scoured the internet looking for problems with other connectors exhibiting this behaviour and can't find any I am guessing it must be an issue with the .net connector.

I don't really understand how the datasource can keep an event from firing on a control that uses it but that is the case. I did test it when ajax wasn't involved and it works fine though. I will try reporting this to Microsoft also but since it works ok with SQL server I don't expect much help there.

thanks

How to repeat:
create an sql datasource in an asp.net page with an updatepanel. Add a dropdownlist control to the updatepanel and set it's datasource to the sql datasource just created. Add a 'selecteditemchanged' event to the dropdownlist control. If you use an odbc connection the event will fie. If you use a .net connector it won't.

Hi Brian and thanks for your report. I am sorry for the delay in processing. I'll assign a coworker to help you deal with this.

Brian,

Are you using some custom dropdown control or the standard one?
Can you attach a test Visual Studio project that would reproduce the error?
Thanks.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".