DataGrip didn’t explicitly know what controls the Modify dialog would be populated with, though. The only good approach here was to generate the UI on a metadata basis, so that whatever the object has inside would find its way to the UI. In each database engine, objects have lots of specific attributes, and we would like our users to have the UI to see and edit those attributes. We could manually design the dialog for 3 or maybe 5 databases, but not for 25 of them. However, the main reason was that with so many supported database engines, DataGrip just could not provide a powerful UI for objects in each of them. There were some usability issues, like expanding the UI, which we admit was not the best idea. Why the new UI?Īt some point it became clear that the whole Modify Object UI had to be rewritten from scratch. Before listing what we’ve improved, let us give you a bit more background info about how the new UI came about. This bug-fix update is focused on enhancing the new Modify Object UI.

Download datagrip 2022