RE: RE: 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.

Thank you so much!

Kind regards,
Cindy
Senior Project Manager
Canada WCBU FDC Consolidation Project
Sharepoint Site: http://sptpmo.conocophillips.net/sites/projects44/wcbu_fdc/default.aspx
Phone: 403-532-5326
Cell: 403-615-4541
Office: 17SE 2.02

Dial In Number:
USA: 877-953-9609
Canada: 1-877-953-9609
Participant Passcode: 4929478

From: Stephen Beausang [mailto:bounce-StephenBeausang_734@toadworld.com]
Sent: Friday, August 23, 2013 12:25 PM
To: toadoraclebeta@toadworld.com
Subject: [EXTERNAL]RE: [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.

RE: 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.

Reply by Stephen Beausang

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.

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.