If you need to access the values of the returned columns individually, then you will have to push the results onto arrays, and then print them out afterwards with something like print( join( '|', @column ), "\n" ).

On the other hand, if you don't need to do this, you could just concatenate to strings, which will be far cheaper in terms of memory consumed.

# assuming $sth is your SQL statement under DBI $sth->execute(); my @columns; for( @{$sth->{NAME}} ) { push @columns, $_; } while( my $r = $sth->fetchrow_arrayref ) { my $index = 0; for( @$r ) { $columns[$index++] .= "|$_"; } } print "$_\n" for @columns;

update: rewrote the code to follow the spec. (Wasn' t paying attention :).


print@_{sort keys %_},$/if%_=split//,'= & *a?b:e\f/h^h!j+n,o@o;r$s-t%t#u'

In reply to Re: DB SQL Result Order by grinder
in thread DB SQL Result Order by johnirl

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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! —
  • 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:
    & &amp;
    < &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.