By definition, the keys in a hash are unordered.
If you need to work with columns in a particular order, simply create a separate array-variable containing the column names in the order that you need. (Construct this array in the same logic that is building the SELECT statement.) Then, iterate through that array to get each successive column-name, and use that column-name to fetch the data from the hash.
Notice that the order of the columns in the SELECT statement will no longer matter: the only thing that matters is the order of the names in the array.
In the spirit of creating robust, reliable, self-diagnosing code, you should verify that every column-name you’re looking for does, in fact, exist in the row-data hashref. It would be an extremely easy thing to make a “tpyo” here, with the consequence that a column of data would never show up in the output... and, maybe, no one would immediately notice the bug. The code should assert that every single column-name must exist (even if the value is NULL), and, IMHO, should die if it does not.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||