Compile PL/SQL Package and loose 'Create Or Replace" and package schema

Hi Mike,

As far as I know, the ‘Submit’ action does generate the expected syntax:

Alternatively, you can use the “Generate DDL to Query Console” action on the package to view the actual generation script:

Hello @..., however if we wanted to compile changes in packages this way, we would not get compilation errors. It just submits and check, if it was compilated successfully. If not, you have no way to see compilation errors.

So I also have to insert the “or replace” keyword, mark whole code and execute it. That gives back “Object has changed in database” warning, so I always have to “Revert local changes”. Or firstly compile via code execute and then submit.. 

If you know some workaround, I would be glad to know it. 

Hi Matej,

So I also have to insert the “or replace” keyword, mark whole code and execute it. That gives back “Object has changed in database” warning, so I always have to “Revert local changes”. Or firstly compile via code execute and then submit.

Can you explain your scenario and why you would get a notification of changes if submitting a change to your package when executing CREATE OR REPLACE statement? 

Hello, 

I open package body from object browser 

lets say i wanted to inject some code there, but break the package along the way

If I pressed submit, it would be changed in the cached data and compiled in background, but I do not get the error this compilation raised. 

Only way to get to this information is to inject or replace keyword and execute the code (marking it, pressing execute shortcut)

This way i get to the error log: 

Realizing my mistake, I fix the code, but I am not sure if more compilation errors won't be raised - therefore I execute the code same way as before - marking the code and executing - if compilation was successfull i do get  banner raised immediately: 

So I also have to revert local changes to finish this properly (or wait for auto-sync). 

That's the workflow I would be forced to take as of now, if I wished to use database objects. We have our packages in repository as files and we compile from there, not using the object browser at all. 

If you have any suggestion to better workflow to change package without having to inject “or replace” keyword, get compilation errors, and also immediately refresh cached data - I am looking forward :) 

Thank you,

Matej 

Hello Aleksandr, 

thank you for acknowledging the issue. 

The best solution, as of me, would be to simply propagate compilation errors raised within submit button. 

Thank you!