Thank you for using Gitora and bringing sanity to PL/SQL.
You can use PL/SQL API’s to connect to Gitora from any PL/SQL development tool. There is a nice tutorial at http://blog.gitora.com/introduction-to-gitora-git-for-plsql-developers/ . I recommend you to read the whole document before using Gitora but here is the relevant excerpt regarding the PL/SQL API’s to log in to Gitora from any PL/SQL editor:
Editing a Database Object Managed by Gitora
Developers may continue using their favorite PL/SQL editor to edit database objects managed by Gitora. Since Gitora is implemented at the database level, it works with any editor.
Once a database object is part of a repository, Gitora will only allow changes to it from database sessions which have a logged in Gitora user and if the database object is not already checked out by another user.
Gitora has an API package called api_gitora.
The API’s in api_gitora are as follows:
login(in_user_cd varchar2, in_password_tx varchar2) :signs in to Gitora with a valid Gitora user name and password
logout;signs out of Gitora
checkOutDBObject(in_schema_cd varchar2, in_type_cd varchar2, in_name_tx varchar2); Locks the specified database object for the logged in Gitora user.
releaseDBObject(in_schema_cd varchar2, in_type_cd varchar2, in_name_tx varchar2); Releases the lock on the specified database object owned by the logged in Gitora user.
addDBObject(in_schema_cd varchar2, in_type_cd varchar2, in_name_tx varchar2, in_repoName_tx varchar2); Adds a database object to a Gitora repository.
There are four more API’s in api_gitora that are used by Gitora internally to manage database objects.Use the TYPE_FUNCTION, TYPE_PACKAGE, TYPE_PROCEDURE, TYPE_SYNONYM, TYPE_TRIGGER, TYPE_VIEW constants in the api_gitora package as input values to the in_type_cd parameter in the API’s.
Use the checkOutDbObject API to check out a database object. During a save, Gitora automatically attempts to check out a database object if the database session has a logged in Gitora user. If the object is already checked out by another developer, Gitora prevents the save with an appropriate error message. Developers may also use the Gitora Code Manager and check out a database object from the navigation tree by right clicking to it and selecting the check out menu item from the pop up menu.
So to log in to Gitora from any PL/SQL editor all you need to do is to execute:
After you execute this line of code, the database session the code is executed in will be logged in to Gitora and Gitora will allow you to edit the checked out code units.
Please note that, several PL/SQL Editors open new database connections for each window they open. So, if you are not careful, you might be signed in, in a window but then still receive an error in the other window. The login procedure only signs you in to Gitora in the database session it is executed in.
Hope this helps.