updated data not visible on second connection?

David Nicol <[email protected]>
Newsgroups gmane.comp.db.mysql.perl
Message-ID <[email protected]>
AFAIK I am not using transactions; autocomit is on, i got an error
when I tried commit().

The problem is, a second identical SELECT produces the same results as
the first,
even after a change has been made to the row in question, from a
different connection.

Changes made from the same connection are visible, and changes made from
the second connection become visible if I open a new connection.

I guess I just have to open new connections all the time?  Is there a way to
have current data only with a persistent perl DBI connection? 

 Cloning the $dbh doesn't give me revised info

Neither does making a new connection.

I'm using ActiveState perl 5.8 and MYSQL DBD version 2.9004 installed from ppm
for the first connection and the mysql graphical admin tool for the second.

I have also tried setting the RowCacheSize=>1 attribute on the connection, and
calling finish on the sth between queries, neither of those worked either.





-- 
David L Nicol
"You don't know how to maintain a station wagon either!"

-- 
MySQL Perl Mailing List
For list archives: http://lists.mysql.com/perl
To unsubscribe:    http://lists.mysql.com/[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.