New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto complete does not bring up contextual completions when triggering with shortcut #2406

Closed
shoan opened this Issue Feb 15, 2016 · 11 comments

Comments

Projects
None yet
4 participants
@shoan

shoan commented Feb 15, 2016

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 1.1.0.1. The autocomplete works fine there.

@dmoagx

This comment has been minimized.

Show comment
Hide comment
@dmoagx

dmoagx Feb 15, 2016

Member

Works fine for me with 4655.
Did you recently update mysql?
Also open Console.app and look for messages from Sequel Pro.

Member

dmoagx commented Feb 15, 2016

Works fine for me with 4655.
Did you recently update mysql?
Also open Console.app and look for messages from Sequel Pro.

@phantasma2983

This comment has been minimized.

Show comment
Hide comment
@phantasma2983

phantasma2983 Feb 16, 2016

Hey,

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:
https://www.dropbox.com/s/r311eaox8dj7kzj/SequelPro_autocomplete.mp4?dl=0

Thanks,
Daniel

phantasma2983 commented Feb 16, 2016

Hey,

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:
https://www.dropbox.com/s/r311eaox8dj7kzj/SequelPro_autocomplete.mp4?dl=0

Thanks,
Daniel

@dmoagx

This comment has been minimized.

Show comment
Hide comment
@dmoagx

dmoagx Feb 16, 2016

Member

OK, this seems to be related to the MySQL server version.

Member

dmoagx commented Feb 16, 2016

OK, this seems to be related to the MySQL server version.

@dmoagx dmoagx added Bug and removed WaitingOnUser labels Feb 16, 2016

@phantasma2983

This comment has been minimized.

Show comment
Hide comment
@phantasma2983

phantasma2983 Feb 16, 2016

Tested it on localhost on MySQL 5.6.23 and am having the same issues.

phantasma2983 commented Feb 16, 2016

Tested it on localhost on MySQL 5.6.23 and am having the same issues.

@dmoagx

This comment has been minimized.

Show comment
Hide comment
@dmoagx

dmoagx Feb 16, 2016

Member

OK, then it is probably that it works for the database that is set in the connection dialog.

Member

dmoagx commented Feb 16, 2016

OK, then it is probably that it works for the database that is set in the connection dialog.

@n9yty

This comment has been minimized.

Show comment
Hide comment
@n9yty

n9yty Feb 16, 2016

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.

n9yty commented Feb 16, 2016

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.

dmoagx added a commit that referenced this issue Feb 17, 2016

dmoagx added a commit that referenced this issue Feb 17, 2016

@dmoagx dmoagx added this to the 1.1.1 milestone Feb 17, 2016

@dmoagx

This comment has been minimized.

Show comment
Hide comment
@dmoagx

dmoagx Feb 17, 2016

Member

Please try the new nightly build (efe4c9e).

Member

dmoagx commented Feb 17, 2016

Please try the new nightly build (efe4c9e).

@phantasma2983

This comment has been minimized.

Show comment
Hide comment
@phantasma2983

phantasma2983 Feb 17, 2016

Tested it and it seems to work. Great job. Thanks!

phantasma2983 commented Feb 17, 2016

Tested it and it seems to work. Great job. Thanks!

@dmoagx

This comment has been minimized.

Show comment
Hide comment
@dmoagx
Member

dmoagx commented Feb 20, 2016

@n9yty

This comment has been minimized.

Show comment
Hide comment
@n9yty

n9yty May 12, 2016

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.

n9yty commented May 12, 2016

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.

@dmoagx

This comment has been minimized.

Show comment
Hide comment
@dmoagx

dmoagx May 16, 2016

Member

Hm, this seems to be a different new issue. See #2507

Member

dmoagx commented May 16, 2016

Hm, this seems to be a different new issue. See #2507

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment