Autocomplete not working correctly after 2017.1 update Follow
Completed
Myself and several of my co-workers upgraded DataGrip to 2017.1 this morning. Since the update the autocomplete functionality is only returning the names of sequences for our tables but not the table names themselves. It is not showing views or functions either, just the sequence names. Is there something that needs done for this to work in 2017.1?
You can see below where it is only returning the name of the sequences, we have a table named "dg_people" that should be showing up.
We are connected to a v9.6.1 Postgres database, have the schema the table lives on selected in the Data Sources and Drivers->Schemas tab, and have "Synchronized" the schema several times.
Please sign in to leave a comment.
I am having similar issue after upgrading to 2017.1. Only tables and views are showing up not functions, procedures and other objects.
I'm also having the same problem after upgrading to 2017.1, but in my case only the tables are showing up, all the rest as the functions and views are not being displayed, even i had "Synchronized" the schemas several times too, We are connecting to a DB2 database.
I uninstalled and 2017.1 version and installed 2016.3.4 version and it's working fine. Definitely something has changed in 2017.1 version. I will stay on 2016 version until they fix the 2017 version
Hi,
What tables do you expect to see?
Did you add schema with the table?
Thank you.
P.S.: Also try to invoke Forget Cached Schemas from data source context menu
Autocomplete of functions and stored procedures working fine for the current database schema (i.e.: public in PostgreSQL), but not working for another database schemas.
@Sergie Inv Hi,
Have you added mentioned schemas to your data source?
E.g. in my Postgres data source I'll have autocomplete only for objects from public schema
Thank you.
I am using Datagrip 2017.3.3. Code completion doesn't work at all. I have tried 'forget cached schemas' and have added all the schemas to my data source.
I'm using
DataGrip 2017.3.4
Build #DB-173.4301.31, built on January 17, 2018
JRE: 1.8.0_152-release-1024-b11 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Mac OS X 10.12.6
All shcemas are selected for my database (PostgreSQL 9.6.5 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-9), 64-bit)
And in autocompletion I see only system functions and no user defined functions AT ALL!
I cleaned the cache (dropped cache and index folders in ~/Library/Cache/DataGrip..) with no sucess.
Is there already an issue in YouTrack to follow?
Thanks!
>>Is there already an issue in YouTrack to follow?
It's probably related to memory issues which seem to happen when too many consoles are open and/or there is too much text in one console. However, auto-completion doesn't work brilliantly even at the best of times.
With 2017.1, mb even with 2017.2 it was just fine.
I also see Java auto-completion stopped working after an upgrade (in my case to 2017.3.4)
I reverted back to 2017.2.6 and all is well again.
Creating a function and selecting from it works if I run it, but give me errors on the editor:
Uri Goldshtein,
Could you try to update to DataGrip 2019.3.2?
It should fix the issue:
Thank you vasily chernov but it behaves the same using the latest 2019.3.2
I'm on a Mac, I was using Postgres 11 and now upgraded to Postgres 12.1 but still the same issue.
Uri Goldshtein,
Do you work with the same SQL script that is in the example above?
Also, but also with many other functions I use every day.
This is a big show stopper for me currently!
The same problem v. 2019.3.3
Uri Goldstein,
I filed an issue https://youtrack.jetbrains.com/issue/DBE-10119
Thank you
Uri Goldshtein,
The fix will be available in the nearest DataGrip 2020.1 EAP.
Thank you very much.
I couldn't find where to download the EAP, could you please point me to it?
or if it's not released yet, do you know if there is an estimate release date?
We released 2020.1 EAP https://blog.jetbrains.com/datagrip/2020/02/27/we-open-eap-for-datagrip-2020-1/
Thank you, I can confirm it is fixed on 2020.1 EAP