I'll look into the code on the PHP side (since I wrote that too). Maybe it is something I did. :)
I may avoid repairing the tables for now, since the missing records have already been re-entered and I don't want to risk anything being duplicated at this point. Perhaps I'll drop all the indexes for now and keep a watch on things. The table is still small (< 5000 records) so reporting speed isn't too much of a problem right now. On Mon, 2002-11-18 at 10:52, Dan Nelson wrote: > In the last episode (Nov 18), Greg Macek said: > > That's the weird part of it. Last week in reviewing the system, > > making sure reports were working I can personally verify his stuff > > was in there (not even logged on as him). This week: nothing. Is > > there any record of 3.23.49 ever having random data loss issues? > > Related to something else on the system? > > Even if there was dataloss, how could you explain not seeing the > entries in the mysql log? I think in this case the query never made it > to mysql. You can always try doing a "repair table" in case the index > got damaged. Also check your log to see if the record was manually > deleted. > > -- > Dan Nelson > [EMAIL PROTECTED] --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
