The developer, John and I discussed this before 12.9 was released and could not really come up with an ideal way to handle this case, so this is very good feedback.
Our goals is to make this as straight forward as possible as to not cause confusion to users, as most users don’t use both VCS for scripts and Team Coding to control DB objects. Having a button for “Add to VCS” act on full files and “check out” work on DB objects that may be referenced in files can definitely cause confusion. In your case, however, I can definitely see where you would always want that button enabled. You are correct in that the enablement of that button is currently acting based off of caret position, or should be at least. If your caret is on a controlled object it should be disabled but when it’s not on a controlled object it, enabled. I was definitely incorrect with my last post. I get confused because we have gone through these scenarios so many times and have changed the behavior frequently.
I also understand your other point where you want to control DDL in scripts (VCS files). Toad can generate different DDL depending on your export DDL options. This was one of my biggest concerns when the decision was made to control tables/constraints/indexes in TC. I honestly can’t comprehend how using TC to version these objects could be managed, this is a big reason we wanted users to be able to manage scripts along side with controlled DB objects.
If we make this a little more solid with the current behavior will that work for you? If your caret is on that trigger and that trigger is controlled, that button should have been disabled. If you want to save this script just place your caret elsewhere to enable the button.
From: herald.ten.dam [mailto:email@example.com]
Sent: Wednesday, July 20, 2016 9:23 AM
Subject: RE: [Toad for Oracle - Beta Discussion Forum] Alter table scripts not possible to add to VCS
RE: Alter table scripts not possible to add to VCS
Reply by herald.ten.dam
this is not quite correct. I had script like this:
Alter table xxx …
alter table yyy…
This will disable the button.
If I add a " select sysdate from dual" at the top, the button is enabled, although the script has still the alter statements. I can even add “alter trigger xxx_br disable” at the top and the button is enabled. All triggers are controlled by TC btw. So the check for objects looks not fully solid.
Is it possible to make an option if you want to enable/disable this option. I need to make these scripts, because I use 1 schema for this, and can’t make diffs with other schema to show the differences. And 1 button in Toad is nicer than going to GIT for an ADD/COMMIT action.
Another option which I would prefer is that the content of the script put in VCS for a table isn’t the same as the script generated in the schema browser (the most preferred script on checkin would be the diff between current vcs and the database, but that will be a very hard 1 ). These are now related, if I forget for example the Drop option, then I get also the drop in VCS and that is not always nice for a release (the script will stop, or a table is deleted in another environment). Now I have to check everytime before making the releases form the vcs.
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Unsubscribe from Toad for Oracle - Beta Forum notifications altogether.
Toad for Oracle - Beta Discussion Forum
this post as spam/abuse.