Was it the same bug reported?
Wed Aug 30, 2023 8:27pm

I sort of remember some post a long time ago saying I was "bug reporter of the year" or something for finding one.

By named vs number are you referring to the result set returned from the DB?

my $comment_id = $results->[2];


my $comment_id = $results->{'comment_id'};

(I know it's actually in PHP but I haven't touched PHP in over 15 years and couldn't tell you anything besides "it's perl-like-ish" about it these days haha)

Or was it some sort of other request attribute?

  • So the comment error was an off-by-one error - Puckdropper, Wed Aug 30 2023 5:41pm
    Or really it was a "I shoulda use a named attribute, not a stupid number." My documentation showed you reported the bug several years ago. Guess I never got around to fixing it. Time to wake the girls up.
    • Was it the same bug reported?- Erik_, Wed Aug 30 2023 8:27pm
      • Yep. I might have added or removed an attribute or just - Puckdropper, Thu Aug 31 2023 3:44pm
        started counting at 1. If I had just done $results["name"] the bug would have been prevented and the code would have been clearer.
        • I've had that happen before too - Erik_, Sat Sep 02 2023 12:58pm
          I wrote an internal support ticket submitting website for work in C# about 10 or so years ago and did the same thing. The DB results were referenced by index instead of column name so if the select statement changed, things had to be reworked that used the result set directly. Not too much of an issue... more
"Forces act when not restrained" - Puckdropper