I have tried DataGrip briefly with Postgres – my first impression was that it's a competent tool for things that are generic across all RDBMSs, but limited in RDBMS-specific management/administration functionality. Not far off from what you said :)
If you have time, what about DataGrip do you find to be "a lot nicer than SSMS"? Which features should I (a DataGrip noob) try using?
First of all, I don't think I've personally scratched the surface of what you can do. But I use it mostly as a direct replacement of what I would have done in SSMS.
First of all Start writing queries and see how much it will help you, for the most it will autocomplete lots of things, once you are used to joins been auto written for you, hard to go back!
personal preference, but, it supports vim bindings.
Its table editor works on partial queries for updates, so you can select something and as long as you selected the key, you can do a update using the table editor. Speaking of the table editor, it is vastly superior and allows batching of changes, it shows you queries its going to do, has lots of helpers for all sorts of things including datetimes. It has lots of options to capture the table in lots of formats. It also allows across database comparisons of tables and synchronization or generation of sql scripts of differences/database changes.
Its ide is standard jetbrains ide ish and has lots editing goodness, refactoring, auto generation, surrounds, templates, local change history, lots of navigation tools ( go to references / usages etc )
I have tried DataGrip briefly with Postgres – my first impression was that it's a competent tool for things that are generic across all RDBMSs, but limited in RDBMS-specific management/administration functionality. Not far off from what you said :)
If you have time, what about DataGrip do you find to be "a lot nicer than SSMS"? Which features should I (a DataGrip noob) try using?