DataGrip Trial - Issues and Concerns (and Feature/Update Requests)

I have been using the trial version of DataGrip for nearly a month now, and I can say that I am pretty much "okay" with it.  It isn't my favorite database management tool, but it's far from the worst one I've used.  I have been using PGAdmin III for several years, but my company is currently in the process of upgrading our PostgreSQL databases to v11, which is no longer supported by PGAdmin III. In fact, PGAdmin III will not even connect to a v11 PostgreSQL server, even after throwing several errors while trying. I've tried using the new PGAdmin 4, but I honestly don't care for it at all, which is why I'm looking into finding an alternative so I can continue managing our databases.

So far, I'm getting used to DataGrip and finding that it can be a really useful tool for managing my databases, and I do actually like it quite a bit. It really seems, however, that this tool was designed for a software developer/programmer rather than a database administrator (luckily for me, I do a bit of both). These annoyances are not necessarily "deal breakers", but they are driving me to look at other solutions. I plan to continue using DataGrip through the evaluation period to see how impactful they are to my daily operations before making a final determination as to whether or not I will be purchasing a license.

I love the fact that with DataGrip I can connect to and manage multiple different types of database servers from a single interface. I actually have to manage both PostgreSQL and MySQL databases, with the occasional SQLite and potentially other types of databases. The database diagramming options appear to be great, although I haven't had a lot of opportunity to really dive into those yet. I've already had reason to use the refactoring tools, and those appear to work very well.

