DataGrip 2023.1 EAP 1
Hello, DataGrip fans!
Our 2023.1 release cycle is all about quality, which means we’re working on the bugs that have accumulated in our public issue tracker. Today we’ll cover what we’ve managed to fix so far. Of course, you can already get the benefits of these fixes by downloading our EAP build!
Working with code
- DBE-4469: We fixed the problem where SQL Formatter didn’t apply the right style for a subquery in the EXISTS clause.
Now it works as expected, and DataGrip can also add a space between the EXISTS keyword and the left parenthesis. For this part, we also added a new setting. Now, if you want to preserve the old Formatter behavior (without the space), you can change the Space after keyword setting to No in Preferences | Editor | Code Style | SQL (go to the Queries tab).
- DBE-14440 [H2]: We fixed the bug with saving style settings. If you have configured a special style for SQL2016 and the Inherit general SQL style checkbox in Preferences is not enabled, then you will need to reconfigure it.
The other fixes in this area are more or less self-explanatory:
- DBE-15973 [BigQuery]: The WINDOW clause is now supported.
- DBE-9219 [Clickhouse]: Сase settings when completing exact-case names are now ignored.
- DBE-14796 [MySQL]: Problems with LAG and LEAD functions have been fixed.
- DBE-16311 [MySQL]: FOR UPDATE in nested queries is now supported.
- DBE-12139 [MySQL]: The ENCRYPTION syntax is now supported.
- DBE-13186 [Microsoft SQL Server]: Inspections no longer erroneously report extra code.
- DBE-11946 [PostgreSQL]: An issue with Place constraints was fixed.
- DBE-6276 [PostgreSQL]: DDL navigation to security policies now works as expected.
- DBE-17263: Data source content statistics is again displayed in the Quick Documentation popup.
- DBE-10812 [PostgreSQL]: The Drop context menu command now works as expected.
- DBE-12578 [Oracle]: Cross database triggers are now supported. You can create a trigger X in schema A to table E in schema B, and it will be shown in schema B under the host table E.
- DBE-6986 [MySQL]: The ROW_FORMAT clause/syntax is now supported.
- DBE-10603 [Microsoft SQL Server]: The Quick Definition now works as expected.
- DBE-9087 [PostgreSQL]: When using the clause REFERENCING, the trigger’s DDL is generated correctly.
- DBE-12404 [IBM Db2]: We fixed an issue with interrupting object introspection. If the user permissions did not allow retrieving a list of database users, the rest of the database objects were not loaded either. Now everything but the list of users will be loaded.
- DBE-16417 [Microsoft SQL Server]: Current schema detection now works for any database.
- DBE-11012 [SQLite]: The SQLite native library is now unpacked to the system folder.
- DBE-16393: We’ve added a source editor to the Modify view.
- DBE-17329 [PostgreSQL]: Virtual view creation is now also available in read-only mode.
- DBE-3572: We’ve added an Alternate row colors setting for results tables. When the checkbox is enabled, rows will have alternating colors.
- DBE-16250: There are no more empty spaces in in-editor results, as the table now adjusts its height to match the height of the results.
- DBE-14074: Named parameters are detected correctly.
- DBE-10555: Whenever you copy and paste something, the IDE now correctly analyzes the selection (instead of the cursor position).
- DBE-12109 [Oracle]: Semicolons are no longer omitted in Oracle Aggregate Functions.
- DBE-16871 [BigQuery]: The Unexpected value error no longer pops up when previewing a table.
DBE-16831: A setting to specify the default resolve mode used in the console has been added to Preferences | Database | Query execution | Other.
- DBE-5497 [Oracle]: We fixed a few problems with Oracle collection methods:
– Public synonyms are now correctly placed in the PUBLIC schema.
– Recursive references to nested routines are resolved correctly.
– Cursor parameter references qualified by a cursor name are resolved correctly.
– Incorrect usages of %TYPE are reported as warnings.
- DBE-12772 [Oracle]: We fixed the resolution of standard attributes for collection types (for example, COUNT).
- DBE-17137: We fixed a bug where the IDE would show the Explain Plan diagram only for the first of several queries.
Navigation and search
- DBE-12015 [Oracle]: Go to Declaration (Ctrl/Cmd+B or Ctrl/Cmd+click) now navigates you to the routine implementation.
That’s it for now! Get the EAP 1 build and try working in DataGrip without these nagging issues. And let us know what you think in the comments below!
Subscribe to Blog updates
Thanks, we've got you!
DataGrip 2023.2: New UI with toolbar icons in the header, AI Assistant, time zones in the data editor, support for Redis Cluster
DataGrip 2023.2 is out!Here’s a sneak peek at what it has to offer. For a detailed description of this update, please visit our What’s New page. User Interface New UI: The toolbar icons have been moved to the header Improved main toolbar customization Light theme with light …
DataGrip 2023.2 EAP 2: Redis Cluster, New Schema Migration Dialog and More
Hello, DataGrip community! The second Early Access Program version for DataGrip 2023.2 is here. If you want to try the new features before the official release, this post is for you! Support for Redis Clusters Now you can connect to Redis Clusters and have the same feature set as with standalo…
DataGrip 2023.2 EAP is Open!
Hello! We are starting our EAP (Early Access Program) for 2023.2 and, as usual, we're inviting you to try the latest features and improvements we’re adding to DataGrip ahead of the official release. Let's look at what's inside the first EAP build. New UI The new UI is now enabled by d…
Nextсloud Performance Hacks with EverSQL and DataGrip
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@as…