This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.
Subject: Data persists after table drop w/MySQL From: Andrew Waegel <asw@benevolent-tech.com> Date: Wed, 20 Sep 2000 16:36:08 -0800 Hello, I'm noticing a weird problem with DBI::DBS 1.13 and MySQL. I drop and redefine a table by reading a text file into the mysql terminal program, which gives no errors. I re-access the database via a small CGI application and the -old- data appears. I connect to mysqld on the command line, and the new data is there. I restart mysqld, and the new data/schema is available to the CGI script. What am I missing? Is this just a mysqld table caching problem? Docs didn't seem to address this. This is plain perl on Solaris, not running under mod_perl. === Subject: Re: Data persists after table drop w/MySQL From: Andrew Waegel <asw@benevolent-tech.com> Date: Thu, 21 Sep 2000 10:14:33 -0800 Solved my own problem with mysqladmin flush-tables. I was amazed how much data mysqld cached... - Andrew ===