Well...

• Approx 1.25 seconds; caching the compiled templates took it down to approx 1 second.
• yes
• no
• no, I'm use .item when working with nested hashes
• Now that's something I didn't know. The main data section has nested loops four-deep. Column order is defined in a config file, so we do something like this:

      [% FOREACH set IN [data_header.top_priority,
                         data_header.middle_priority] %]
      [% FOREACH fieldno IN set %]
      [% field = data_header.field.slice(fieldno, fieldno).0 %]
      [% value = order.item(make_key(field.title))
      ...
  [download]

  Which probably isn't very nice to the TT processor.
• I wasn't, but I am now.
• No, calls to the database are made through callback functions.

---

---

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.