[14.2.43.993] Wrong point-in-time for package locked message

Toad for Oracle - Beta
1

We have some of out databases configured for VCS (we use GIT). When we start 14.2.43.993 Beta, open one of our databases, open a package in the editor that we checked out earlier ourselves, change e.g. a comment and try to compile, the error "The package is locked by... Team Coding prevented compilation." is shown before any VCS logon is presented. This should happen later, after the VCS logon, and only when the user doesn't fit.

2

Hi Rainer,

I see the issue you're referring to. Team Coding should prompt you to log into the VCS provider before it attempts to compile the object and it's not doing that. I've created a ticket to get this resolved here soon. I'll let you know when it'll be ready in an upcoming beta.

Thanks for bringing this to my attention! I'll get this fixed as soon as I can.

-John

3

:+1:t2: :+1:t2: :+1:t2:
I look forward to the bugfix. You guys at Quest are really good and quick.

Best regards
-Rainer

4

Hi Rainer,

This should be fixed in Monday's beta. Feel free to give that a shot then and let us know if you run into anything else.

Thanks again!

-John

5

Hi John,

it works again as expected in the newest beta. Team coding login is prompted immediately when I try to compile.

Thanks!!!

Best regards,
Rainer