Hi all- I'm a pretty frequent user of DBI/DBD, but this is the first time I've stumbled across connect_cached. However, I'm in the middle of a project that could really make use of this feature, and I just wanted to make sure I'm using it safely.
Per the documentation, "Caching can be useful in some applications, but it can also cause problems and should be used with care. The exact behaviour of this method is liable to change, so if you intend to use it in any production applications you should discuss your needs on the dbi-users mailing list". Voila, here I am. :) Anyways, I'm working on a script which reads output from the OpenBSD pflog interface to dump logs to a "master" MySQL database, or, in the case of a dropped connect(), to a local temporary backup. Regardless, I want it to be able to attempt to reconnect whenever possible, without unnecessary overhead (code or cpu), particularly since I'm using MySQL/SSL. connect_cached appears to be the perfect solution. My tests so far confirm the expected behavior, but I'd just like to see if the list has any caveats on applying the method in this way. TIA, -- Jason Dixon Argus Network Systems http://www.argus-networks.com
