Toad Edge provides a way to reuse queries by using variables instead of specific values. These variables can be given value each time you execute a query.
To bind and use variables
To make writing scripts and editing JSON data easier, Toad Edge offers a convenient tool - Content Assist (also known as Intellisense). This utility automatically suggests keywords or templates you might want to use when you are working with Worksheet or JSON support and JSON Editor
Content Assist can be displayed in two ways:
In this environment, Content Assist suggests various relevant SQL keywords depending on the context of your query. It also suggests default or custom Templates.
Once you open JSON Editor, you can invoke Content Assist to utilize JSON templates. Instead of worrying about closing brackets and quoting keys properly, you can simply insert the key-value structure and just fill in the values.
The Copy Table tool is convenient for when you need to copy an entire table with all its contents to the same or a different database.
NOTE: You can only copy tables between databases of the same connection.
To copy a table:
Version control systems (VCS) are not a part of database systems by default. However, Toad Edge™ offers a way to apply version control to any supported database by mapping it to a file system as a folder structure where each object is represented by a JSON file. The resulting structure is referred to as a "repository". It can be tracked with any VCS and it can be also synchronized with any other database of the same platform and version using Schema Compare.
To map a database to a file system
Your database is now mapped to the file system. The path to the folder structure is displayed next to the database icon in Object Explorer.
Object Explorer also displays the synchronization status of all objects in the database.
The following table lists all possible states indicated by the object decorators and the action suggested once you synchronize database and repository:
|A new object was added to database that is not present in repository||Change target||You added a new object to your database. Toad Edge assumes you want to add the object to your repository as well|
|An object was deleted from repository, but it still exists in database||Change source||You deleted an object in your repository. Toad Edge assumes you want to delete the object from your database as well|
|/||An object was probably modified in database / repository||None||You modified an object in your database / repository. These changes have been detected by Toad Edge but they have not been confirmed yet. To confirm and resolve them, Synchronize the database and the repository|
|/||An object was confirmed to be modified in database / repository||Change source / target||You modified an object in your database / repository and synchronized them afterwards. Toad Edge assumes that when you modify an object on one side you will want to modify on the other side as well.|
|An object was possibly modified in both database and repository||None||You modified an object in both your database and your repository. These changes have been detected by Toad Edge but they have not been confirmed yet. To confirm and resolve them, Synchronize the database and the repository|
|An object was confirmed to be modified in both database and repository||Change both||You modified an object in your database / repository and synchronized them afterwards. Toad Edge assumes that when you modify an object on both sides, you will want to decide which specific changes should be applied in the source and the target|
|An object has not been added to repository yet, its state is unknown||Change target||You mapped your database to a file system (repository), but you have not synchronized them yet. Synchronize the database and the repository in order to copy the objects from your database to the repository|
To remove mapping of a database to a file system
To synchronize a mapped database with a repository
The process of synchronization of a database and a repository is very similar to Schema Compare.
For this reason, please see About Schema Compare to learn more about the synchronization process.
NOTE: When synchronizing a database and a repository, it is currently not possible to use the Change both resolution action to resolve specific differences.