There are, however, a few issues that I've encountered while using DataGrip.  Because I'm still just trying it out for the first time, it is possible that I'm overlooking something, so please feel free to correct me if I'm wrong.  Here is my list, in no particular order:

  1. I've yet to figure out how to check the current value of a sequence (PostgreSQL) directly from the UI without running a separate query.  This is something that I actually use fairly frequently, and the lack of this feature is somewhat problematic. Here is an example of what I am used to seeing in PGAdmin III:

    Note here that I can see all the details about the sequence, including the current (START) value.  Because I'm not only managing our database, but also doing a significant amount of programming against that database, this information can be important when I make a programming error that causes the sequence to do strange things or not get used at all.  In comparison, I've tried a couple of ways to get this information in DataGrip, but without success.  I've tried the options to "Generating DDL to Console", the "Source Editor", as well as the "SQL Generator", but none of them provide the level of detail I am looking for.  All I end up with is the following:

    Notice that it does not show me the current status of the sequence.

  2. In addition to the lack of sequence status details, another "missing" element is the current ACL/permission detail for an object.  Using the sequence above as an example, you can see that, even though DataGrip shows the current ownership, it does not show any of the other permissions granted (or revoked) for the object.  This is apparently true for all objects viewed through the DataGrip UI.  Due to the nature of some of the data in our database, we have set up a number of "security groups" on the server to which our employees are assigned for their job functions.  Ensuring that new database objects have the correct permissions set has caused me headaches over the years, so not being able to see this information at a glance is troublesome to me.
  3. While I definitely like the auto-fill/"Intellisense" feature, it can be a bit overbearing at times. For instance, when I am trying to assign an alias to a table in my JOIN statements, it will frequently pull up keywords, function names, etc. and try to assign those as the alias name (whether or not I use the "AS" clause). For example, I started typing a command of "SELECT * FROM sometable AS a", and the editor automatically inserted "UNION ALL". This can be a real inconvenience as I now have to delete "UNION ALL" (or [CTRL]+[Z]), re-type my "a" for the alias I want to use, then make sure I don't accidentally hit [SPACE], [TAB] or a period, but instead hit the [ESC] key to prevent it from putting in something nonsensical (in the current context).

    EDIT: I did find the option (File -> Settings -> Code Completion) to disable the automatic inserting of suggestions, so this issue is something of a moot point.

  4. It took me some searching to find the options to automatically enclose database object names in quotation marks. Many of the tables, views, functions, columns, etc. in my PostgreSQL database are defined using mixed-case object names, requiring them to be explicitly identified surrounded by quotation marks. While DataGrip will show names in mixed case, it will not, by default, automatically "quotify" the object names. This can be very problematic in my environment. As I said, I did find the option, but it was somewhat buried and not altogether intuitive.

    Even so, this option could use a bit of refining.  For instance, for the sake of argument (not getting into whether or not it's "good database practice"), if I try to create a new object using mixed-case like "MyTable", it does not appear that DataGrip automatically recognizes that it's mixed-case, so it doesn't put the quotation marks around the name.  If I put the quotation marks around it myself, it tries to add extra quotation marks, so I have to delete some out in order to get it formatted correctly.  It seems that it is able to pick up on other queues like spaces or special characters in the object name (like "My Table") to correctly quotify the name, but mixed-case does not trigger such a response from the UI.
  5. I've still not been able to find anything that explains some of the color-coding used in the UI. Specifically, when I update a function or view through the console, I sometimes see the text in the tab turn blue, and sometimes it turns red. I can't seem to figure out what causes this difference.
  6. The automatic save of console windows/files is a bit of a pain. I have a tendency to open up several of these at a time when I'm working on a project, then I have to go back and clean them all up from the "Scratches and Consoles" list. If there is an option to automatically delete them when the tab is closed, I haven't yet found it. Even if there is an option to prompt to save/delete, that would be better than just keeping them "hanging around" indefinitely.
  7. The "Synchronize" feature, while definitely necessary, can be a bit cumbersome. In my opinion, it would be much better if the user had the option to only "synchronize" (or "refresh") the current object (table, schema, etc.), or even just the current database rather than having it go through ALL of the connected databases on the server.
  8. Also with regards to the "Synchronize" feature, I've noted on more than one occasion that using this has caused DataGrip to completely "freeze up". To be fair, this usually happens when I've started a synchronization, then made some change to an object, then started another synchronization, all within less than a minute. I've seen some of the discussion posts that recommend turning off the "Auto Sync" flag for the DataSource, and this seems to have helped some, but I do still see this happening from time-to-time.
  9. Modifying a date field in my database by trying to just type in the date immediately pulls up the DatePicker box, preventing me from typing more than one character without closing out the DatePicker. While this is certainly useful in some situations, if I'm typing into a date field, I probably don't want the DatePicker to pop up.

    I would rather have a button inside the date field that I can click to pop up the DatePicker if I choose, but otherwise, it just accepts my typing into the field without that box.
  10. When using a console, it seems that the console window will sometimes forget the database/schema to which I want to send the query/command, resulting in errors about cross-database queries. I was finally able to find the little option at the top of the console window that allows me to select a database/schema, but that option is somewhat hidden and not very well documented.  I frequently have to switch between databases (and schemas), so being able to switch this on the fly is nice, but I've noted that it sometimes seems to "forget" which one I was using last.
  11. When setting up a new DataSource, there is a checkbox option for the user to save the password. Leaving this unchecked during the initial connection tests and such correctly prompts for the password, but there's apparently a second "Save Password" checkbox in that prompt dialog. It seems I missed that when I reconnected to the database and my password was saved by DataGrip because I'm no longer prompted.

    In my opinion, it would be better if the prompting dialog would respect the option in the DataSource setup dialog. If the user THEN decides that they want their password saved, they can check that box and continue without interruption. Otherwise, the application will continue to prompt for subsequent connections.

  12. I believe I've seen an option for what text to display in the tabs when connected to multiple objects, but I can't remember where at this point. The issue, though, is that this text can get SO long that certain open objects are hidden and it can be difficult to find them. I realize there is a drop-down at the end of the line, but I think a left and right arrow indicator that scrolls through the open tabs (a la Notepad++) would be a much better design for this particular element.

  13. I have not found a way through the UI to easily create a Trigger.  In PGAdmin III, this was available in the context menu:

    However, I can find no such option in the DataGrip context menu:

    I've also tried going through the main toolbar menus, but if this option is available through one of them, I still haven't found it yet.
  14. Regarding users (or "roles" in PostgreSQL), there does not appear to be any way through the DataGrip UI to list any groups to which the user belongs.  This is similar to point #2 above in that it does not appear to show any of the ACL definitions for the user.  For example, let's say I have a user to whom I've granted permission for the "Administrators" group.  All I can currently see when I view the definition for this user, either through generating the DDL or the SQL Generator, is the most basic CREATE statement.

  15. Also on the topic of users, I have not yet found a way to create new users through the UI.  Again, perhaps I've missed it, but this seems like it would be an important option to have in the context menu for the "roles" folder.

There have been a few other "quirks" that I've noticed, but these are the main ones that I've run across that have caused me the most issue with DataGrip so far. I'm not sure if these are actually limitations imposed by the data connector being used, or if they are things that simply did not make it into the design phase for this tool.  While some of these things can be "worked around" (i.e., I can create a user through issuing the appropriate SQL command to the database, or I can get the current value of a sequence by using an appropriate SQL query), it feels to me like they should be readily available as an integrated part of the UI.  As I said above, it certainly appears that DataGrip was created with the software developer/programmer in mind, rather than the database administrator.

Even so, I do actually think this will be a useful tool for me going forward, and I'm well aware that there will obviously be something of a "learning curve" involved with making the transition from PGAdmin III to DataGrip.  This is just a list of those things which are making that transition the most difficult. Thank you for your time. Feel free to reach out to me with any questions about the information I've presented here.

Comment actions Permalink
Official comment

Hello, Jeremy! Thank you for the unbelievably detailed feedback.

The first thing I have to say is that we’ll be happy to give you a free one-year subscription for DataGrip because the detailed feedback helps us to make DataGrip better. To get your 100% discount code, please write at Also, you can use this email for any kind of communications with us.

Your main message was “DataGrip was designed rather for developers than for database admins” and we can agree with it. In JetBrains, we have a 20-year experience in creating developer tools and the initial idea of DataGrip was to help SQL developers to do better. Now, three years after the first release of DataGrip, we see that our audience is much wider than “SQL developers”. And we do want to meet the demands of DBAs, analysts, marketing specialists: all those who also deal with SQL and databases.

Let me answer you using the number of paragraphs you used yourself.

1. DataGrip should show start value for sequence if it as defined in CREATE statement. To see it, please check Specify start with in SQL generator. As I see you did this, and it’s not shown anyway. Is it the same sequence you show the DDL for? Start value will not be generated if it’s default. If it’s a problem, the ticket is here:

About the sequence's current value: now there is no UI to see this, we think the quick doc pop-up is the best place to display this information. Please, follow and comment on the ticket:

2. Yes, this is not yet implemented

3. With code completion settings, as we think, you can approach any workflow we can think of. Let’s look closer at your case. There is the specific option in the Settings which is called “Suggest alias names in completion”. As I see it’s checked at your screenshot and I really wonder why the list doesn’t offer you the alias and goes with UNION ALL instead. Please, provide a screenshot.  This should work and you don’t need to uncheck “insert selected suggestion by pressing space…”

 4. We had a looooong discussion in our team after you pointed to this issue. The initial idea was to make this dialog consistent for all databases. For example, in Oracle the case usually used in that window (low) is not the same as the databases use (upper), and not to make the user use uppercase every time (or not to make him annoyed by quotation) we created this type of behavior. On the other hand, the situation with Postgres is different and “default-every-day-case” which is low is the same as the database's default case. Which actually means what you pointed to: if the camelCase is used, we might understand that the quotation is needed.

I created an issue for that:

By the way, when you quote it manually in the script preview window, the following behavior should work: select the word, type symbol.

Note, that it should work only if Surround selection if typing quote or brace is on.

Unfortunately, it doesn't happen on the field in the Modify Table window, so the separate issue is created as well.

5. If I got you right, the answer is:

  • If the tab name is blue, it means that you’ve modified the source code, but haven’t submitted it yet to the database. I.e. the source code you see differs from the database one because of pending changes.
  • If the tab name is red, it means that this object is deleted from the database. If it happens and the object is not deleted, that’s an issue and we need to know more details. Sometimes it can happen during synchronization but it shouldn’t. 

6. Here we need to understand the actual problem. You just don’t like some temporary files to be created and saved? You can use just one console file. Or you can use common SQL files from your computer and write SQL there: no more new files in Scratches and Consoles. More information about working with files can be found here:

Or, if you want files to be deleted under the hood, you can use scratch buffers, but I don’t think it’s convenient.

7. Making a possibility to refresh only one object is against the whole concept of DataGrip. I will try to explain it.

In DataGrip we have a source code storage: when DG syncs the schema, we have all the sources in the local storage which actual for the moment of synchronization. It is kind of your database model: it helps not only to search through the source code base but provides a navigation → you will be able to know i.e. table A is used in the procedure B, procedure B is executed from the procedure C etc. It is a model which should be consistent to help DataGrip to have all its smart navigation and search features. So, that's why if we refresh only one object, we will break the consistency of the model.

8. Freezes need to be fixed! I ask you after the next time you’ll face it, please send us logs, SQL logs (can be found in Help menu as well) and a memory snapshot. Reporting performance problems are described here:

9. I agree, now it works a little bit like a mess:

  • If you double-click the date-picker appears. The focus is on the first drop-down. It impossible to switch focus. To type the value manually, press ESC and start typing.
  • If you press Enter on the field nothing happens (which is silly I suppose).

I created a ticket to make all this more comfortable for keyboard lovers, for mouse lovers, for date picker fans, and for date picker haters. The current behaviour seems to be no the best for any of them.

10. Particularly for PostgreSQL there is an option called “Switch schema” in the properties.

The default is manual and the search path will be set for this switcher. So, the schema will not be remembered, but the database will.

In the automatic mode, the switcher respects the context of creating a new console.

BTW, you can map a shortcut for action Set Current Schema and use it to put a new value there.


Actually, the manual mode was introduced after that ticket:

11. This UI is reworked in 2019.1. The setting will be saved even for the message box. I hope 2019.1 will solve the issues with saving passwords. More information is here:

12. We usually promote using Recent Files for navigation (Ctrl+E). I hope it is much much handier. Also, consider using Recent Locations pop-up which will work by CtrL+Shift+E from 2019.1

13. We think that generating the appropriate code in some cases work faster than UI. But anyway, we have a ticket for this: and I think we’ll do that. But please consider generating code options which are invoked by Alt+Insert.

14. It took us a while to understand the whole conception of users, roles and groups in PostgreSQL (since some things are obsolete now) and to understand if actually database stores this information. And it does! So, I created a ticket (no one ever asked for this). Does any other tool show this information?

15. The same a 13, but even generate option is missed.

16. Also, not implemented yet:

Thank you very much again!

Comment actions Permalink

Another option from PGAdmin III that would be nice to have in DataGrip from a DBAdmin standpoint would be the ability to disable/enable triggers on a table from the UI. 

This is really useful to me when a minor correction to the data is needed (usually due to a programming error on my part) but I don't want the UPDATE trigger event to actually fire.

Comment actions Permalink

UPDATE (pun intended): My trial of DataGrip has officially expired as of today.  Based on my observations, I'm still not certain whether or not these "issues" are going to outweigh this tool's usefulness.  I'm still investigating my options but, misgivings from the above list aside, DataGrip seems to be the best alternative currently available to PGAdmin 4, especially since I already have the IntelliJ CE installed for working with some legacy Java code.

Before I ask my company to shell out money for a license, though, I would like to see if anyone - either from JetBrains or other users - can possibly address my concerns.  Thank you.

Comment actions Permalink

Thank you, Maxim, for your response, and for taking the time to directly address each of my points individually.  Also, thank you for the subscription offer.  Since my DataGrip trial expired, I started testing another product - Valentina Studio by Paradigma Software - and would like to give that one a "fair shake" before taking you up on that offer, if you don't mind.  I still like DataGrip quite a bit and think that it has tremendous potential to be a powerful tool for developers and DB admins alike.  The issues I addressed in my OP are simply those things that I have encountered as regular parts of my "day-to-day" interactions with my database.

All that said, all three of the tools I've worked with so far - PGAdmin, DataGrip, and Valentina Studio (and, to a lesser extent, MySQL Workbench) - have shown things that I like and things that I don't care for.  I'm going through the support tickets you linked for some additional context, but, since I have your ear, I'll go back through my list with your responses in mind to see if I can provide any further detail, as well as some additional comparison.  I've provided screenshots from Valentina Studio (hereafter referred to as "VaS") for reference since this is the tool I'm currently evaluating.

  1. Most, if not all of my sequences are using the "default" next value for the sequence.  According to the referenced ticket, this is part of the reason that this information is not displayed in the UI.  The other reason given is that the value may change virtually immediately after the information is retrieved and displayed.  This latter, to me, is really a moot point.  If I'm wanting to look at the current value of the sequence at a point in time, I am doing so for a specific reason and even a "best guess" is better than not being able to see it at all.

    Looking at VaS, this information is displayed in a sidebar, which, while I'm still getting used to the layout, seems like a decent way of providing this information without being too intrusive (I included the Windows title bar in the image to provide context). 

    The information can also be shown in a "Generate SQL" window in VaS, although it isn't quite as succinct or immediately obvious:
  2. One thing of note in the screenshots from VaS above is that - for schemas, at least - the ownership information is not present, nor is there any reference to the ACL/permission detail for other roles/groups.  Looking through other objects, the ownership of the objects appears to be populated, but there is still no ACL definition available there either.  For example, this is the information available for a table:

    So far, it looks like the only tool that readily provides this information without having to "dig" for it remains PGAdmin.

  3. Here is a screenshot from my DataGrip console window when attempting to insert an alias of "a":

    And, here are my current settings for Code Completion:

    To be thorough, I attempted it with an actual table in my database and the same alias ("a") and it came up with the same pick-list.  However, when I tried to assign an alias (to a valid table) that "matches" the current table name, it looks like it DOES try to pick something more appropriate:

    My only "issue" there is that it isn't respecting the "Match Case" option (unless I'm misunderstanding the meaning of "Match Case" in this context).  When writing queries, I usually try to assign a single-character, lower-case alias for easy reference.  I believe I understand what it's doing - taking the first character (or, in the case of the second pick-list item for a mixed-case table name, each of the upper-case characters) - but that's not what I typed.  Again, this isn't necessarily a huge issue, but it's a bit of an annoyance.

  4. Thank you for the reference to the Smart Keys configuration setting.  I hadn't seen that option (there are quite a few), but that looks like it would be very useful in this situation.  I also appreciate the new tickets created on behalf of this concern.

  5. Thank you for that explanation of the color meanings.  Now that I look at the situations which prompted the question, this seems to make total sense.  Usually, these were times when I was updating a function or something and, after pushing it to the database, the color of the text in the tab would change.

    Understanding that, if I changed function parameters, the original function with the original parameters would not exist anymore, therefore turning the text red.  If I just changed a part of the query or some other minor update to the function, the original function still exists but is now different than when I retrieved it for the current console window, thus the text would be blue.

  6. This is probably more a matter of personal preference than anything, as well as being unfamiliar with the tool.  When I open a console to execute a specific query, it lists it in the "Scratches and Consoles" list.  I will frequently create multiple queries that I may have to run a couple of times through the course of my development and testing, so I'll leave that console open for a while.  But, when I close the console, I would personally prefer that it "cleans up after itself" and doesn't leave an entry in the "Scratches and Consoles" list.  Why?  Well, the only even half-decent reason I can give is that, the next time I open a console, it assigns a new number to it, and I can get those numbers pretty high.  Not that it has any impact on usability or anything, it's just a bit of an irritant to see a console window title with a "[56]" when there aren't any other console windows open.

    I'll take a closer look at the documentation you provided on working with files and scratches, though.  Perhaps I'm being a bit hasty in my perception here, but my preference would be that perhaps, when being closed, the console window prompts whether or not to save the console status (or this is at least user-configurable) instead of always saving them.  I like a "clean" list as much as possible.

  7. While I understand the point you're making and the reason why it works that way, it can be a bit frustrating when I've made one minor (or significant) change to an object in one of the many databases on my server, then I have to wait for all of the databases on the entire server to synchronize in order to see that change reflected in the UI.  Of course, that's my personal opinion on the matter and certainly shouldn't be considered the "last word" on anything.

  8. Since I'm currently testing VaS, I'll have to get back to you next time I'm in DataGrip and experience the "freezing up" problem.

  9. Thank you for creating the ticket for the DatePicker frustration.

  10. I have had the "Switch schema" option set to "Manual".  I'll see what happens if I set it to "Automatic" in future testing.  Also, I'll look into the keymapping idea.  That may help as well in the event I need to switch schemas "on the fly".

  11. Ahh... It looks like I'm using 2018.3, so that would explain why I wasn't having the same experience when it comes to the "Save Password" checkbox options.

  12. The shortcut keys ([CTRL]+[E]) are probably helpful, but I often look at the tabs across the top of the UI when I'm popping between queries, data views, and other elements while I'm testing.  I'll definitely give the keyboard shortcut options a test run, but it would still be nice (again, just my opinion based on my current habits) if the tabs either:
    A) Were a bit less verbose
    B) Had an option to "wrap" the text or set a minimum/maximum width
    C) Used a slightly modified "navigation" option as I identified in my OP

  13. Holy cow!  I totally didn't know about the [ALT]+[INS] option for the "Generate" box.  I must've missed that part in the documentation.  That certainly provides a much easier way to create triggers, and I'll definitely have to remember that feature is there.  Even so, it would still be nice to have a UI "wizard-type" option for creating triggers, just like there is for creating other objects.

  14. VaS does have detailed role/group membership information available, although you have to go to a different part of the UI to see it - the "Server Admin":

    The only real complaint I have about that interface is that there is no clear, visual distinction between user roles and group roles (there are actually some of both in the list from the screenshot above) as there is in both PGAdmin and DataGrip:
  15. Again, thank you for creating the ticket for this issue.  If nothing else, having the "Generate" option for roles would be helpful.

  16. While it can be done through SQL commands, having a context menu in the UI for quick and easy trigger enabling/disabling would definitely be preferred.  Thank you.

