Package changes not showing up.
GaffApr 7 2010 — edited Apr 8 2010Hi:
We recently upgraded to SQL Developer Version 2.1.1.64 and are seeing behavior that differs from an older version (sorry, don't have that version # but it was about a year ago).
Our developer is opening a file to get to the package source (as opposed to moving down the object tree from the connection in the left pane) and compiling it after changing the source. It happens to be a subversion (Tortoise) controlled source folder but SQL Developer knows nothing about that (as far as I know!). We haven't created a repository from within SQL Developer (that's another issue).
So the developer makes the changes and runs the package and sees those changes. But for everyone else that runs the package, they see the old behavior. I don't even understand how this is possible! There's one version of the package in Oracle at any time. The developer changed it and saw the changes. How can another user NOT see those changes?
Q1: How is this happening physically?
Q2: What needs to be done in order to expose the new behavior to all other users?
Thanks.