DataGrip 2021.3 EAP 2
Hello! Another EAP build for 2021.3 is available! We would appreciate it if you would try it out and share your feedback with us.
Check for boolean expressions
One of our users tweeted about an unfortunate situation: he executed the UPDATE query on a production database with the condition WHERE id – 3727 and got millions of rows updated! We were also surprised that MySQL allows that, but c’est la vie.
We wouldn’t be the DataGrip team if we wouldn’t add an inspection for that! Please welcome the check for boolean expressions in WHERE and HAVING clauses.
If the expression doesn’t seem to be explicitly boolean, we highlight it in yellow and warn you before you run such a query. It works for ClickHouse, Couchbase, Db2, H2, Hive/Spark, MySQL/MariaDB, Redshift, SQLite, and Vertica. In all other databases, this will be highlighted as an error.
New database diff window
The new database diff window is under construction, but you can already try it. Please share your feedback with us and report any issues you find to our tracker.
Just to remind you: to compare two schemas or objects, select them and press Ctrl/Cmd + D.
Foreign key navigation by several values
In the data editor, you can now select several values and navigate to the related data.
Automatic column types in CSV files
We now automatically detect column types in CSV files. The main benefit of this is that you can sort data by numeric values. Before, they were treated as text and sorting wasn’t natural.
Extract function for queries
Now queries can be extracted as a table function. To do this, select the query, invoke the Refactor menu, and use Extract Routine.
[PostgreSQL] Ability to hide system schemas and template databases
Internal system schemas (like pg_toast or pg_temp) and template databases used to be hidden from the schemas list. It’s now possible to show them with the help of the corresponding options in the Schemas tab.
Don’t forget to click Refresh after you change these options.
That’s it for today! As usual, we would appreciate your feedback in the issue tracker, on Twitter, or in the comments below.
The DataGrip team