Export User Objects - some improvements needed

[Maxmix]

As always, I struggle to prepare scripts to distribute changes (including privs, synonyms, etc) from DEV db to multiple PRODs.

This time, I manually made the list of all the objects (.OSF file), that are new/changing/to be deleted in PROD dbs.

Now I opened Export User Objects module and am enumerating schemas, participating in deployment. For each schema, I am calling Load Object Selection and load my .OSF file. As the result, all objects present in both my .OSF file and selected user's schema are selected and ready for export.

Now to the problems:

1. When I have both package Pack1 and package body Pack1 selected in the list, then only package body will be exported, because PLD unloads them one after another into the same filename, Pack1.sql (option File per object is in use, as I do not want mix specifications and bodies).
2. If only I could choose multiple schemas... Then I had all my objects exported in one gulp!

 

[Marco Kalter]

Perhaps you can define different extensions for package specificatiosn and bodies? You can do so through Tools > Preferences > Files / Extensions.

 

[Maxmix]

Yes, I can, but others could lose their stuff, because it's counter-intuitive. I see that views are unloaded as .vw -files. You might assign a new dedicated extension for package-bodies, perhaps?