We have our own application server built on mod perl and the template toolkit. Most of the application specific sql queries all run as a single user which is great for Apache::DBI. Every end user also has 3-4 tables they can query (using the template toolkit DBI plugin) using their own username, and for I do not want to use Apache::DBI because it results in too many cached connections.
Other than hacking DBI.pm and adding our own disconnect function which won't be overriden by Apache::DBI, does anyone know of a better way to have both cached and non cached connections in the same apache/mod perl process? Chris -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
