Critical Defect (Toad v12.0 and v12.1) – Team Coding is NOT LOCKING a CHECKED object or file to prevent other developers from working on the same object. This defect exists in Toad v12.0 and v12.1 beta.
- See screenshot #1 in attached document. The screenshot is the view for Oracle User CINDYK looking at the Team Coding Dashboard. Oracle User CINDYK sees 2 items (one object and one script) in Checked Out status, but these items should be locked to CINDYK. CINDYK can revise these items.
- Oracle User GENT_APPDBA checked out PROCPRINTPROCESSINPROGRESS procedure. This object should be Locked to CINDYK.
- Oracle User TCOMBILL checked out Create product_seq Sequence script. This script should be Locked to CINDYK.
- See screenshot #2 in attached document. This screenshot is the view for Oracle User CINDYK in SQL Navigator 7.0. In this case, Team Coding is correctly locking the 2 items so that CINDYK cannot modify them.
I hope this can be fixed in this next release.[View:~/cfs-file.ashx/__key/communityserver-discussions-components-files/86/Defect-Team-Coding-CHECK-OUT-Not-Locking-File-2D00-Toad-v12-and-v12_2D00_1-Beta-Testing.docx:550:0]