Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a Perl script for writing data to a MySQL DB, runs fine. Question I have is if there is a proper method to log prepared queries to a local file if the connection to the MySQL DB times out or fails? If the connection fails or timeouts, does the Perl-DBI obj even allow preparing MySQL statements?
Thank you!
Brad
There’s nothing like that built into DBI or the MySQL client. It’s hard to make it work correctly in a generic fashion, too, as many of the edge/exception cases really are application specific.
This sort of thing is also prone to error as you’re doing something relatively complicated only when things are already going badly. If MySQL being unavailable is a common case or it’s too important to stop/timeout/retry in case of errors, see if you can write the data to another stream (always) that is better at handling errors. For example you could push it into scribe on the local server and have another program read the data from scribe and insert/update MySQL. Scribe takes care of the local buffering to disk and such.
Of course that just has different trade-offs in different error scenarios.