Hi. On Mon, May 20, 2002 at 03:15:44PM -0400, [EMAIL PROTECTED] wrote: [...] > > > SELECT * FROM table1,table2 WHERE table1.name = table2.name; [...] > > Else, try to create a test case. I.e. try to create a minimal set of > > SQL commands which will produce the strange behaviour in order to > > enable us to verify the behaviour. > > > > Creating a test case will also help, if it should be an usage error, > > as you will learn better what happens. > > I'm not sure what you mean; do you mean running more basic commands? > I did a generic SELECT * from each table, and they come out just > fine.
Well, the short (for me :-) answer is: http://www.mysql.com/doc/N/o/No_matching_rows.html http://www.mysql.com/doc/B/u/Bug_reports.html The longer answer is: I meant, try to make a complete set of commands which will enable us to run your query on our systems. In this case, this means the CREATE TABLE commands, some INSERTs to fill the tables with basic data and the SELECT. Run that on your system to be sure that you can reproduce the error with the reduced command set. In more detail (be sure to read through, before doing it in real): First, make a backup of the tables in questions. A good point to start with is IMHO mysqldump to create a full dump of the tables in questions. Change their names. Re-import (mysql utility) the tables. Adapt the SELECT (for the new tables names). Does the error still occur? If yes, remove most of the records. Re-import. Does the error occur? If yes, remove all columns not used in the query (easier with ALTER TABLE DROP ...). Re-import. Does the error occur? If yes, you have a minimal set of SQL commands to reproduce your problem. You should add a SELECT VERSION(), so we can see your MySQL version. Send that to the list, including the output of the run on your system and an short explanation of what you would have expected instead. If you have to answer "no" at any of these stages, you have learned something about your problem. Go one step back and re-try. You should see the problem again. Then follow the step again, but do not remove as much as the first time (i.e. not all unused columns, but only a few) and re-iterate until you have identified the step that makes the difference. Maybe you have learned enough about the problem to fix it yourself now (if it was usage error). Or else, send in the test case as described above (if small enough). Else, describe what change seem to matter. If you cannot reproduce the problem by simply dumping and re-importing the whole table, the tables are somehow corrupt. Your fix is to simply use the re-imported tables (as there is no problem anymore), but the MySQL developers are probably interested to have a look at the corrupted table, so keep us informed anyhow. I hope that answered your question. Please also read (at least glimpse) the manual pages I cited above. I know this is all a long read, but without the proper information, there is nothing we can do about your problem. Bye, Benjamin. -- [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
