Transactions via http tunnel
Posted: Fri 05 May 2017 16:12
I'm interested in the dotConnect for MySQL (With the http tunnel)
But, with direct connections, I often use transactions where the client will update more than one table and the client receives result of the update(s) and, based on the result of those updates, will Commit or Rollback the the transaction.
Can the php tunnel handle that? I mean how does the connection persist when the client is sending more than one query to the php script.
Is it all handled locally by dotconnect or is there something in the php at the server that allows the client to reuse the same connection through multiple posts?
Thanks
Ian
But, with direct connections, I often use transactions where the client will update more than one table and the client receives result of the update(s) and, based on the result of those updates, will Commit or Rollback the the transaction.
Can the php tunnel handle that? I mean how does the connection persist when the client is sending more than one query to the php script.
Is it all handled locally by dotconnect or is there something in the php at the server that allows the client to reuse the same connection through multiple posts?
Thanks
Ian