Michał Sadowski

Travis / my_prove said: ``` Test Summary Report ------------------- tests/test-mytap-runtests.my (Wstat: 0 Tests: 14 Failed: 2) Failed tests: 1, 1 Parse errors: More than one plan found in TAP output...

Interesting case in build 31 for MySQL 5.7 (https://travis-ci.org/hepabolu/mytap/builds/603775539?utm_medium=notification&utm_source=github_status) -- it look there is a bug which arises when using constructions like `SELECT tap.ok((), ...)`. It's safer to use session...

> The order that tests are run can be slightly problematic because it can complicate setup and teardown or slow things down at the very least and no one likes...

Sorry, I didn't mean to be rude or harsh in my previous comment. The problem is, that sometimes when writing your code you *expect* to run its parts (test cases,...

I am almost sure it's not possible. You had to have an option to perform assertions using more than one connection (or thread) in one time. You will have to...

Ready for merge except one fixup commit and question posted in PR description. Please take a look at this.

Any news on this?

I think we can workaround this problem with NOT using `mysql.user` or `information_schema.columns` and using own views. Example below. Using: ```sql DROP VIEW IF EXISTS tap.mysql__user; CREATE SQL SECURITY INVOKER...

OK, I feel we're getting closer. But, I can not understand what is the meaning of these statements: ```sql SET @sql1 = 'CREATE USER ''__taprole__''@''localhost'''; SET @sql2 = 'CREATE USER...

Or better, if anyone can translate it to MariaDB I think I'll be able to do the rest (compatibility layer + tests).