DataGrip 2017.1 Released!

Hello!  From this post you’ll find out what’s new in DataGrip 2017.1.

DataGrip_20171@2x_splash

It is a long read, so let’s begin with the table of contents.

Database tree: New schema management, SQL resolution scopes; Create database/schema UI; Color settings affects editor and grid.

Import/export data: Column mappings and DDL preview; Drag-n-drop tables; Export result-set to a database.

Query Console: Respecting the default search path in PostgreSQL; Trigger generation pattern; Insert string concatenation on Enter option;  Settings for Qualifying objects and more.

Database objects: Double-cliсk opening of column details in Modify table; Warning if object has been changed in another place.

Miscellaneous: Query time and column/row numbers in data editor status bar; Including/excluding text occurrences in Find Usages; Windows authentication for SQL Server in jTDS driver and more.

Below come the details.

Database tree

New schema management

Now the schema selection UI is a tree with the ability to choose if you want to introspect the current schema/database or, all schemas/databases. The  ‘Schemas…’ node in the database view will also show this tree.

00-—-SchemasPopup

The Schemas tab comes back to the data source properties dialog. We added the Pattern field, where you can describe what you want to be introspected. The Ctrl+Q (Ctrl+J for OSX) shortcut will give you information about the syntax.

03-—-NewSchemaManagement

SQL resolution scopes

As you know, DataGrip resolves objects from SQL code to your database. It means that the IDE understands which particular object you use in your script and provides navigation, code completion, and everything else that we are proud of. But previously this process incurred some difficulties if objects in code were unqualified. For instance, if your script contained just table names without schemas or databases, and there were two identical data sources, test and production, then the situation would become confusing.

04 — SQLResoultionScopes

Now, you can simply map any file or folder to any datasource in Settings → Database → SQL resolution scopes. This means that all unqualified objects will be resolved to the selected datasource/database/schema. The project level mappings are the same as Options → Resolved unqualified references in previous versions. All your settings configured there will transit here, so you won’t lose them.

Create database/schema UI

Many of you asked us to implement some simple UI for creating schemas and databases. Voila!

01 — AddSchema

Decide if you want these new schemas and databases to be introspected immediately. This also applies to creating and deleting schemas/databases from the query console.

02 — TrackCreation

NB! As we still do not support several databases for PostgreSQL, any database created in this UI will not appear in the database tree, even if this option is enabled. Please create another data source to manage your new database.

New options in color settings

Data Source color (Context menuColor settings) now affects the console and result tab toolbars. It can even be applied to the editor and grid as well. We hope this will help you avoid running test scripts on your production databases.

05 — ColorSettings

SQLite better introspection

We introduced a small database tree improvement for SQLite users. In earlier versions, we used the introspection provided by JDBC-driver for SQLite. As a result, many objects were absent in the database tree and some source codes were incorrect. Now we show triggers, expression indexes, partial indexes and check constraints.

06 — SQliteIntroscpetion

Import/export data

Import dialog enhancements

We’ve been asked to make the import process more flexible. It frequently happens that the number of columns in a .csv file is not the same as in the target table. Or you just want to import several columns from a file, but not all of them. Now it’s possible to map every column of the file being imported to a table column in your database, which can be either an existing table or a new one created during the import process. Of course, completion works for column names.

01 — ImportMappings

Another new thing in this window is a DDL preview tab, showing you the code to be executed for creating or changing the table.

02 — ImportDDL

Export/import tables

Now there is an easy way to export tables and their data from one database/schema to another. It works even if the tables are in different databases from different vendors. For example, if you need to copy a table from a PostgreSQL database to a SQL Server database, just drag-n-drop it. Check if all is OK in the Import table window and go ahead!

03 — DragnDropTables

The same for the result-set! We added the Export to database buttonChoose any schema in the list and go ahead: the new table is created, the data is inserted.

04 — ExportResultSet

Query console

Respect the default search path

