GraphQL

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 a license is not installed, you can still use the connection manager to generate a JDBC URL, but the 'Test Connection' feature will be disabled.

There are sixteen ways to connect to GraphQL

AWS Signature

Version 4

Input an Access Key, Access Secret, Session Token, Service Name and select an AWS region to establish a connection.

Version 2

Input an Access Key, Access Secret, Session Token, and select a Signature Method to establish a connection.

Azure OAuth

Certificate

A Tenant ID, Client ID, and Scope can be used along with a saved Certificate File and Certificate Password to establish a connection.

NOTE: The certificate file only supports the PFX format. For newly generated certificates, a PEM file is also generated. This PEM file needs to be configured in the portal.

Client Credentials

A Tenant ID, Client ID, and Scope can be used along with a Client Secret to establish a connection.

Basic

Users can choose to use their instance url along with their Username and Password to establish a connection.

Bearer Token

Users can choose to use a Bearer Token to establish a connection. The Bearer Token allows requests to authenticate using a static access key.

Credentials (Basic, Digest, NTLM)

Users can choose to use their instance url along with their Domain, Username and Password to establish a connection.

Custom Token

Users can choose to use a custom token found using a CURL command. The command will send a request and return the server response. The TokenStrategy and TokenExpression will follow the path to the requested value. Using the Test Custom Token button with open up a window in which you can parse through the CURL File and test the token request. The token will be available for use by specifying &Connection[AccessToken] in supported connection properties.

Google Service Account

A JSON Key File Path along with a Scope can be used to establish a connection.

JWT

A Jwt web token can be used to establish a connection. The token can be imported using the Import Claims From Existing JWT or manually entered using the provided table.

Kerberos

Users can choose to use their instance url along with their Domain, Username and Password to establish a connection.

None

Used when your request does not require authorization.

OAuth 1

Users can choose to establish a connection through the OAuth 1.0 method by selecting the signature method and inputting valid credentials. For HMAC signature methods, valid credentials include Consumer Key, Consumer Secret, Access Token and Token Secret. For RSA signature methods, valid credentials include Consumer Key, Access Token and Private Key.

OAuth 2

A saved token file and token password can be used to establish a connection. If you wish to generate a new token file, click Generate Token File to go through the token generation process, save the token file locally, and use the set token password to connect. A dropdown is provided to customize the location of the access token in the request.

OAuth Client Credentials

Users can choose to establish an OAuth connection using their ClientId, ClientSecret, Scope, and TokenUrl. A dropdown is provided to customize the location of the access token in the request.

Static Token

Users can choose to use their Token Name and Token Value to establish a connection. A dropdown is provided to customize the location of the access token in the request.

Windows Integrated Authentication

No credentials required. Automatically authenticates as the current signed in user.

WSSE

Users can choose to establish a connection by providing their Username and Password.

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 GraphQL 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 app";
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 customer (input-email, input-firstName, input-lastName) VALUES ('[email protected]', 'John', 'Smith')";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserror
gid://shopify/Customer/7559639957617,null,null,{"var1":{"email":"[email protected]","firstName":"John","lastName":"Smith"}},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 customer SET input-firstName = 'nameUpdate' WHERE input-id = 'gid://shopify/Customer/7559639957617'";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserror
gid://shopify/Customer/7559639957617,null,null,{"var1":{"id":"gid://shopify/Customer/7559639957617","firstName":"nameUpdate"}},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 customer WHERE input-id = 'gid://shopify/Customer/7559639957617'";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserror
gid://shopify/Customer/7559639957617,null,null,{"var1":{"id":"gid://shopify/Customer/7559639957617"}},false

UPSERT

Using the UPSERT operation, you can either insert or update an existing record in one call.

Not all tables support the upsert operation. Query the system.tables table to identify which tables support UPSERT operations.

If the key isn't matched, then a new object record is created.

If the specified key is matched, the action taken will depend on if there were multiple matches or not.

• If the key is matched once, the existing object record is updated.
• If the key is matched multiple times, an error is generated and the object record is not inserted or updated.

The Upsert SQL statement must end with 'ON DUPLICATE KEY UPDATE UPSERTFIELDS = key', where 'key' refers to the field specified by the user as the upsert key.

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

