Bob,
I agree there are inherit limitations and better ways to pool
db connections. Any decent middleware package would probably
handle these problems very easily.
I just thought that some people may have found simplier ways to
realize the benefits of pconnect and reduce some of the side effects.
I
Hi Brian
Why don't you just avoid using sybace_pconnect() with transactions?
I use ODBTP to connect to SQL Server and Sybase databases, and this is not
an issue. The reason is because ODBTP involves the use of a mediating
service that pools all connections, and automatically rollbacks
transactio
On transactions, no this is my biggest concern. Say a php script
performs a
"begin tran" then aborts early due to an error (user error for
instance), but
the script error handling fails to rollback the transaction before it exits.
Just 1 poorly coded script.
Now the begin tran is still open, th
The biggest problem I've had with persistent connections is the problems
that arise when the connection goes down. You have to monitor the
connection status anyways (and reconnect on a failure), so it was
usually easier to just connect every time. I don't know if this is
specific to sybase. You
I've been using PHP4/5 and Sybase for several years, using standard
sybase_connect. Today I tried playing around with pconnect to get
aquainted.
I expected one simple condition of a "use database" from one web page
affecting another, and easilly handled that with a connection wrapper that
re-use
