2019.3

Hello, Here is the fourth bug-fix update for DataGrip 2019.3. Better subquery folding Based on DBE-10131, we’ve added a new option for subquery folding: Important bug-fixes – DBE-10189: Wildcard is used for Preview update when the table is unresolved. – DBE-10125: Fixed the false positive in the Unused expression inspection. – DBE-9988, DBE-10134: Fixed the false positive in the Redundant COALESCE inspection. Thanks! The DataGrip Team

Hello, Here is the third bug-fix update for DataGrip 2019.3. Important bug-fixes The right schema is used when adding a foreign key constraint to a table. DBE-9743 Auto sync is working after a DROP followed by a CREATE statement. DBE-9980 No more freezes in JOIN completion. DBE-9844 Thanks! The DataGrip Team

Hello! This is the second bugfix update for DataGrip 2019.3. Here’s what it has inside: Virtual foreign keys We’ve introduced the concept of virtual foreign keys. You can use this concept in the event that you need to use a relationship that exists but is not located in your database.! Doing so will help you: – Have the proper completion when writing JOIN clauses. – See the relations in diagrams. By default, DataGrip tries to guess if you have relations between columns whose names contain id. It looks like this: These relations are also displayed in the diagram. If you don’t want them to

Hello! This is the first bugfix update for DataGrip 2019.3. Here’s what it has inside: DBE-9708: A new option lets you choose whether you want to use schema qualifications when using JOIN. DBE-9736: The table filter is cleared when opening a table from the database explorer. DBE-9743: The correct schema is used when adding a foreign key. DBE-9728: Fixed the bug with queries seeping into column names. DBE-9714: Right-clicking on a column header shows the menu again. DBE-8196: A new registry option to remove the schema qualification when updating data.

Hello, today we have a new build for the DataGrip 2019.3 EAP for you to try. DBE-7976: The Modify Table action is now available from the data editor context. Want to add a new column while editing table data? Just press Ctr/Cmd+F6 and go ahead! DBE-9336: Intentions now work inside the source code of routines. For example, if you want to expand the wildcard via Alt+Enter on an asterisk, now this is possible. DBE-9548: Now if your result-set contains multiple columns with the same name, you won’t have any problems with ambiguous names if you create a table from it. DBE-9428: A new inte

Hello! It’s time for a new EAP build for 2019.3 which is due for release this December. Tree data view We’re continuing to build on the MongoDB support. We’ve just crossed another milestone with this process by adding the tree data view. To turn it on, click the Gear icon -> View as... -> Tree. Inline query progress Now you can clearly see when your query is running: there is a spinning icon on the gutter and the inline live timer as well. Flame chart for explain plan We’ve added a new type of visualization for the explain plan results. To see it, click the corresponding button on t

Hello! It’s time for the new EAP build for 2019.3 that is going to be released this December. Let’s take a look at several new features. Oracle PL/SQL debugger We’ve started working on a debugger for Oracle PL/SQL. Right now, it provides just basic functionality: you can debug procedures, functions, triggers, anonymous blocks and observe variables there. Updates to this feature and additional information will appear in the corresponding issue. Search with Google for connection error It’s now easier to deal with connection errors! When a connection fails, it’s possible to Google the error te

Hello! We have begun our DataGrip 2019.3 EAP and there is something really exciting inside. MongoDB support Finally, the day has come for us to start working on MongoDB support. After more than 400 votes we have decided now is a good time to begin including at least some very basic functionality. What actually works now: Introspection You can observe collections and fields in the database explorer. We fetch the first 10 documents from each collection to get information about the fields. This can be customized via the JDBC parameter fetch_documents_for_metainfo which is available in the Adva