Bare with me on this. I dont know much about connection pooling. My
take on connection pooling is that you open a small number of sessions
to the database and all users connect to a middle tier which decides
who connects to the database. Am I correct? I have some questions
about how this affects oracle.
- Do you need to commit after every sql statement? If there are just
a few sessions open and another user comes in. He commits, your data
will be committed anyway. if so doesnt this kill recovery with all
sorts of bad data problems and inconsistencies? Perfomance must be
impacted also right?
- In shared server you really want to use very short transactions due
to the fact that there are only a few connections to the database. Im
assuming the same is true for conneciton pooling?
Any comments would be appreciated.
Received on Fri Dec 12 2003 - 12:48:07 CST
