I am currently running nightly 4654 and since the last few nightlies the auto complete does not provide any table specific completions. All I am seeing is built-in Mysql functions and the names of the databases. But no table or column names.
When selecting the database on start, the escape key shows the familiar 'fetching structure...' in the context menu. But later any partial completion attempt results in 'No item found'.
I just checked in the stable build 188.8.131.52. The autocomplete works fine there.
Works fine for me with 4655.
Did you recently update mysql?
Also open Console.app and look for messages from Sequel Pro.
I've been having this same issue for a few months now. I'm on the latest nightly 4656 on OSX. I've recorded the screen so you can better understand what the problem is:
OK, this seems to be related to the MySQL server version.
Tested it on localhost on MySQL 5.6.23 and am having the same issues.
OK, then it is probably that it works for the database that is set in the connection dialog.
Having the same problem, for what it is worth. Have been for quite a while. I had to move to nightlies at some point becuase of a bug, I think, with connections over ssh on 10.10 or 10.11, I can't recall. But for a long time this problem has been there, and I thought it might have been a misconfiguration on my part so I didn't complain as I didn't see anyone else with it. So now I will simply say there is naother case out here. :)
Also can confirm dmoagx's comment... If I put the database name in the connection dialog then autocomplete names show up properly for that database.
Fix an issue where auto completion in query editor would not work in …
…some cases (#2406)
Issue introduced in 0b9fb7e
Please try the new nightly build (efe4c9e).
Tested it and it seems to work. Great job. Thanks!
Issue fixed in 1.1.1
Is this broken again? Auto-complete in the latest nightly release (a00f27fda) doesn't work for me (even with the database name supplied in the connection dialog), but the last release version v1.1.2 does work (even without the database name in the connection dialog). I hope this isn't just a mistake here, but thought I would re-visit this bug report.
Hm, this seems to be a different new issue. See #2507