On Tue, 2008-01-22 at 11:23 +1100, Chris wrote: > > Why is it saying 'Impossible WHERE noticed after reading const tables'? > > http://dev.mysql.com/doc/refman/4.1/en/explain.html > MySQL has read all const (and system) tables and notice that the WHERE > clause is always false. > > ie - no rows match that query and so there's nothing to 'explain'.
There must be a problem then. In this particular example, there were 3773 records returned by this select. > I'd suspect that the time is spent trying to check or clean up the > foreign key reference. Are there lots of locations with that id in the > tlocations table? 1 > I'd also assume that since it's named 'id' it would be > a primary key (and indexed) ? Indexed, yes. I'll go ahead with that restore from a backup tonight. -- Daniel Kasak IT Developer NUS Consulting Group Level 5, 77 Pacific Highway North Sydney, NSW, Australia 2060 T: (+61) 2 9922-7676 / F: (+61) 2 9922 7989 email: [EMAIL PROTECTED] website: http://www.nusconsulting.com.au -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