Here is the most important point for PostgreSQL users: now DataGrip respects the default search path. Before, we set the search path according to the context of the console opening. At some point we discovered it wasn’t very convenient for many of you. Now the default search path is set for any console. Change it in any moment or go back to the default one.

00 — SearchPath

Better triggers support

A trigger template has been added to the Generate menu, which is invoked with Ctrl+N (Cmd+O for OSX).

01 — GenerateTrigger

The IDE supports NEW/OLD and INSERTED/UPDATED tables when creating or editing triggers. This means you can use completion for these tables’ columns as well.

02 — TriggerInserted

Code assistance

Try enabling Settings → Editor → Appearance → Show parameter name hints: DataGrip will prompt you about column names in INSERT statements.

03 — ValueHints

We’ve added an SQL section to Settings → Editor → Smart Keys.

05 — QualifyOnColllisions

The Insert string concatenation on Enter option lets you choose if you actually need this. It was the default option before, and it works like this:

EnterWithConcat (2)

But the majority of database management systems support multiline string literals, so this IDE behavior may be annoying. Uncheck the option if you use multiline literals.

EnterWithoutConcat

Qualify object in completion is also a thing we’ve been asked to implement. There are three options and here’s how they work. Suppose we have two schemas, max and public:

04 — QualifyIntroscpector

The table persons is present in both schemas and the table cardvendors is only in max. Here is the example Qualify on collisions:

06 — QualCollisions
Named parameters of routines can be completed by using second completion (pressing Ctrl+Space twice):

07 — ParametersNAmedCompletion

Aliases casing can now be set in Settings Editor Code style SQL. Aliases are offered in code completion.

08 — AliasCasing

The general platform setting in Settings → Editor → Appearance → Show method separator now draws a line between statements.

09 — StatementSeparators

An amusing feature for MySQL: due to errors in the MySQL grammar, a database cannot run queries with some combinations of parenthesis and UNION’s. Now DataGrip can handle these situations.

13 — UnionError

Jump to colors and fonts

A small helpful action is available to those who don’t want to wade through colors and fonts settings to find a single thing they need. For now it is only present in the Find Action menu (Ctrl/Cmd+Shift+A), but as usual, you can assign any shortcut to it.

10 — FindActionText

This action will navigate you to the settings which are relevant to the context under the caret. If there are several of them, just choose one.

11 — JumpToStringToken

Here you are!

12 — StringTokenPrefs

 

Database objects

Modify table UI improvement

The column details in the Modify Table dialog are now opened by double-cliсk.  We changed it based on your negative feedback on single-click opening.

02 — ModifyTable

Tracking source code changes

Sometimes you make changes to the source code of some object, but forget to apply them. As you may know, DataGrip will detect and indicate this with colored marks on the gutter. If you modify such an object in some other place in DataGrip, the source code editor will alert you.

01 — LocalChanges

Documentation link for system tables in PostgreSQL

The quick info pop-up (Ctrl+J) for PostgreSQL system tables now contains the link to the documentation page at postgresql.org.

03 — PgDocument

SQLite views

Also, now DataGrip loads the correct source code for views in SQLite. Before it was the ‘CREATE table’ code.

04 — ViewSQlite

Miscellaneous

More information in result-set status bar

Some information was added to the status bar of the data editor. It is query time and selected column/row numbers under the cursor.

01 — QueryTime

Text occurrences in Find Usages

Also, we have the new option to include or exclude text occurrences in Find Usages.

02 — FindUsagesOptions

If it’s selected, the results will include comments, occurrences in text files, and string literals.

03 — UsagesOfText

Other

— Windows authentication for SQL Server in the jTDS driver.
— Correct line endings are sent to the database in SQL Server.
— Support of the CREATE/ALTER construction from SQL Server 2016. 
TNS names are correctly parsed from tnsnames.ora file in Oracle.
— It’s possible to use routine parameters in LIMIT in MySQL.
— Commit triggers synchronization in PostgreSQL.
— Single quotation mark is now escaped in DDL.
— Read-only preview is available for large files.
— Warnings are added on the Output tab as soon as they’re raised.
Zero-latency typing is now enabled by default.
— Icons for synonyms are displayed in the structure view and completion.
— Customized colors are used for syntax highlighting of regular expressions.

