>I get an error:This is typical of the MySQL daemon aborting (as in segfault).>"Error 2013 problem, Lost connection to MySQL during query" and the MySQL
>service stops when I run an SQL statement:
>"SELECT * FROM mytest WHERE NameFirst is Null AND NameLast is Null AND
>Geslacht_ID is Null".
You've hit a bug somewhere. It might be tickled by corrupted data
or schema, but the daemon isn't supposed to die like that.
If you can isolate the problem (start off with a fresh, clean database,>There are 2 indices: NameFirst + NameLast and NameLast.
>The strange thing is, when I remove one of the indices, or change the SELECT
>statement into anything else I don't get the error and the MySQL keeps
>For example, the following almost identical SQL statement doesn't give me
>"SELECT * FROM mytest WHERE NameFirst is Null AND NameLast is Null"
>Also, at the bottom of MySQL Query Browser it says "Cannot fetch table
>information" when this problem occurs.
>Anyone any idea what is the problem?
create and load up your tables, then run the query and have it fail),
report it as a bug. Are you running the latest version? Upgrading
might fix it.
Gordon L. Burditt