I'm just using DBD::mysql, which should be the best
thing for the job. Further, the program doesn't even
make it into the loop, as the 'print' diagnostic
I have in the code doesn't report back. Instead,
a HUGE amount of data is sent from the MySQL server over
TCP/IP to the Perl process, which happily gobbles it up
into RAM.
ichimunki's idea of the brackets for the my declarations
was interesting, but produced no effect. I even removed
the error checking from $s->execute() and there was no
change.
The only solution (read: hack) that I came up with is to
limit the query to managable chunks:
SELECT * FROM table LIMIT ?,?
Then iterate through the entire table in LIMITed chunks.
This is not the fix I was hoping for.
-
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.
|