comment on

Of course, I'd love to have comments on individual bits of the code - but ...

You're in luck! :)

Error handling, error handling, error handling. In particular, use {RaiseError = 1} when you're connecting to the database to tell DBI to check and report errors for you. That alone can save lots of grief.

You can refactor some of the database calls, by preparing them once, then binding/executing when you need to invoke them. See (Ovid) Re: DBI placeholders for hints.

In reply to Re: Re-Factoring: Philosophy and Approach by dws
in thread Re-Factoring: Philosophy and Approach by George_Sherston

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Just another Perl shrine
	PerlMonks