Jira

Building the JDBC URL

After installing the license, access the connection management page by executing the command java -jar kingswaysoft.jdbc.jar. Enter the necessary details, and the program will automatically generate the JDBC connection URL. Users can click Test Connection to test the generated URL and Copy to Clipboard to copy the connection string for use within the application where the JDBC driver is being used.

Note: If the license is not installed, you can still use the connection manager to generate a JDBC URL; however, the 'Test Connection' feature will be disabled.

General Page

The General page allows you to specify connection properties and login credentials for the Jira GraphQL service:

General Settings

API Throttle Rate

The API Throttling Rate will limit the number of requests that can be sent per the selected unit of time. Set this value to 0 to disable API throttling.

Enable Preview Api Features

Enabling the option Enable Preview Api Features allows the use of fields marked as 'beta' and 'experimental'.

Authentication

Authentication Mode

The Authentication Mode option allows you to choose the method used to authenticate with the Jira GraphQL API. Available options are:

• OAuth
• Basic
• Personal Access Token

Authentication Methods for Jira

Test Connection

After all the connection information has been provided, click the "Test Connection" button to test if the user credentials entered can successfully connect to the selected service.

Advanced Settings Page

Using the JDBC Driver

Explore detailed examples in this section that demonstrate the application of JDBC classes such as Connection, Statement, and ResultSet to effectively manage interactions with Jira data. This section covers the use of regular statements and prepared statements for executing complex or frequently executed queries.

Executing Statements

Once you've connected from your code (see Connecting with DriverManager and Connecting with DataSource), you can execute SQL statements using the Statement class. Refer to the Executing Prepared Statements section for information on how to execute parameterized statements.

SELECT

Use the Statement class's generic execute method or the executeQuery method to execute SQL statements that return data. To retrieve the results of a query, you would then call the getResultSet method of the Statement.

String sql = "SELECT * FROM apps";
try {
    ResultSet resultSet = statement.executeQuery(sql);
    LOGGER.info(resultSet.toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

INSERT

Use either the generic execute method or the executeUpdate method of the Statement class to execute an INSERT operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the inserted data's ID, exceptions raised during execution, and details of the affected data.

String sql = "INSERT INTO app (name, description) VALUES ('AppName', 'Added using Jdbc Driver')";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

app-id,errorcode,errormessage,processdata,haserrors
ari:cloud:ecosystem::app/2c3e0f0f-46aa-4252-9f6c-a0e90fd09ef4,null,null,{"var1":{"name":"AppName","description":"Added using Jdbc Driver"}},false

UPDATE

Use either the generic execute method or the executeUpdate method of the Statement class to execute an UPDATE operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the updated data's ID, exceptions raised during execution, and details of the affected data.

String sql = "UPDATE appDetails SET description = 'Updated using Jdbc Driver' WHERE appId = 'ari:cloud:ecosystem::app/2c3e0f0f-46aa-4252-9f6c-a0e90fd09ef4'";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

app-id,errorcode,errormessage,processdata,haserrors
ari:cloud:ecosystem::app/2c3e0f0f-46aa-4252-9f6c-a0e90fd09ef4,null,null,{"var1":{"appId":"ari:cloud:ecosystem::app/2c3e0f0f-46aa-4252-9f6c-a0e90fd09ef4","description":"Updated using Jdbc Driver"}},false

DELETE

Use either the generic execute method or the executeUpdate method of the Statement class to execute a DELETE operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the deleted data's ID, exceptions raised during execution, and details of the affected data.

String sql = "DELETE FROM app WHERE appId = 'ari:cloud:ecosystem::app/2c3e0f0f-46aa-4252-9f6c-a0e90fd09ef4'";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
null,null,null,{"var1":{"appId":"ari:cloud:ecosystem::app/2c3e0f0f-46aa-4252-9f6c-a0e90fd09ef4"}},false

CallMutation

You can use either the generic execute method or the executeQuery method of the Statement class to execute mutations through a "CallMutation" query. CallMutation statements are formatted similarly to Insert statements but require the full mutation name. The field to output can be specified using an OUT parameter located in the columns list prefixed by "OUT". If the mutation has fields to return (see system.functions and system.functions.columns), an OUT parameter is required.

For example, the corresponding CallMutation Statement for INSERT INTO customer (input-email) VALUES ('email') is CallMutation customerCreate (input-email, OUT customer-email) VALUES ('email').

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the mutation data's ID, exceptions raised during execution, and details of the affected data.

String sql = "CallMutation createApp (name, description, OUT app-id) VALUES ('AppName', 'Added using Jdbc Driver')";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

app-id,errorcode,errormessage,processdata,haserrors
ari:cloud:ecosystem::app/2c3e0f0f-46aa-4252-9f6c-a0e90fd09ef4,null,null,{"var1":{"name":"AppName","description":"Added using Jdbc Driver"}},false

Executing Prepared Statements

Using a PreparedStatement can improve performance when you need to execute a SQL statement multiple times with different parameters. Unlike a Statement object, a PreparedStatement object is provided with a SQL statement when it is created, which can then be executed with different values each time. This special type of statement is derived from the more general class, Statement.

Below are the steps outlining how to execute a prepared statement:

1. Create a PreparedStatement: Use the prepareStatement method of the Connection class to instantiate a PreparedStatement. Refer to Connecting with DriverManager or Connecting with DataSource for information related to establishing connections.
2. Set Parameters: Declare parameters by calling the corresponding setter method of the PreparedStatement. Note: The parameter indices start at 1.
3. Execute the Statement: Use the generic execute or executeUpdate method of the PreparedStatement.
4. Retrieve Results: Call the getResultSet method of the Prepared Statement to obtain the query results, which will be returned as a ResultSet.
5. Iterate Over the Result Set: Use the next method of the ResultSet to iterate through the results. To obtain column information, utilize the ResultSetMetaData class. Instantiate a ResultSetMetaData object by calling the getMetaData method of the ResultSet.

SELECT

Use the Statement class's generic execute method or the executeQuery method to execute SQL statements that return data.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the retrieved data.

String sql = "SELECT * FROM jira/allJiraProjectTypes WHERE cloudId = ";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "4d5812b4-e5c9-4ca8-a815-afac61ef31f3");
    ps.execute(sql);
    while (ps.getResultSet().next()) {
        for (int i = 1; i <= ps.getResultSet().getMetaData().getColumnCount(); i++) {
            LOGGER.info(ps.getResultSet().getMetaData().getColumnLabel(i) + "=" 
            + ps.getResultSet().getString(i));
        }
    }
} catch (SQLException e) {
    LOGGER.error(e);
}

