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.

cindy.kennedy · August 23, 2013, 10:47am

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]

Thanks, Cindy

Stephen.Beausang_734 · August 23, 2013, 11:24am

Cindy, I am looking in to this.

Stephen

From: Cindy Kennedy [mailto:bounce-cindykennedy@toadworld.com]

Sent: Friday, August 23, 2013 1:48 PM

To: toadoraclebeta@toadworld.com

Subject: [Toad for Oracle - Beta Discussion Forum] 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.

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.

Thread created by Cindy Kennedy

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. Defect
Team Coding CHECK OUT Not Locking File - Toad v12 and v12-1 Beta Testing.docx

Thanks, Cindy

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - Beta notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag
this post as spam/abuse.

fabrice.boin · June 26, 2014, 2:21am

Hello,

we are looking pour TOAD too, and we have the same issue, is it corrected in th 12.5 ?

Thnaks for reply

Fabrice

Stephen.Beausang_734 · June 26, 2014, 4:54am

Hello

This issue is fixed and logged in version 12.1.0.20 internal CR 111887.

To the best of my recollection it is working correctly since 12.1 GA .

Stephen

From: fabrice.boin [mailto:bounce-fabriceboin@toadworld.com]

Sent: Thursday, June 26, 2014 5:22 AM