Executes a prepared Query
Example 1566. Object oriented style
Example 1567. Procedural style
Code Examples / Notes » mysqli_stmt_execute
Just to clarify this note in the Manual regarding this function:
"Note: When using mysqli_stmt_execute(), the mysqli_stmt_fetch() function must be used to fetch the data prior to performing any additional queries."
This is because this function DOES NOT store the result set on the client side so you have to fetch everything in the result set or else you risk major errors.
If you however use the function mysqli_stmt_store_result immediately after you use this function, you are forcing the result set to be stored on the client side and thus it is safe to issue extra queries before fetching all the data.
This is where you really have to make a choice regarding on your application's priorities. If you know your result set is memory hefty, then its a good idea not to store it on the client side so you don't run in any errors regarding unavailable memory on the server. But this also means your not going to do a lot of calculations on the result set or else you will prevent any other usage of the table to which the result set came from until you fetched it all.
If your going to do a lot of calculations or your result set is not memory hefty, its probably a good idea to store it on the client side.
Most of these problems can easily be solved if you have a lot of memory available on your server but thats usually not the case for those on shared hosting.
An intelligent way to counter this problem if your on a shared host is to be smart in the way you design your queries. Try to limit the result set if you know you will be fetching memory hefty result sets.
Test different alternatives for your application and see what works best for you under different conditions.
If you select LOBs use the following order of execution or you risk mysqli allocating more memory that actually used
If you skip 3) or exchange 3) and 4) then mysqli will allocate memory for the maximal length of the column which is 255 for tinyblob, 64k for blob(still ok), 16MByte for MEDIUMBLOB - quite a lot and 4G for LONGBLOB (good if you have so much memory). Queries which use this order a bit slower when there is a LOB but this is the price of not having memory exhaustion in seconds.
I decided to use mysqli since I could use prepared statements for my stored procedures. To me, this is good so I don't have to worry about SQL injection by doing this. No dynamic SQL on the PHP end or in my stored procedure.
Anyways, I would open one connection to the database and run multiple stored procedures. On the second stored procedure, I would get this error - lost connection - and I know that none of my queries are long running where I would hit a timeout.
To me, I just care about the result set that my stored procedure is producing, which is only one result set. The rest can be safely ignored. If you are in the same boat as me, this is what you can do:
After you are done getting the resultset from mysqli, do the following before you execute the next query: