Marcus B?rger wrote: > >> However it may be very usefull to terminate any open transaction before > >> reusing a persisten connection. Typically this happens when the same script > >> runs again. But anyway using transactions together with persistent conenctions > >> in a multithreaded environment isn't the best thing you could do. So our > >> options are > >> 1) tell the users to do 'auto commit mode' > >> 2) nested transactions > >> 3) locking > >> > >> >From my perspective 2) and 3) are bad ideas for the web environment. In other > >> words i guess we should leave it as is with transaction rollback only when the > >> client terminates (e.g. the webserver stops). > > BM> I don't see why you wouldn't just do BEGIN;COMMIT;RESET ALL; when you > BM> pass the connection to a new client. > > > Bruce you said RESET ALL is available since 7.2. I am currently checking for > the lib version but it would be more correct to check something on the server. > So the question what do i check?
We usually use SELECT version(). -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
