"Compile with PL/Scope" action: compiling private and public synonyms should be separate choices

[rvo-cs]

As of v1.0.0, the "Compile Synonyms?" prompt controls recompilation of both private and public synonyms. It should be possible to distinguish between the two, by splitting this choice into 2 separate prompts, respectively labeled:

• "Compile Public Synonyms?"
• "Compile Private Synonyms?"

Reason: private synonyms are part of the target schema, whereas public synonyms are not; recompiling the latter is more likely to cause invalidations in other schemas (distinct from the target of the action), whereas recompiling private synonyms could result in invalidations in other schemas, but only indirectly. Therefore, handling the 2 separately would provide a greater degree of control.

Additionally, the default value of both prompts should be "No".

Reason; because of the potential for invalidations in other schemas, recompiling public synonyms should be left to users who know what they are doing, hence "No" by default. Using the same default for private synonyms would then be necessary, otherwise the dialog box of the action would seem inconsistent.

[PhilippSalvisberg]

Reason; because of the potential for invalidations in other schemas, recompiling public synonyms should be left to users who know what they are doing, hence "No" by default. Using the same default for private synonyms would then be necessary, otherwise the dialog box of the action would seem inconsistent.

As mentioned in #55 the scope of the public synonyms is reduced to objects of the current schema. So, the current user is responsible for this public synonym. If not, he should not have the rights to create and drop public synonyms.

Instead of splitting the the option into public and private synonyms I think about removing the option. It would be consistent with the other object types for which not such an option exists.