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
In reply to Re^3: SQL::Statement confusing literals and identifiers
by grinder
in thread SQL::Statement confusing literals and identifiers
by ikegami
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |