This week's book giveaway is in the Mac OS forum. We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line! See this thread for details.
Hi all, in my application i have two databases. lets call them a & b.from database a i will be just reading data and displaying it to the user.no writing has to be done.but on database b i have to perform writing as well as reading operations.since multiple users will be accessing this database i have a few questions i) how do i take care of the cuncurrency issue? ii)will the cuncurrency issue come in only when two users try to write something to the database at the same time or is it a problem even when multiple users try to read at the same time? iii) should i implement connection pooling?i dont expect a lot of cuncurrent users(around 50 or so).is there any threshold value for the no. of concurrent users beyond which it is advisable to implement connection pooling. Thanks in advance. Subbu
subject: How to handle concurrent write/read to a db