The plugin allows for effective reverse engineering of an existing Exasol database. This comes very handy during migrations, or when comparing the model versus what is really implemented in a database. Specifically, for Exasol we have added support for reversing of whatever Exasol offers: partition by, distribution key, virtual schemas, sizes of objects, scripts, UDF, etc. Moreover, to improve the default behaviour of PD, we are not throwing everything into one basket. Instead, we are separating each Exasol database schema into its own package and create a separate model diagram for each. It really helps to keep things organized, eases model readability and identification of objects, but on the other hand, does not limit the developer in cooperation with other objects. This can be adjusted to your specific needs, based on the database design. For example, each schema can be reversed as a separate model.
Reverse engineering process is fully configurable using numerous filters. We are adding a special functionality, to identify proper schema for an object (missing in default PD overview), hence you are free to filter by schemas, owners, object types etc.
Pic.: Reverse engineered Exasol database into 5 packages – for each schema. Easily expandable and explorable, with it’s own diagram and associated objects for each.