Team Coding should have its own configuration that would allow the Team Coding Admin to specify if the schema name should be included in the DDL. They should have the choice of including grants, synonyms, and any other option that is currently available to a user creating a script of that object type. The difference between the two is that one configuration is used exclusively by TOAD when creating files that go to Team Coding while the other configuration is the user’s personal setting (this one already exists today).
For the logger lines, I have all 3 check boxes selected. The error never wrote out to the log file that I can find. The root of the TFS issue was that someone changed the “Advanced->Use Custom Collection” value to something that didn’t work. Maybe you can use that to see if you can reproduce the logging issue.
I would be happy to add an entry to the Idea Pond (I’ll do that right now). Again, the issue I have is that it appears TOAD is broken when TFS is not accessible. If someone attempts to compile code managed by Team Coding, TOAD just sits there. It gives the impression that the Compile button is broken.
From: John Bowman [mailto:firstname.lastname@example.org]
Sent: Thursday, June 29, 2017 12:35 PM
Subject: RE: [Toad for Oracle - Discussion Forum] TOAD/TFS Integration - View Contains Schema Owner in Script
RE: TOAD/TFS Integration - View Contains Schema Owner in Script
Reply by John Bowman
I really like the concept of having a separate configuration for Team Coding. When we were talking about it internally before drafting the email, that is also what we thought should be the solution which would allow items being checked in to follow one standard while everyone’s personal configurations remaining intact.
I’m not sure I’m following what you’re saying here. Can you explain a bit further what you were thinking should be the solution? I just wanted to make sure we’re on the same page.
What I find interesting is that the “Output Window” shows the error while the Log File does not.
It sounds like you may not have all the logging options you need checked in the configuration window. In the Logging section of Team Coding’s options (Team Coding -> Configuration -> User Settings -> Logging), there are three options:
- Log Team Coding messages in the output window - will output basic Team Coding messages like “Check-in successful” or "Check-out failed. Reason: " to the output window
- Log VCS commands in the output window - will include the VCS requests and responses in the output window
- Enable VCS debug logging - will output all VCS debug logging to an external file which can be referenced later
The VCS debug log will include the VCS commands with their requests and full responses for later debugging in case there was a problem on the VCS end. If there was a problem there, you should definitely see the error in that file. Are you not seeing that?
In addition, I would expect that if I ask for a DB Object/file to be checked out, and it fails to work, that I would be notified on the screen of such a failure. Can the exception handling be improved so that on failure that a pop-up window is created showing the error that was encountered?
We felt that popup error dialogs would be far too intrusive to the user if a failed action happened, and instead opted for outputting the failure to the output window. If you’d prefer it to display a physical error dialog anytime a failure happens, that is a user option we could easily add. I’d be curious if there were others who felt that way first. Would you consider adding an entry to the Idea Pond on Toad World so it could receive feedback from other users?
In the meantime, it sounds like the best option for you guys might be to enable the first and third options within the Logging options of the configuration window. That way, you can see errors output to the Output Window without it getting cluttered by VCS commands, while the VCS commands and responses could get output to the external VCS debug log. Would that work for your situation?
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Unsubscribe from Toad for Oracle Forum notifications altogether.
Toad for Oracle - Discussion Forum
this post as spam/abuse.
***** This email is from an external sender outside of the CenterPoint Energy network. Be cautious about clicking links or opening attachments from unknown sources. *****