Philippe Malera
Member²
Menu : Tools / Preferences / Compiler / Conditional Compilation Flags
I noticed a dangerous behavior with this setup.
If you set a specific flag for your session, it automatically delete all existing systems flags.
In our case, we have system flags to identify test or production environment, they are used to compile differently according to environment.
If a user specify a custom flag just for him in this setup and he compile something, this often lead to major issue as the system doesn't know if he is in a production db or not.
Actually the only way to prevent such issue is to tell developers to never set any flags in this setup.
But the clean solution would be that PL/SQL Dev MERGE session flags with system flags rather than replacing them.
And also nice to have :
Possibility to define flags according to connection.
I noticed a dangerous behavior with this setup.
If you set a specific flag for your session, it automatically delete all existing systems flags.
In our case, we have system flags to identify test or production environment, they are used to compile differently according to environment.
If a user specify a custom flag just for him in this setup and he compile something, this often lead to major issue as the system doesn't know if he is in a production db or not.
Actually the only way to prevent such issue is to tell developers to never set any flags in this setup.
But the clean solution would be that PL/SQL Dev MERGE session flags with system flags rather than replacing them.
And also nice to have :
Possibility to define flags according to connection.