I believe that addresses all of the points.  As I said, I'm taking a bit of time to investigate which tool is going to be "right" for my situation.  I am a one-man development and IT department, so I need to make sure that the tools I use aren't going to end up causing me more headache in the long run.  I'm going to have to switch to a new tool for my PostgreSQL databases and DataGrip certainly seems to be a front-runner at this point, but there are some advantages to VaS that I have to consider, not the least of which being that VaS is free for my current scenario.  Please don't take that the wrong way - I'm not trying to "squeeze" you for free stuff.  I am perfectly willing to pay for a product if it's worth it, and DataGrip does appear to be worth it in a number of ways.  Still, I have to take all factors into consideration here.

Again, thank you so much for your time, and for addressing each point with clear and actual "action items".  That, alone, shows me that you all are interested in more than just putting a product to market, but also in making something of quality and value.  That's something I greatly appreciate.  Please let me know if you have any additional questions about the (new) information I've presented.

Comment actions Permalink

Forgive me, but I came up with a couple more "feature requests" as I was looking over the "Server Admin" tab in VaS and doing some "comparison shopping".

#17. The "Connections" tab (in VaS), which shows the details of active connections and queries on the selected/active database.  PGAdmin III showed this in the "Statistics" tab when selecting a database, but it was only a read-only view.  VaS provides this as an interactive window, similar to how MySQL Workbench operates.  Not only does it refresh over time, but it also allows you to kill active queries and connections in the case of a "hung" query or something (infinite recursive looping, or whatever).  Again, if I've overlooked this feature in DataGrip, please let me know as this is something that doesn't come up often, but would definitely be nice to have when needed.  Here's a screenshot from MySQL Workbench 6.3 CE:

