I could hit the db again and set a conditional based on the result. Or I could just stick a flag in a loop. Which one costs the most? I don't even know how to know, except, mythically, to try it both ways with benchmarking, a feature about which I know even less than about debugging.
About which, by the way, I'm pretty frustrated. The times I've tried the debugger it has, understandably, stepped me piece by piece through the included modules, cgi.pm and dbi. I get lost pretty easily there, and can't help thinking, instructional as it will be generally to increase my knowledge of the guts of those modules, it's not as effiecient as the dot-com-bubble-days method of using print statements diagnostically. I confess: I'll feel more like a real programmer when I can make the debugger sit up and beg.
[]
static link
writebacks: 0 (writeback = trackback +/- comment)