MySQL Bugs: #39496: Transactionscope/Rollback

Bug #39496	Transactionscope/Rollback
Submitted:	17 Sep 2008 11:42	Modified:	16 Jul 2009 9:33
Reporter:	R Roberts	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	5.2.1	OS:	Windows (Windows XP Pro)
Assigned to:		CPU Architecture:	Any

Description:
Hi

I seem to be having problems in trying to do a rollback on C# VS 2005. I am using MySQLConnector.Net 5.2.1, SQLYog CommunityEdition v6.16, VS 2005 (C#).

I have created datatable through XSD Wizard (dataset.xsd).

Then on my BLL (Business layer logic) - I have coded with transactionscope etc but it refuses to do a rollback.

I can't be sure if this is a bug and if it is not a bug; can you please tell me how it should be done. I have read on the internet - that it is a bug.

Thanks

Romy

How to repeat:
Just a table with two columns

Using XSD

Then did the coding in BLL

I am not using insertcommand, updatecommand, selectcommand and deletecommand. I have just create a delete SQL text through the XSD wizard for the table adapters. 

I can't seem to get the transaction using the MySQL connection, it still deletes and never does a rollback. Still trying various approaches on this in still using the XSD(table adapters).

Thanks

I have tried this approach and yet again it still did not rollback either; just kept inserting it:

int RowsAffected = 0;
manufacturersTableAdapter X = new manufacturersTableAdapter();
X.Connection.Open();
MySqlTransaction myTrans = X.Connection.BeginTransaction();
X.AttachTransaction(myTrans);
try
{
DataSet1.manufacturersDataTable manuRows = X.GetAllManufacturers();
DataView view = new DataView(manuRows);
view.RowFilter = "manufacturer_id = '" + Code + "'";
if (view.Count == 0)
   {
        X.Insert(Code, Description);
        throw new Exception();
   }
else
  {
    texstatus = "The code you have entered is already in use. Please use another.";
  }
}
catch (Exception ex)
{
    myTrans.Rollback();
    texstatus = "Transaction has been aborted!";
}
return (RowsAffected == 1);

Any luck with it? Is there a way to resolve this please?

Romy, I apologize on our behalf, too much work and we forgot about this report. Is this solved by now? I remember we had similar discussion on another report.

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".