in reply to named placeholders in DBI
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,
_____________________
"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."
For example,
In this specific example the query would be:# 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);
Introducing placeholders here may not be as useful or productive as say in a case where you build your SQL query 'manually'. ;)INSERT INTO user(first_name,address,last_name,phone) VALUES(?,?,?,?)
_____________________
"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
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Re: named placeholders in DBI
by simonm (Vicar) on Sep 22, 2003 at 21:25 UTC |
In Section
Meditations