I use an embperl program to make a small change to a MySQL database. The program performs the following steps:
Connect Lock tables Select My Select statement had a bug in it, so the server returned an error message. I cleaned up the bug, transferred the program to the server and ran it again in the browser. I was expecting the program to rerun. Instead the browser just hangs. I terminated my browser and started it up again and re-ran the embperl program and then I get DBI error messages about Locks. I appears as though the database still has locks from the first time. To solve this I have to contact the server manager who kills the process (I don't have the privilege) or wait for the process to time out. Can anyone explain what is going on and what are my options? Should I programmatically turn off the DBI persistence while I am developing/testing and turn it back on for production (and how would I do that?) Apache/1.3.12 (Unix) (Red Hat/Linux) Embperl/1.3.3 mod_perl/1.24 Thanks, Jim Jim Hamer Downtown Data Processing Inc. (416) 489-3298 home and office [EMAIL PROTECTED] Toronto, Ontario, Canada http://webhome.idirect.com/~jhamer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