If it’s not the first post you read in this blog, you already know all the information below, but still:

— Get your 30-day trial of DataGrip here.
Tweet at us!
Discuss anything in forum.
— Report bugs to our issue tracker.

Thank you for your attention!
Your DataGrip Team
_
JetBrains
The Drive to Develop

Posted in Releases | Tagged , , , , | 21 Comments

DataGrip 2017.1 RC is Out!

Hi there,

All IntelliJ-based IDEs are rushing to the 2017.1 release, and here is our DataGrip 2017.1 RC. Many new things were added since the latest EAP, so let’s see what’s new inside.

Create database/schema

Many of you asked us to implement some simple UI for creating schemas and databases. Voila!

AddSchema
Decide if you want these new schemas and databases to be introspected immediately. This also applies to creating and deleting schemas/databases from the query console.

TrackCreation

NB! As we still do not support several databases for PostgreSQL, any database created in this UI will not appear in the database tree, even if this option is enabled. Please create another data source to manage your new database.GenerateMenu

The Generate menu (Alt+Ins/Cmd-N) also contains a Schema and database now.

 

Find usages

Here we have a new option to include or exclude text occurrences.

FindUsagesOptions

If it’s selected, results will include comments, occurrences in text files and string literals.

UsagesOfText
Source code editing

Sometimes you make changes to the source code of some object, but forget to apply them. As you may know, DataGrip will detect and indicate this with colored markers on the gutter. If you modify such an object in some other place in DataGrip, the source code editor will alert you.

LocalChanges

 

We’ll be happy if you try this build and follow us not to miss the huge blog-post about all new features in this release!

DataGrip team.

Posted in Uncategorized | 2 Comments

DataGrip 2017.1 EAP 3

Hello!

In this post I’ll tell you what our team has been doing in February and what the latest EAP build brings to DataGrip 2017.1.

SQL resolution scopes

As you know, DataGrip resolves objects from SQL code to your database. It means that the IDE understands which particular object you use in your script, and provides navigation, code completion and everything else that we are proud of. But previously this process met with some difficulties if objects in code were unqualified. For instance, if your script contained just table names without schemas or databases, and there were two identical data sources, test and production, then the situation would become confusing.

Resolution

Now, you can simply map any file or folder to any datasource in Settings → Database → SQL resolution scopes. This means that all unqualified objects will be resolved to the selected datasource/database/schema. The project level mappings are the same as Options → Resolved unqualified references in previous versions. All your settings set there will transit here, so you won’t lose them.

Respect the default search path in PostgreSQL

Before, we set the search path according to the context of the console opening. At some point we discovered it wasn’t very convenient for many of our users. Now the default search path is set for any console. You can change it in any moment or go back to the default one.

Search-path

Editor

The color setting of the datasource can be applied to the editor as well. We hope this will help you avoid running test scripts on your production databases.

Colors

If you enable this option in Settings → Editor → Appearance → Show parameter name hints, DataGrip will prompt you about column names in INSERT statements.

Hints

The general platform setting in Settings → Editor → Appearance → Show method separator now draws a line between statements.

Separator

A small helpful action for those who don’t want to wade through colors and fonts settings to find a single thing they need. For now it is only available in the Find Action menu (Ctrl/Cmd+Shift+A), but as usual, you can assign any shortcut to it.

Jump-to

This action will navigate you to the settings which are relevant to the context under the caret. If there are several of them, just choose one.

ChooserJumpTo

Here you are.

ColorSettingFonts

Statistics

Query time is now shown in the status bar.

TimeQuery

We’ve added some statistics to the notification you get after import from file is finished.