String sql = "UPSERT INTO customers (store_id, customer_id, email_address, first_name, last_name, id, opt_in_status) VALUES ('357822853', '123', '[email protected]', 'testF', 'testL', '123', true) ON DUPLICATE KEY UPDATE UPSERTFIELDS = (email_address)";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserror
null,null,null,{"var2":false,"var4":1,"var3":"gid://shopify/Location/19550830705","var1":"UTC"},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-id) 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 commentSpam (id, OUT comment-id) VALUES ('gid://shopify/Comment/20430717041')";
try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

comment-id,errorcode,errormessage,processdata,haserror
gid://shopify/Comment/20430717041,null,null,{"var1":"gid://shopify/Comment/20430717041"},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 companies WHERE names IN (?, ?)";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "name1");
    ps.setString(2, "name2");
    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 customer (input-email, input-firstName) VALUES (?, ?)";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "[email protected]");
    ps.setString(2, "name");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.error(e);
}

id,errorcode,errormessage,processdata,haserror
gid://shopify/Customer/7559659028593,null,null,{"var1":{"email":"[email protected]","firstName":"firstNameInsert"}},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 customer SET input-firstName = ? WHERE input-id = ?";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "nameUpdate");
    ps.setString(2, "gid://shopify/Customer/7559659028593");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.error(e);
}

id,errorcode,errormessage,processdata,haserror
gid://shopify/Customer/7559659028593,null,null,{"var1":{"id":"gid://shopify/Customer/7559659028593","firstName":"nameUpdate"}},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 customer WHERE input-id = ?";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "gid://shopify/Customer/7559659028593");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.error(e);
}

id,errorcode,errormessage,processdata,haserror
gid://shopify/Customer/7559659028593,null,null,{"var1":{"id":"gid://shopify/Customer/7559659028593"}},false

UPSERT

Using the UPSERT operation, you can either insert or update an existing record in one call.

Not all tables support the upsert operation. Query the system.tables table to identify which tables support UPSERT operations.

If the key isn't matched, then a new object record is created.

If the specified key is matched, the action taken will depend on if there were multiple matches or not.

• If the key is matched once, the existing object record is updated.
• If the key is matched multiple times, an error is generated and the object record is not inserted or updated.

The Upsert SQL statement must end with 'ON DUPLICATE KEY UPDATE UPSERTFIELDS = key', where 'key' refers to the field specified by the user as the upsert key.

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

String sql = "UPSERT INTO deliveryPromiseProviderUpsert (active, fulfillmentDelay, locationId, timeZone) VALUES "
	+ "(?, ?, ?, ?) ON DUPLICATE KEY UPDATE UPSERTFIELDS = (locationId)";
try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setBoolean(1, false);
    ps.setInt(2, 1);
    ps.setString(3, "gid://shopify/Location/19550830705");
    ps.setString(4, "UTC");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.error(e);
}

id,errorcode,errormessage,processdata,haserror
null,null,null,{"var2":false,"var4":1,"var3":"gid://shopify/Location/19550830705","var1":"UTC"},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-id) 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 commentSpam (id, OUT comment-id) VALUES (?)";
try {
	Connection connection = buildRestConnectionFromDriverManager();
	PreparedStatement ps = connection.prepareStatement(customSql);
	ps.setString(1, "gid://shopify/Comment/20430717041");
	ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
	e.printStackTrace();
}

comment-id,errorcode,errormessage,processdata,haserror
gid://shopify/Comment/20430717041,null,null,{"var1":"gid://shopify/Comment/20430717041"},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.

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,adaptive_auth_event,Table,
null,null,agent_assist_recommendation,Table,
null,null,agent_file,Table,
......

The getTables method returns the following metadata columns:

Columns

Use the getColumns method of the DatabaseMetaData interface to retrieve detailed information about the columns in the database. To narrow your search to a specific table, specify the table name as a parameter.

try {
    Connection connection = buildRestConnectionFromDriverManager();
    ResultSet rs = connection.getMetaData().getColumns(null, null, "agent_file", 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,agent_file,sys_updated_on,91,java.util.Date,40,null,0,0,null,null,null,91,null,null,null,null,null,null,DT_DBDATE
null,null,agent_file,start_date,91,java.util.Date,40,null,0,0,null,null,null,91,null,null,null,null,null,null,DT_DBDATE
null,null,agent_file,sys_updated_by,12,java.lang.String,40,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 GraphQL.

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

TABLE_NAME,PRIMARY_COLUMN_NAME
agent_file,sys_id

The getPrimaryKeys method returns the following columns:

Connection Settings