Database console folder name gone after last update

After the last update. Under the file table - > Scratches and Console - > Database Consoles, The folder names are replaced with hashes instead of names. Totally confused.

Please can you suggest a workaround.

 

If this helps,

DataGrip 2017.3.5
Build #DB-173.4652.2, built on February 14, 2018
JRE: 1.8.0_152-release-1024-b11 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0

16 comments
Comment actions Permalink

Same thing happened to me. These are the folder names the console files are stored in which are under the \config\consoles\db folder. I tried renaming one of them  to try and get it back to what it was using the refactor->rename functionality and it just disappeared from the view.

Only work around I can think of is to re-name the console file so you know what data source it is for or just use scratches and attach them to your data source as needed.

It looks like they've already flagged it as fixed for a future release.

https://youtrack.jetbrains.com/issue/DBE-5904

0
Comment actions Permalink

Hello; when can we expect the next update? Within the week? Or should I roll back to previous version until it's resolved.


Thanks in advance!

0
Comment actions Permalink

We will do our best to release it tomorrow, Feb, 23.

0
Comment actions Permalink

Hi Maxim,

I got an update today. Installed it but did not help at all. Still, there are no names (only GUIDs). How can I revert back to DataGrip 2017.3.4?

Done with this thing,
DataGrip 2017.3.6
Build #DB-173.4652.3, built on February 22, 2018
JRE: 1.8.0_152-release-1024-b11 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Windows 10 10.0

1
Comment actions Permalink

Same here Jay!


But I have faith that we'll get a fix soon. :)

Same build but on a Mac (at work); haven't tried it home since I didn't update to the faulty build.

0
Comment actions Permalink

Yep, same here. Updated today but it's still not fixed and it actually wasn't mentioned in the update description i think. Any ETA when it's going to be pushed out?

Thanks.

0
Comment actions Permalink

Hello to everybody! We apologize for the mistake: this fix appeared only in 2018.1 EAP.

We are going to release 2017.3.7 on Monday with this fix.

0
Comment actions Permalink

Thank you for fixing this :)

0
Comment actions Permalink

Christoffer which version are you using. Is it windows or mac?

 

I can confirm, I did not receive any update yesterday (Monday) or today (Tuesday).

 

0
Comment actions Permalink

Jay; I am using the EAP until the stable release is working :)

0
Comment actions Permalink

I am sorry, Jay, we faced additional problems. I wrote Monday because I really hoped to do this. We're doing our best and it is very high probability, that it will be released on Wednesday. I will not promise, because I have spent one promise already.

As a workaround untill that moment you can use EAP or 2017.3.4 version, which can be found here: https://confluence.jetbrains.com/display/DBE/DataGrip+previous+releases

 

 

0
Comment actions Permalink

Thank you, Christoffer, for sharing the details.

Thank you Maxim. Reverting back to 2017.3.4

0
Comment actions Permalink

Thank you, Maxim, for your efforts. I really appreciate it. 

It is fixed in today's update my colleague just confirmed.

0
Comment actions Permalink

Yes we've just released 2017.3.7 with the fix: https://blog.jetbrains.com/datagrip/2018/02/28/datagrip-2017-3-7/

Thanks to everybody for your patience! 

0
Comment actions Permalink

Yep, thanks, it fixed the issue.

0

Please sign in to leave a comment.