And from VaS:

And PGAdmin III (read-only, unless I've missed something there):

As I said, if this information is available - and, especially, interactive - in DataGrip, I've not yet found it.

#18. (This item is definitely a "Wish List" type of item, not a huge necessity) Quick access to the database configuration files through DataGrip would be nice, either via a "fancy" and featured UI dialog, or simply a "raw data" view.  VaS doesn't seem to have this (at least, that I can tell so far).  PGAdmin obviously has a UI option for editing and maintaining the PostgreSQL database configuration files (pg_hba.conf, postgres.conf, and pgpass.conf):

And MySQL Workbench obviously has a UI option for its main configuration file (my.ini):

I don't know that much about other database servers, but I've done a fair amount of work "tweaking" these configuration files to suit my environment.

As I said, this item (#18) is definitely not a "requirement", but it would provide a decent boost in the QoL for users of DataGrip in the long term to have quick and easy access without having to manually go find the file(s) for editing. Hopefully, I'm done for the day.  Thank you again.

Comment actions Permalink

Hi, Jeremy! Some of your points are completely clear but require no additional reaction. If there are a ticket and our understanding of the feature request, we have no more to say than thanks for the feedback. We’ll consider and discuss all of them, but the whole prioritizing process depends on many factors. Which is obvious :)

But I’ll answer to those paragraphs which still require this.


  1. Got the point. We agreed that suggested aliases should be always lower-cased


  1. Again, makes sense! Created a ticket where we can discuss possible approaches if the suggested is not the best.


  1. In PostgreSQL, you don’t need to wait for the whole re-syncing, because we support incremental introspection for it. So, if the object is changed from DataGrip, we understand that only this object needs to be refreshed. Of course, if the change came from the other place, we cannot track it.


  1. While we don’t have the options you mention, please, try playing with options in Settings


Or set small tab labels



Or maybe just place all tabs to the left.



  1. Group wears a hat :)


  1. The first iteration of “connections dashboard” is coming in 2019.1


  1. Just a workaround: these files can be accepted via SQL



Please sign in to leave a comment.