StatsAndError

Also, the error message in importing now contains a row/symbol number and shows actual/expected symbols.

Other important fixes

— Single quotation mark is now escaped in DDL
— Read-only preview is available for large file
— Emoji support
— Warnings are added on the Output tab as soon as they’re raised
— Commit triggers synchronization in PostgreSQL
— Correct line endings are sent to the database in SQL Server

Take DataGrip EAP for a spin!

Your DataGrip Team

Posted in Uncategorized | Tagged | 8 Comments

DataGrip 2017.1 new EAP build

Hello! It’s time for the new EAP build for 2017.1 which is going to be released later this March. There are several notable features, let’s take a look at them.

Schema management

We are still working on the schema selection UI. Now it’s a tree with the ability to choose the current schema. Of course, if the current schema is changed in some other place, DataGrip will show the new one.

SchemasPattern

The Schemas tab comes back to the data source properties dialog. We added the Pattern field where you can describe what you want to be introspected. The Ctrl+Q (Ctrl+J for OSX) shortcut will give you information about the syntax.

Import CSV

First: Drag-n-drop csv files to the datasource.

Second: Import zipped CSV files.

ImportCSV

Remember that the process information is available on the Database tab of Event Log. We added a link to the error file.

ImportErrors

Also, importing itself has become much faster. For instance, a 50 MB file was imported for 2 minutes. Now it takes just 10 seconds.

Other enhancements

The column details in the Modify Table dialog are now opened by double-cliсk.  We changed it based on your negative feedback on single-click opening.

ModifyTable

Data Source color (Context menuColor settings) now affects the console and result tab toolbars.

Colors

Aliases casing now can be set in Settings Editor Code style SQL. Aliases are offered in code completion.

Aliases

An amusing feature for MySQL: due to errors in MySQL grammar, a database cannot run queries with some combinations of parenthesis and UNION’s. Now DataGrip can handle these situations.

MySQL

That’s it! Don’t forget about twitter, forum, and the issue tracker.

Your DataGrip Team
_
JetBrains
The Drive to Develop

 

Posted in EAP, Features | Tagged , , | 9 Comments

DataGrip 2016.3.3 is here

Hello! A minor update for DataGrip 2016.3 is out.

The most notable enhancements are:

The Drop action in the context menu for schemas.

DropSchema

We removed the Drop action from the context menu of the objects which cannot be dropped by DataGrip.

This build also comes with the following improvements:

— The random switch-off of Auto-commit has been fixed
Long lines on Oracle routines are no longer truncated

Update your version of DataGrip using the Check For Updates… menu or just download the new version from our web-site.

Please keep reporting problems to us if there are any.

Your DataGrip Team
JetBrains
The Drive to Develop

Posted in Features, Minor updates | 4 Comments

DataGrip 2017.1 Early Access Program Started

Hello! The new year has already brought us a new version of DataGrip, as today we start the Early Access Program for DataGrip 2017.1. Everybody can try this free build and take the new possibilities for a spin:

Сolumns mapping in CSV
Drag-n-drop tables
Smart options for SQL editing
Code insight
SQLite introspection
Miscellaneous

Let’s see what these enhancements are about.

Сolumns mapping in CSV import

Many users have asked us to make the import process more flexible. It frequently happens that the number of columns in a .csv file is not the same as in the target table. Or you just want to import several columns from a file but not all. Now it’s possible to map every column of the file being imported to a table column in your database, which can be either an existing table or a new one created during the import process. Of course, completion works for column names.

ImportMapping

Another new thing in this window is a DDL preview tab, showing you the code to be executed for creating or changing the table.

ImportDDL

Drag-n-drop tables

Now there is an easy way to export tables and their data from one database/schema to another. It works even if the tables are in different databases from different vendors. For example, if you need to copy a table from a PostgreSQL database to a MySQL database, just drag-n-drop it. Check if all is OK in the Import table window and go ahead!

DragnDrop

