Bug #587 user table query only returns one row
Submitted: 4 Jun 2003 12:29 Modified: 30 Jun 2003 10:17
Reporter: Edward Walter Email Updates:
Status: Closed Impact on me:
Category:MySQLCC Severity:S2 (Serious)
Version:0.9.2-beta OS:Windows (XP Pro)
Assigned to: Bugs System CPU Architecture:Any

[4 Jun 2003 12:29] Edward Walter
Running MySQL version 4.0.13-nt
Can add users to the user table in the mysql db using MySQL Control Center.
When the user table is queried, only one row, the generic localhost/root record is returned.
Manually typing the query produces the same result... 1 record returned.

Querrying the user table from phpMyAdmin shows that the rows are being inserted into the user table.  Edits to the localhost/root record in the user table using phpMyAdmin do show up in the result set from MySQL Control Center.

I stopped and restarted the db several times in testing this and also manually flushed the tables several times.  It never returns more than one record, and always the same record.

How to repeat:
Install MySQL 4.0.13 and MySQLCC 0.9.2.  Connect to the mysql database on localhost and try to creat new records in the user table.
[9 Jun 2003 7:52] Martin Purdy
CONTROL CENTER will not return records if there is more than one record in the table

the error

[Local] ERROR 1104: The SELECT would examine too many records and probably take a very long time. Check your WHERE and use SET OPTION SQL_BIG_SELECTS=1 if the SELECT is ok

continually occurs even if the option is set via SQL or via the SQL options
[30 Jun 2003 10:17] Jorge del Conde

This bug was fixed in 0.9.2.  The reason why you're still experiencing this in
0.9.2 is because MySQLCC is using the "buggy" server configuration files which
where created by 0.9.1.  To fix this, edit the server properties, to the "MySQL
Options" tab and change the "Max Join Size" option to 1000000 and change the "Limit Records" option to something more reasonable like 1000 or to "Unlimited".  You can also
delete the server and create a new one and that will fix the buggy default
values introduced in 0.9.1

Thanks for the bug report