INSERT

Use either the generic execute method or the executeUpdate method of the Statement class to execute an INSERT operation.

The results of SQL queries are saved in a ResultSet. Users can retrieve the ResultSet after execution to view the ID of inserted data, exceptions raised during execution, and the data affected by the insertion.

String sql = "INSERT INTO app (name, description) VALUES (?, ?)";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "AppName");
    ps.setString(2, "Added using Jdbc Driver");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.error(e);
}

app-id,errorcode,errormessage,processdata,haserrors
ari:cloud:ecosystem::app/2c3e0f0f-46aa-4252-9f6c-a0e90fd09ef4,null,null,{"var1":{"name":"AppName","description":"Added using Jdbc Driver"}},false

UPDATE

Use either the generic execute method or the executeUpdate method of the Statement class to execute an UPDATE operation.

The results of SQL queries are saved in a ResultSet. Users can retrieve the ResultSet after execution to view the ID of updated data, exceptions raised during execution, and the data affected by the update.

String sql = "UPDATE appDetails SET description = ? WHERE appId = ?";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "Updated using Jdbc Driver");
    ps.setString(2, "ari:cloud:ecosystem::app/2c3e0f0f-46aa-4252-9f6c-a0e90fd09ef4");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.error(e);
}

app-id,errorcode,errormessage,processdata,haserrors
ari:cloud:ecosystem::app/2c3e0f0f-46aa-4252-9f6c-a0e90fd09ef4,null,null,{"var1":{"appId":"ari:cloud:ecosystem::app/2c3e0f0f-46aa-4252-9f6c-a0e90fd09ef4","description":"Updated using Jdbc Driver"}},false

DELETE

Use either the generic execute method or the executeUpdate method of the Statement class to execute a DELETE operation.

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the deleted data's ID, exceptions raised during execution, and details of the affected data.

String sql = "DELETE FROM app WHERE appId = ?";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "ari:cloud:ecosystem::app/2c3e0f0f-46aa-4252-9f6c-a0e90fd09ef4");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.error(e);
}

id,errorcode,errormessage,processdata,haserrors
null,null,null,{"var1":{"appId":"ari:cloud:ecosystem::app/2c3e0f0f-46aa-4252-9f6c-a0e90fd09ef4"}},false

CallMutation

You can use either the generic execute method or the executeQuery method of the Statement class to execute mutations through a "CallMutation" query. CallMutation statements are formatted similarly to Insert statements but require the full mutation name. The field to output can be specified using an OUT parameter located in the columns list prefixed by "OUT". If the mutation has fields to return (see system.functions and system.functions.columns), an OUT parameter is required.

For example, the corresponding CallMutation Statement for INSERT INTO customer (email) VALUES ('email') is CallMutation customerCreate (email, OUT customer-email) VALUES ('email').

The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the mutation data's ID, exceptions raised during execution, and details of the affected data.

String sql = "CallMutation createApp (name, description, OUT app-id) VALUES (?, ?)";
try {
    Connection connection = buildRestConnectionFromDriverManager();
    PreparedStatement ps = connection.prepareStatement(customSql);
    ps.setString(1, "AppName");
    ps.setString(2, "Added using Jdbc Driver");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    e.printStackTrace();
}

