tntdb on Ubuntu on Windows 10: Erros with MySQL

[dev8765]

My installed versions:
I have downloaded and installed the cxxtools-, tntnet- and tntdb-master.zip's this week on my client.

My client:
Bash on Ubuntu on Windows 10 (Creators update, 03-2017)
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
ldd (Ubuntu GLIBC 2.23-0ubuntu7) 2.23
For the "tntnet" command to be able to start I had to deactivate TCP_ACCEPT_DEFER (I commented the whole block in configure.ac).

The "tntdb-test" command is working fine on my client with sqlite3 3.11.0

But some of the asserts fail with my db server in my lan. Most are looking to be not important (testDouble, ininity, longval, ...).
But there are two issues that are scaring me.

My db server:
Linux kernel 2.6.32 (Mips cpu)
Debian 6.0.10
MySQL 5.1.73-1 (Debian)

Issue 1:
base::testTransaction: ASSERTION at base-test.cpp:371
not equal:
value1 (count)=
<3>
value2 (2)=
<2>

Issue 2:
types::testNull: OK
types::testBool: EXCEPTION
Mysql-Error 2014 in mysql_query: Commands out of sync; you can't run this command now
types::testShort: EXCEPTION
Mysql-Error 2014 in mysql_query: Commands out of sync; you can't run this command now
types::testInt: EXCEPTION
Mysql-Error 2014 in mysql_query: Commands out of sync; you can't run this command now
types::testLong: EXCEPTION
Mysql-Error 2014 in mysql_query: Commands out of sync; you can't run this command now
types::testUnsignedShort: EXCEPTION
Mysql-Error 2014 in mysql_query: Commands out of sync; you can't run this command now
...
types::testBlob: OK
types::testDate: OK

[maekitalo]

First of all I never use mysql. Postgresql is always better. Even the license. But of course I support mysql with tntdb because it is still so common.

Which version of tntdb you use? The line number 371 makes no sense in the current git version. I guess it is line 397 in the git version. There count is expected to be 2. It checks whether the the transaction was rolled back. It looks like the transaction did not work there. And now we come back to mysql. If you use a backend, which do not support transactions, you can start, commit and rollback transactions as you want, they just silently do not work. Mysql do not complain about not supported operations. It just do nothing. Thats how mysql works and that is one of the reasons I do not use mysql never.

Can you check, if you really use a transaction table type?

The following error message looks familiar to me. As far as I remember I have fixed that in later versions.

[dev8765]

Thank you for your informations and for your quick response.
I have now changed my client to:
CentOS 7 (g++ (GCC) 4.8.5 20150623, mariadb-devel.x86_64 1:5.5.52-1.el7)
And I "git clone"-d all 3 tntnet-repos yesterday in order to get the newest possible version.
But without luck so the errors keep unchanged: The transaction is not working and the testBool-testString tests get out of sync.
I have to tell that my db server is chuckold (MySQL 5.1.73-1 (Debian)) and very slow (Mips cpu).

base::testTransaction: ASSERTION at base-test.cpp:397
not equal:
value1 (count)=
<3>
value2 (2)=
<2>

types::testBool: EXCEPTION
Mysql-Error 2014 in mysql_query: Commands out of sync; you can't run this command now
types::testShort: EXCEPTION
Mysql-Error 2014 in mysql_query: Commands out of sync; you can't run this command now
types::testInt: EXCEPTION
Mysql-Error 2014 in mysql_query: Commands out of sync; you can't run this command now

[dev8765]

I changed the table type from MyISAM to InnoDB and the transaction is now fully working:
base::testTransaction: OK
Thank you for pointing this out.
The file mysql-test.sql could be enhanced by ... TYPE = InnoDB; in the source repo.
But the "out of sync" errors keep unchanged:
types::testBool: EXCEPTION
Mysql-Error 2014 in mysql_query: Commands out of sync; you can't run this command now