comment on

I'm running a mod_perl program on Apache (where else?), and it uses Apache::DBI and DBD::mysql to connect with my database. In this database I have a table of "quotes", and I use the following code to attempt to select a random one.

my $sth = $state->{'DBH'}->prepare('SELECT quote,author FROM quotes OR
+DER BY RAND() LIMIT 1');
$sth->execute;
my $row = $sth->fetchrow_arrayref;
$sth->finish;
[download]

It seems to consistantly select 1 quote for each thread that apache is running, and those are the only quotes I can get out of it through normal use. Simply going in and executing that statement from a terminal yields different ones almost all the time. When there are 80 to choose from, and 3 threads (non-production server), it pushes probability that I could consistantly get only the same three quotes. Does Apache::DBI, DBI, DBD::mysql or MySQL itself cache responses?

My code doesn't have bugs, it just develops random features.

Flame ~ Lead Programmer: GMS (DOWN) | GMS (DOWN)

In reply to Apache::DBI, DBI, DBD::MySql and MySQL cache? by Flame

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.


The stupid question is the question not asked
	PerlMonks