2018.3

Hi! We have an update for 2018.3. Some bug-fixes are inside. SQL formatter: we’re still improving it! DBE-7362: Formatter works in SQL-injections. DBE-7376: Better WITH formatting. DBE-6937: Better arrays formatting in PostgreSQL. DBE-4805: We keep the case of quoted identifiers in PostgreSQL. DBE-7881: Support for ON CONFLICT clause in PostgreSQL. DBE-7890: No more line break after PERFORM in PostgreSQL. DBE-7605: INTO TEMP TABLE support in PostgreSQL. DBE-7806: Better formatting for variables in SQL Server. Other During data import errors are written into a file by default. DBE-7838: Fixed b

Hi all, Here’s a list of important bug-fixes in 2018.3.3: DBE-7745: No more false positives in Unreachable Code inspections in case of FOREACH statements. DBE-4399: Fixed the problem with resolving objects in files. DBE-7699: UTF-16 is always used in the data editor. DBE-5850: No more -1 day changes to dates. DBE-1465: Fixed a regression issue with synchronizing read-only data sources. DBE-7795: Fixed problems with rename cancellation. DBE-7694: The correct script is generated for changing table comments. DBE-7712: All MySQL functions are correctly highlighted in the editor. If you use the&

Hello, Here it is, the second minor update for 2018.3 with some added improvements. The most notable feature is: Enum values can now be completed in the data editor. This works in both PostgreSQL and ClickHouse. Other important fixes we’ve made: DBE-7561: DataGrip doesn’t change the default value of a column in MySQL. DBE-7572: CREATE OR REPLACE is supported for MariaDB events. DBE-7604: Hidden schemas are not used in comparison now. DBE-7417: Report mismatch between expected/actual column count in the SQL Server OUTPUT clause is fixed. DBE-7457, DBE-7458: DataGrip doesn’t

Hello, Here comes the first minor update for 2018.3 with a few important improvements. DataGrip had a usability problem where, every time you opened the source code, it showed you a version loaded during the indexing process. In fact, if someone had changed the source code from another place, DataGrip was unaware of it and thus displayed an outdated version of the DDL. The thing is that DataGrip maintains a consistent database model at every moment to provide navigation and usage search. This means the IDE cannot update just one single DDL in the local storage as that would break the whole

Hello everybody! We are excited to release DataGrip 2018.3 today! As usual, we thank all our early adopters who have helped us make the IDE better during this release cycle. The most active ones have already got their free DataGrip subscriptions, as a token of our appreciation. If you wish to see the detailed overview of this update, please visit our What’s new page. Read on for a list of all the enhancements waiting for you in 2018.3. Database objects — Cassandra database supported — Generate SQL files for the selected objects — Support for extensions in PostgreSQL — Support for stored proc