From my understanding MySQL locks a unit upon writing to ensure no reads happen during that: so writing blocks any reading you do. Depending on the storage engine you use (more on that here) it may only block a row; or the entire table; you should probably choose to do rows, although it takes more resources to do that, as your DB will be accessed by multiple applications that may not hold their own caches, etc. and blocking one sounds like it would be disasterous.
A connection pool should reduce the amount of stress on your DB making connections and the amount of time it takes for the Java or PHP to fetch data, it should help, but not during the query aspect.
Hi, I am a newbie in developing a website. i have tried to connect using mysqli conncetion
Here is my simple code.
// db.php code
//$con = mysqli_connect("localhost","root","","bakery"); ...
If you're in one of those predicaments where cls.__private attributes just aren't enough since they can easily be accessed through inst._cls__private, and you need something a little more secure, here's ...