MySQL locks and transactions

Hello dear Wappler community superstars !

I was wondering if (My)SQL transactions and locks could be used within Wappler ?
I can see that the syntax exists in the custom query autocomplete helper.
But so far, my attempts to execute transactions failed.

For instance, this test transaction :

produces the following error :
2019-11-24_1119

Now if I place each transactions in a seperate query, I get the following error on the first one “START TRANSACTION;” :
SQLSTATE[HY000]: General error: 2030 This command is not supported in the prepared statement protocol yet

Thank you very much for your help ! :slight_smile:

2 Likes

Have you tested what happens if you set the Prepare Statements to True or False in the Database Connection. I believe it should set to True.

It’s actually set to auto.
I’ll try both True/False values and will come back.
Thank you for your help @patrick :slight_smile:

Indeed, with True instead of auto (or false), the query executes properly when it’s correct.

If I voluntarily introduce a syntax error in my second query though (or anything else that should return an error), there is no commit (great!) but it always returns “No results returned”.

I tried both the test button in the Wappler query editor and calling the php server connect file, same issue.

It seems like no exceptions are returned with Prepare Statements to true.
Am I missing something ? :slight_smile:

Thank you very much for your help !