Beefy Boxes and Bandwidth Generously Provided by pair Networks
Problems? Is your data what you think it is?
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
First, you should be using a placeholder in the query string, and preparing the query statement outside the foreach loop. Second, you can either include a "LIMIT 2" clause at the end of the query string, as suggested above, or you can simply exit the inner "fetch" loop after doing two rows (but using the LIMIT clause would probably be more efficient, assuming your database server supports it).

Regarding the placeholder usage, it would go like this (and I'm throwing in both the LIMIT clause and a counter for the inner fetch loop):

my $sql = "SELECT G.Region, G.Score FROM Gov_regions_scores_TEMP G, Re +gion_lookup R WHERE R.String = ? AND RTRIM(R.Place) = RTRIM(G.Region) LIMIT 2"; my $sth = $dbh->prepare( $sql ); foreach ( @regions_A_array ) { $sth->execute( $_ ); for ( 1, 2 ) { my @regions_A = $sth->fetchrow_array; print OUTPUT "@regions_A\n"; } } $sth->finish();
I don't have a means for testing that, but it should be pretty close to what you want. (If it doesn't work, show us exactly how you tried it, what error messages and output you got, if any, and what output you expected.)

In reply to Re: Returning two records with SELECT statement and then printing to file by graff
in thread Returning two records with SELECT statement and then printing to file by Win

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



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others cooling their heels in the Monastery: (4)
As of 2024-04-18 05:02 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found