Smart options for SQL editing

We’ve added an SQL section to Settings → Editor → Smart Keys.

SmartOptions

The Insert string concatenation on Enter option lets you choose if you actually need this. It was the default option before, and it works like this:

SmartConcat

But the majority of database management systems support multiline string literals, so this IDE behavior may be annoying. Uncheck the option if you use multiline literals.

SmartLiteral

Qualify object in completion is also a thing we’ve been asked to implement. There are three options and here’s how they work. Suppose we have two schemas, max and public:

SameTables

The table persons is present in both schemas and the table cardvendors is only in max. Here are examples corresponding to the different values in Qualify object in completion:

– Always
CompletionAlways
– On collisions
CompletionCollisions
– Never
CompletionNever

Code insight

DataGrip now supports NEW/OLD and INSERTED/UPDATED tables when creating or editing triggers. This means you can use completion for these tables’ columns as well.

Inserted

Named parameters of routines can be completed by using second completion (pressing Ctrl+Space twice):

NamedParamCompletion

Also, the CREATE OR ALTER construction, which appeared in SQL Server 2016, is now supported as well.

CreateOrAlter

SQLite introspection

In earlier versions we used the introspection provided by JDBC-driver for SQLite. As a result, many objects were absent in the database tree and some source codes were incorrect. Now we show triggers, expression indexes, partial indexes and check constraints.

SqliteDBView

Also, now DataGrip loads the correct source code for views. Before it was ‘CREATE table’ code.

SQLiteView

Miscellaneous

A trigger template has been added to the Generate menu, which is invoked with Ctrl+N (Cmd+O for OSX).

GenerateTrigger

The quick info pop-up (Ctrl+J) for PostgreSQL system tables now contains the link to the documentation page at postgresql.org.

Documentaion

TNS names are correctly parsed from tnsnames.ora file in Oracle. This means that the completion is available in this field of the connection window.

TNS

Other enhancements

Zero-latency typing is now enabled by default
– Icons for synonyms are seen in structure view and completion
– It’s possible to use routine parameters in LIMIT in MySQL
– Customized colors are used for syntax highlighting of regular expressions

That’s all for today. Your feedback is welcome in our twitter, forum, and the issue tracker. Let us know what you think about DataGrip 2017.1!

Your DataGrip Team
_
JetBrains
The Drive to Develop

Posted in EAP, Features | Tagged , , , | 6 Comments

DataGrip 2016.3.1 is Out

Hi! Thank you for your feedback about our 2016.3 release. This is the first minor update.

Fixed bugs:

DBE-2147 — Sometimes columns width is extremely narrow

bugfix

DBE-3562 — Routine/Trigger editor does not drop object before running

DBE-3605 — OSX connection to SQL Server does not accept password

And one enhancement:

Since it is possible to submit changes in bulk by Ctrl/Cmd+Enter starting from 2016.3, many users asked to add the submit button. Done!

submit

Please update your version of DataGrip from Check For Updates… menu or just download a new version from our web-site. Please, keep reporting problems to us if there are any.

Your DataGrip Team
JetBrains
The Drive to Develop

Posted in Minor updates | 6 Comments

DataGrip 2016.3 Released!

Hello, everybody!

This release cycle was really important for DataGrip — triggers support, find usages inside views/procedures, bulk submitting of changes: all these features were long-awaited and we thank everybody who helped us provide them in the right way during our EAP program. We are excited to release DataGrip 2016.3!

announce

As usual, everything described here is also available in 2016.3 version of IntelliJ IDEA, PyCharm, RubyMine and PHPStorm, except one small feature we will tell you about.

Here we go!

Source code storage

Now DataGrip shows triggers, views, and materialized views source code. Also, IDE lets you find usages of tables/views inside other views, stored procedures, and functions.

How does that work? The IDE loads the source code of major types of objects and puts them into the local storage. This opens up many new possibilities, so let’s briefly go over them.

