Exasol schema introspection

HI,

I am wondering if anyone else is having troubles with unresolved tables in Datagrip 2016.3.2?

Setup:

Schema:

Unresolved references:



Exasol driver: 5.0.17

 

 

 

 

0
9 comments

Hi,

Could you make a screenshot of your data source settings Options tab?

Example:

0

Options screenshot:

It is interesting that objects that are created from now on are resolved ok. I tried to invalidate caches but it did not help for older tables. Another issue that arises with this specific connection is that each time a first query is issued I have to provide the password despite the remember option is checked.

I have notice that there are some problems with duplicate recent projects too but probably this is a different issue:





0

It seems that something is messed up. Now I even cannot connect to exasol db (cannot attach connection to a file):

 

0

Hi,

You need to change dialect for your tmp.sql file.
To change dialect press `Shift Shift` and type `sql dialects` and select Generic dialect for your SQL file.




Also, you can attach folder with your SQL files to your project and change dialect from right click context menu.

0

Perfect, that solved both problems (introspection + file connection problem).

Do you have any tips how to solve a non-remembered password and duplicate recent projects?

Thank you

0

Hi,

Could you provide steps to reproduce for password loss? 

Thank you.

0

Yes sure. Same behaviour I think I noticed on postresql connection.

 

 

 

0

What do you have in data source settings?

0

0

Please sign in to leave a comment.