You can eliminate webserver/browser/caching issues from consideration by trying your query directly in the mysql client.

Are you using InnoDB and transactions? It sounds to me as if you deleted the record but have not yet committed. In that case, the deleted record will be gone for the client which started the transaction, but will still be available to all other clients until you commit.

Michael

Amer Neely wrote:
Brian Reichert wrote:

On Sat, Sep 04, 2004 at 02:40:20PM -0400, Amer Neely wrote:

My question is, in my admin script I deleted a record, but it still shows up using the other script. The admin script shows 102 records and the other shows 103. The record does show up in the 'public' script, so it's not just a mis-count. How is this possible? Is there a step I'm missing because I'm using 2 different scripts to access the same tables? That doesn't make sense. Can someone shed some light on what might be happening here?



Web caching? Flushing tables after your delete?


I just checked the database with phpMyAdmin. The record I deleted through my script is still there, but doesn't show up in a query for it. Tried to execute the 'FLUSH TABLES' query with phpMyAdmin, but got this instead:


#1227 - Access denied. You need the RELOAD privilege for this operation

So I'll need to see about getting RELOAD privilege I guess. Thanks for pointing in the right direction.


-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]



Reply via email to