app-id,errorcode,errormessage,processdata,haserrors
ari:cloud:ecosystem::app/2c3e0f0f-46aa-4252-9f6c-a0e90fd09ef4,null,null,{"var1":{"name":"AppName","description":"Added using Jdbc Driver"}},false

Metadata Discovery

This section provides examples on how to retrieve table and column metadata using the getTables and getColumns methods from the DatabaseMetaData interface. These are essential for discovering database structures.

Tables

The getTables method from the DatabaseMetaData interface can be used to retrieve a list of tables.

This method only retrieves tables that are not write-only.

To get a list of tables which include write-only tables, query the table [system.tables](/products/jdbc-driver-pack/help-manual/advancedfeatures#systemtables).

try {
    Connection connection = buildRestConnectionFromDriverManager();
    ResultSet rs = connection.getMetaData().getTables(null, null, null, null);
    LOGGER.info("\r\n" + rs.toString());
} catch (SQLException e) {
    LOGGER.severe(e.getMessage());
}

TABLE_CAT,TABLE_SCHEM,TABLE_NAME,TABLE_TYPE,REMARKS
null,null,actions/actionableApps,Table,
null,null,activity,Table,
null,null,activity/all,Table,
......

The getTables method returns the following metadata columns:

Columns

Use the getColumns method of the DatabaseMetaData interface to retrieve detailed information about database columns. To narrow the results to a specific table, specify the table name using the parameter table_name.

This method returns columns only for tables that are not write-only.

To get columns for tables which are write-only, query the table [system.columns](/products/jdbc-driver-pack/help-manual/advancedfeatures#systemcolumns).

try {
    Connection connection = buildRestConnectionFromDriverManager();
    ResultSet rs = connection.getMetaData().getColumns(null, null, "app", null);
    LOGGER.info(rs.toString());
} catch (SQLException e) {
    e.printStackTrace();
}

TABLE_CAT,TABLE_SCHEM,TABLE_NAME,COLUMN_NAME,DATA_TYPE,TYPE_NAME,COLUMN_SIZE,BUFFER_LENGTH,DECIMAL_DIGITS,NUM_PREC_RADIX,NULLABLE,REMARKS,COLUMN_DEF,SQL_DATA_TYPE,SQL_DATETIME_SUB,CHAR_OCTET_LENGTH,ORDINAL_POSITION,IS_NULLABLE,IS_AUTOINCREMENT,IS_GENERATEDCOLUMN,DTS_TYPE
null,null,app,avatarFileId,12,VARCHAR,null,null,0,0,null,null,null,12,null,null,null,null,null,null,DT_WSTR
null,null,app,avatarUrl,12,VARCHAR,null,null,0,0,null,null,null,12,null,null,null,null,null,null,DT_WSTR
null,null,app,contactLink,12,VARCHAR,null,null,0,0,null,null,null,12,null,null,null,null,null,null,DT_WSTR
......

The getColumns method returns the following columns:

Primary Keys

The getPrimaryKeys method in the DatabaseMetaData interface is used to retrieve metadata about primary keys for a given table in Jira.

try {
    Connection connection = buildRestConnectionFromDriverManager();
    ResultSet resultSet = connection.getMetaData().getPrimaryKeys(null, null, "users");
    LOGGER.info("\r\n" + resultSet.toString());
} catch (SQLException e) {
    LOGGER.severe(e.getMessage());
}

TABLE_NAME,PRIMARY_COLUMN_NAME
users,id
......

The getPrimaryKeys method returns the following columns:

Advanced Features

Additional Bindings

The Statement class's generic execute method and the executeQuery method can both be used to retrieve additional binding entity data. Additional binding entity names are delimited by a slash '/' whereas field names are delimited by a hyphen '-'.

SELECT

To retrieve the results of a query with additional bindings replace the table name with the format entity/binding. To retrieve the results of the additional binding of a specific entity, include a condition with entity-id.

String sql = "SELECT * FROM team/teamV2 WHERE id = '1' AND siteId = 'siteId'";

INSERT

To insert data to an entities additional binding, replace the table name with the format entity/binding. The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the inserted data's ID, exceptions raised during execution, and details of the affected data.

String sql = "INSERT INTO confluence/createPage (spaceId) VALUES ('1')";

UPDATE

To update data of an additional binding, replace the table name with the format entity/binding. The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the updated data's ID, exceptions raised during execution, and details of the affected data.

String sql = "UPDATE team/updateRoleAssignments SET role = 'TEAMS_USER' WHERE organizationId = '1'";

DELETE

To delete data of an additional binding, replace the table name with the format entity/binding. The results of SQL queries are saved in a ResultSet. You can retrieve the ResultSet after execution to view the deleted data's ID, exceptions raised during execution, and details of the affected data.

String sql = "DELETE FROM confluence/deleteComment WHERE id = '1'";

Connection Settings