This is of course true unless you are dealing with an automated process of building your queries from predefined perl structures. This would especially apply to building insert queries where data to be inserted is stored in a convenient perl hash (with keys being the fields and values being the corresponding field values :).

For example,

# a new record to be inserted
my %user_rec = (
                first_name => 'Foo',
                last_name => 'Bar',
                phone => '12345678',
                address => '123 Foo St',
                );

##
## . . . some code here . . .
##

# possibly somewhere in an add_db_user() sub
# ...
my @fields = keys %user_rec;
my @values = @user_rec{@fields};
my $placeholders = join(",", ("?") x scalar @fields);

my $sql = sprintf(qq~
                INSERT INTO user(%s) VALUES(%s)
                ~, join(",", @fields), $placeholders);

my $sth = $dbh->prepare($sql);
$sth->execute(@values);
[download]

In this specific example the query would be:

INSERT INTO user(first_name,address,last_name,phone) VALUES(?,?,?,?)
[download]

Introducing placeholders here may not be as useful or productive as say in a case where you build your SQL query 'manually'. ;)

_____________________
"We've all heard that a million monkeys banging on a million typewriters will eventually reproduce
the entire works of Shakespeare. Now, thanks to the Internet, we know this is not true."

Robert Wilensky, University of California

---

---

• 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.