Oh duh, silly me, I should have known ikegami would not make a mistake like that. Still, I think SQL::Statement is playing the game correctly. Witness:
use strict;
use warnings;
use SQL::Statement;
my $stmt = SQL::Statement->new(<<END_SQL, SQL::Parser->new);
SELECT id,
gid,
card,
"set",
illus,
num
FROM Print
END_SQL
print join( "\n\t" => $stmt->command, map{ $_->name } $stmt->columns),
+ "\n";
__PRODUCES__
SELECT
ID
GID
CARD
"set"
ILLUS
NUM
Perhaps Print."set" may be advisable. In that case, the output changes slightly:
SELECT
ID
GID
CARD
"SET"
ILLUS
NUM
• another intruder with the mooring in the heart of the Perl
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|