ClearSQL: synchronization

Editing original data files without making a backup or a copy is no good. To avoid the risk of losing or damaging valuable information, the main principle we instilled into ClearSQL is that you never have to work with sources.

As a first step, you are prompted to create a Project, import scripts to it, and only then carry out necessary manipulations. Imported files can be: PL/SQL scripts, Oracle Forms & PL/SQL libraries, and Oracle database objects, imported from both your file system and Oracle database.

Assuming the source files can be updated, recreated, or dropped without your assistance, it's handy to synchronize imported data with its original sources and work with the latest versions only.

In other words, you can overwrite already imported scripts from their sources and, vice versa, write back changes from the Project to the source (the latter cannot be undone!). Synchronization is flexible meaning you can unlink or relink established connections and check if you are using the latest edition of the code by validating it.

To keep track of the modifications, ClearSQL automatically creates different script versions after each source2project synchronization. The history of changes is saved, so you can always restore the version you need, or compare them against one another. On the whole, there are three types of comparison:

Detected differences are highlighted with distinctive colors and shown in two parallel panes, similar to the UI of typical comparison tools.

Taking into consideration complex structure of PL/SQL systems, with its hierarchy and multi-levelled organization, we empowered ClearSQL with flexible synchronization settings. These allow you to adjust common sync behavior for the whole Project as well as for specific types of imported items.