Prayer comes to mind. (What else did you expect at the Monastery? ;-)

Seriously, here's a few tips.

• Try to break it up into pieces. Even if it's not in subs, make a copy of the original, and start ripping out lines. Once you have some manageable chunks, you'll be able to figure it out more easily.
• Make a version that doesn't do any database calls at all. You don't mention whether it's using DBI; in any case, it has to be calling something to execute SQL. Substitute an "execute_sql" routine that just prints out the string that was passed in.
• Learn to use the Perl debugger real well real fast.... Use it to test expressions you don't understand by typing them in and seeing what they do.
• Personally, I wouldn't bother with the UML diagrams. They're great for design, but I've never found them useful for reverse engineering. But that's just me.

Prayer may not be a bad idea, actually....

HTH

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.