To make this storage work, please re-synchronize your data source. Select Forget Schemas, and then click the Synс/Refresh button.

forgetschemas

You’re ready. Most importantly, now you can find usages of objects inside the source code of other objects. For instance, you can learn in which stored procedures, functions or views your table is used. As usual, press Alt+F7 on the table name or call it from the context menu. In the Usages window you can see the preview of objects, i.e. the source code of the objects where your table is used.

What else? We’ve fixed many bugs related to source code. Now DataGrip shows it for triggers in all popular management systems: MySQL, PostgreSQL, SQL Server, Oracle, and Sybase. We also added the Drop action to the context menu.

triggerssupport

View source code is also shown correctly in all places. In addition to Copy DDL, there is a new action in the context menu now: Open DDL in Сonsole.

openddlinconsole

We didn’t forget about materialized views in PostgreSQL: their source code is now available, and materialized views can be refreshed from the UI.

materializedviews

When you edit the source code of any object, DataGrip tracks your changes and highlights edited rows in the left editor panel. If you click on a highlighted row, a small toolbar is displayed with a Show Diff link. Click it to see the difference between the row you’ve changed and the one from the source code.

Important! Everything you’ll write in this editor will be saved as the local version of the object’s source code. It means that you will see all queries you entered here every time you open the editor, until you press Revert.

gutterdiff

If there are lots of changes in many places, you can see all of them in the Database Changes window. Please note that this window is available only in DataGrip, not other IntelliJ-based IDE’s.

databasechangesmenu

Any individual change can be clicked to display the diff viewer as well.

databasechanges

Remember that you can manage which sources will be loaded (or none at all) using the Options tab of data source properties, or from the context menu for several data sources at once.

loadsourcesmenu

Other enhancements connected to database objects support are:

  • Views can be renamed using Ctrl+F6 (Cmd+F6 for OSX).

renameviews

  • Operator’s signature in PostgreSQL is shown in the database view.

operatorssemantic

  • Comments in creating procedures/functions DDL are now saved to the database.

commentprocedures

Data editor

A lot of new features of this version are related to the data editor. The first and the most important: now all your changes are stored locally and can be submitted at once. Local changes are colored, so you can see which changes you are going to save, be it updating, inserting or deleting rows.
Submit changes by Ctrl+Enter (Cmd+Enter for OSX).  As usual, Ctrl+Z (Cmd+Z for OSX) is for canceling, but works in a tricky way — only the selected changes are canceled. If you wish to cancel all of them, select all cells by Ctrl+A (Cmd+A for OSX) before reverting.

bulksubmit

Several fields can be edited at once: just select them and begin to type. Of course, it works only if the columns you are editing are not unique and have the same type.

mordor

We added data conversion. Copy-paste your data even if the fields have different types of data, and moreover, even if the tables are in different databases from different vendors!

Since multiple cells edit is also available, this will work with the whole column of data as well. Date to string, bool to integer — not a problem.

conneversion

The familiar editor’s action called Select next occurrence by Alt+J (Ctrl+G for OSX) works here now, even if several cells are selected.

nextoccurence

Another familiar Expand selection action by Ctrl+W (Alt+Up for OSX) works in the data editor like this: first, a field is selected, then the column of the active field, then the row of the active field, and finally, the whole grid.

growselection

Code insight

The INSERT statement completion offers you not only the list of all fields but also the list of fields which have no default value.

completionwithputdefaults

The IDE will warn you about an unused variable or parameter in the function.

unusedinspection

Another inspection will let you know if there is a different number of columns in queries used in set operators (UNION, INTERSECT and EXCEPT).

unioninspection

The new intention action offers you to introspect the schema or databases right from the editor if DataGrip has no metadata on them yet.

introspectmissing

Some specific features for PostgreSQL users: when you use JOIN USING, DataGrip offers you only the field names common for both tables.

usingcompletion

Find Usages now handles positional parameters references: $1 will be treated as the first parameter’s usage and so on.

