DataGrip 2017.3.4

Hi, I'm Pasha. In my everyday life, I'm a Developer Advocate for data engineering, but by night, I'm a geek. Like, a really geeky geek! I have used Linux since 2009 as my primary OS (BTW I use Arch). If possible, I always prefer to host everything I use. So if you decide to drop me an email at me@asm0dey.site, rest assured, I’ll receive it on my self-hosted mail server. While self-hosting certainly has its benefits, it does have some downsides, like poorer performance, that should be addressed.This is the story of how I “fought” with self-hosted MySQL to get better database performance. Nex

Hello!  For DataGrip 2023.1, we focused entirely on quality. We’ve fixed many bugs that had accumulated in our public issue tracker (not the most fun part of the job, but important nonetheless). While there won’t be any new features for you to explore this time, we hope you’ll notice improvements in your daily work with DataGrip. Here are a few of the highlights, and for a full list of bug-fixes with more details, please visit our What’s New page. Working with code DBE-4469: We fixed the problem causing the SQL Formatter not to apply the correct style for subqueries in EXIS

DataGrip 2023.1 EAP 3 is out! Here are the new fixes in this version: Introspection Switch the introspection level to Level 1, where DataGrip introspects only the names and types of objects. On introspection Level 1, you can click Refresh selected object to edit a specific object or view its sources. Check if you have the SELECT_CATALOG_ROLE and the SELECT ANY DICTIONARY permissions, which grant you access to the Oracle internal catalog. This makes introspection much faster. Code highlighting Schema Diff If the Specify next value for sequences option is