Persistent connection issues

[Anon]

There's been a lot of discussion about xx_pconnect() recently. Most of this has focussed on the ill effects on the servers (both the dbms and apache), but I wanted to come up with a list of things that might be visible to the programmer. Here's what I've got so far; what am I missing?

1. TEMP tables don't go away at the end of the script.

2. You can find out somebody else's last-insert-id (requires malicious or buggy php code, of course.)

Anything else?

[[deleted]]

One thing that's not really pconnect related but bloody annoying nontheless:

PHP's connection-pooling makes it so that if you open two connections to the same database using the same credentials, you will get the same connection identifier twice. So you can start a transaction on the first 'connenction', and close it using the second 'connection'.

I have not been able to get this behaviour to work through pconnect with two different scripts, but that may be because I'm such a terrific programmer :-)...and modestg too.

[smarlowe]

I think this is another place where a transactional oriented application (not just the dbms, but the web app you write on top needs to be aware of what it's doing) can really help.

If you create temp tables withing a transaction, the close of the transaction kills them instead of the close of the connection.

Basically I think if you're gonna use persistant connects, you need to write all your code that creates temporary data and requires a "clean" environment should be in a begin/end pair.