Modifying source code of database objects
DataSpell tracks changes that you make to objects that store their source code in the database. These objects might be triggers, procedures, functions, views, or other objects. Every modification that you make to these objects in the editor is saved as a local version of the object source code.
Updating source code
DataSpell retrieves the information about a database during the introspection process. This information is used to show the objects in the Database tool window, display their DDL, suggest them during completion, and in other features for code assistance.
You can update the source code of database objects directly by editing their DDL and submitting your changes. The IDE will generate a migration script and execute it in the database.
The Database Changes tool window displays a summary of all your changes.
Load source code for a data source
DataSpell retrieves the source code for a data source during the introspection. You can manage this process in the data source properties.
In the Database tool window ( ), click the Data Source Properties icon .
Select one or more data sources for which you want to download source code.
Right-click the selection and navigate to. You can select between the following options:
None: do not download source code.
Except System Schemas: download source code for all the objects except for system schemas.
All Schemas: download all the available source code.
Edit source code of an object
You can update the source code of database objects by directly editing their DDL
CREATE scripts and submitting your changes in the editor. The IDE will generate a migration script with your changes, prompt you to verify it, and then execute it in the database.
Right-click an object and select. Alternatively, press Ctrl+B.
Make changes to source code.
(Optional) In the Database Changes tool window ( ), double-click the modified object to open a difference viewer and verify your changes.
Click Submit ().
When you press the Submit button () in the Database changes tool window, you see the Migration dialog. The Migration dialog displays a migration script for the object.
In the Object Migration dialog, verify that the migration script is correct and press OK.
A migration script is code that changes all database or a part of it. You can use migration scripts to add or remove a column, upgrade the database version, or change column properties.
DataSpell can automatically generate a migration script, but you must check it before running.
See all the changes in source code
Selectfrom the main menu.
See the difference between modified and stored versions
In the Database tool window, double-click the modified database object.
When you edit source code of any object, DataSpell tracks changes and highlights them in the gutter. For example, add a comment line to a routine or a trigger function. The added line becomes highlighted. If you click the highlighted line in the gutter, a small toolbar is displayed with the Show Diff button. You can click the Show Diff button () to see the difference between the code that you added and the one from source code.
In the Database Changes tool window ( ), double-click the modified object to open a difference viewer and verify your changes.
Outdated cached objects
DataSpell caches the source code of all the objects from the database to provide fast code assistance and navigation. If an object that you opened was updated from a third-party location, you will see a notification that the cached object differs from the source code of the same object in the database.
If you see this warning in the IDE, you can select between the following actions:
Synchronize: fetch changes from the database and update the cached local object.
Disable check: disable this notification.
Also, there might be a conflict between your version of the object source code and the one in the database. For example, when you has modified the same source code as someone else and pressed Submit (Ctrl+K).
You can forcefully replace source code of the object in the database (Force Refactoring) or synchronize the object state and then proceed with changes (Abort Refactoring and Synchronize).
If you selected Abort Refactoring and Synchronize, DataSpell aborts the submit operation and fetches changes from the database (just like if you pressed Synchronize Ctrl+F5). If the conflict still exists, you will see the following notification.
In this notification, you can select between the following options:
Revert local changes: roll back all your changes and replace them with the version from the database.
Keep local changes: use your changes and overwrite changes in the database.
Merge: display the diff dialog to merge two versions of the object source code.
Colors of the object state
By default, all the objects are displayed in black. It means that the current state of an object source code does not differ from source code of the same object on a server.
If source code of the object has been changed but there are no conflicts with the object source code on a server, the object is displayed in blue.
If there are conflicts in source code of a local object and the same object on a server, the object is displayed in red. If you open such object in the editor, you will see a notification about conflicts.
For example, on the following screenshot, the
Do_Something procedure is modified but contains no conflicts, the
V1_trg_i trigger was modified and conflicts with source of the same trigger on a server, other objects are not modified.
Controls of the Database Changes tool window
Tooltip and shortcut
Submit local changes to the database server. See Submit changes to a database.
Roll back changes. This button is available only for the manual transaction mode. See also, transaction modes and isolation.
Compare two versions of source code.
Group objects according to their type. For example, routines, rules, or views.
Expand all nodes in all trees.
Collapse all nodes in all trees.