findusagesbucks

Navigate to the next method, familiar to many of you from our other IDE’s, now works in DataGrip and is called Navigate to the next statement.  Invoke it by Alt+Up and Alt+Down (Ctrl+Down and Ctrl+Up for OSX).

navigation

Data Dump

We integrated DataGrip with mysqldump and pg_dump. To dump the objects, use the Dump with… option from the context menu.

dumpcontext

This is what the dialogue window for MySQL looks like:

dumpmysql

And here is the one for PostgreSQL. Note that in both cases you can use completion for the console parameters.

dumppostgres

XML extractor comes back

Back in 0xDBE times (remember those?) we had an XML-extractor. Some of you asked to bring it back, and we’ve obliged.

xmlcontext

Here what the extractor’s result looks like:

xmlresult

Other features

When large script files are run from the context menu, now they are executed much faster.

fasterrunscripts

Now DataGrip detects if an old driver is in use and offers you to update it.

driverversions

You might have noticed the new icons! We hope you’ll like them.

icons

Other fixes and enhancements in this release include:

  • SQL Server 2016 grammar support
  • PostgreSQL 9.6 grammar support
  • Many minor objects can now be dropped from the UI
  • Many minor objects are now resolved in the SQL code
  • Rules support in PostgreSQL
  • External tables parsing in Oracle
  • The FiraCode font is bundled
  • Auto-inc support in SQLite
  • Expression index support in SQLite

That’s it! Get your 30-day trial of DataGrip today if you haven’t yet, or just enjoy the new features of DataGrip if you’re our user already. Your feedback is welcome in our twitter, forum, and the issue tracker. Let us know what you think!

Your DataGrip Team
_
JetBrains
The Drive to Develop

Posted in Features, Releases | Tagged | 9 Comments

DataGrip 2016.3 RC is Out

Hi! We are rushing to the release in the end of November, and here is the release candidate for 2016.3!

Among various bug-fixes a couple of new features were added since the last EAP:

Navigate to the next method, familiar to many of you from our other IDE’s now works in DataGrip. It’s called Navigate to the next statement and should be invoked by Alt+Down and Alt+Up (Ctrl+Down and Ctrl+Up for OSX).

navigation

If you run large script files from the context menu, please know that now they are executed much faster.

fasterrunscripts

We’ll be happy if you try this build and follow us not to miss the huge blog-post about all new features in this release!

DataGrip team

Posted in Releases | 4 Comments

Another EAP build: Data conversion, materialized views in PostgreSQL and more

Bonjour! We are rushing to the release and here is a new bunch of features you can already try in the DataGrip 2016.3 EAP.

The most notable feature of this build is data conversion. Now you can copy-paste your data even if the fields have different types of data, and moreover, even if the tables are in different databases from different vendors!

Since this release also brings you multiple cells edit, this will work with the whole column of data as well. Date to string, bool to integer — not a problem. Our loyal EAPers already know: edited rows are colored and stored locally before you submit your changes. Well, with 2016.3 you’ll get a powerful data editor, won’t you?

convertgifbig

Select Next Occurrence (Alt/Ctrl+G) action now works in data editor. Even if several cells are selected.

findoccurence

PostgreSQL users will be glad to know that we now fully support materialized views. It means that DataGrip lets you edit their source code, refresh them from the UI, and search for usages of objects inside them. And just a reminder: finding usages inside views is also a new feature of 2016.3. Please remember to refresh the schemas of your database to get this support.

matviews

Triggers, which are also supported in this version, now can be dropped from the UI.

droptrigger

If you run large script files from the context menu, please know that now they are executed much faster.

runscsipts

And maybe you’ve already noticed the new icons! We hope you like them.

icons

That’s all for today. Your feedback is welcome in our twitter, forum, and the issue tracker. Let us know what you think about 2016.3!

Your DataGrip Team
_
JetBrains
The Drive to Develop

Posted in EAP, Features | Leave a comment