TUniTable Delphi XE2 Transaction Error on MySQL Database

Discussion of open issues, suggestions and bugs regarding UniDAC (Universal Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
sashki
Posts: 11
Joined: Fri 25 Nov 2011 17:17

TUniTable Delphi XE2 Transaction Error on MySQL Database

Post by sashki » Tue 20 Dec 2011 16:25

I discovered a possible transaction bug with the "TUniTable" component when you enter into a transactional state and you're trying to edit and post some data.

It's definitely not the database, as I'm running MySQL 5 with InnoDB transaction tables. Also, this works in an earlier version of UniDAC on earlier versions of Delphi.

After you connected to the database via the "TUniConnection" component and linked to a table in the database on the "TUniTable" component, try the following:

Code: Select all

  UniTransaction1.StartTransaction;
  UniTable1.Open;
  UniTable1.Edit;
  UniTable1.FieldByName('FirstName').AsString := 'John Doe';
  UniTable1.Post; //-> This is where the error is raised
  UniTransaction1.Commit;
The exception raised is as follow:
"Multiple transactions are not supported by the database".

This exact code can be replicated using an earlier version of UniDAC on Delphi 2010, which works 100%.

So all I can think of, is that there is a bug in your latest release for Delphi XE2??

I'm currently running UniDAC version 4.0.2 in Delphi XE2 Update 2.

Does anyone have any idea why this is happening? Or is this a confirmed bug and what do you suggest I do to get around this?

Thank you.
Last edited by sashki on Fri 23 Dec 2011 00:01, edited 2 times in total.

AndreyZ

Post by AndreyZ » Wed 21 Dec 2011 14:34

Hello,

Thank you for the information. We reproduced the problem and the investigation is in progress. We will notify you when we have any results.

sashki
Posts: 11
Joined: Fri 25 Nov 2011 17:17

Post by sashki » Fri 23 Dec 2011 00:01

If you can please let me know as soon as you have a solution to this problem.

In the mean while, I took the route to update the table with a SQL statement, but would like to know that this issue has been solved.

Thank You!

AndreyZ

Post by AndreyZ » Fri 23 Dec 2011 14:02

We have fixed this problem. This fix will be included in the next UniDAC build. We plan to release the new UniDAC build next week.

Post Reply