Anthropic

Building the JDBC URL

After installing the license, open the connection management page by running java -jar kingswaysoft.jdbc.jar. Enter the required details to generate the JDBC connection URL. Click Test Connection to test the generated URL, or Copy to Clipboard to copy the connection string for use in your application.

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 of the Anthropic Connection Manager allows you to specify the general settings of the connection:

Authentication Methods for Anthropic

{
  "grant_type": "urn:ietf:params:oauth:grant-type:jwt-bearer",
  "assertion": "123123123123123123123123",
  "federation_rule_id": "123",
  "organization_id": "321",
  "service_account_id": "123",
  "workspace_id": ""
}

Advanced Settings Page

The Advanced Settings page allows you to specify advanced settings for the connection.

Using the JDBC Driver

This section provides examples that use JDBC classes such as Connection, Statement, and ResultSet to manage interactions with Anthropic data. It covers regular statements and prepared statements for complex or frequently executed queries.

Executing Statements

After you have connected from your code, you can execute SQL statements using the Statement class. For connection details, see Connecting with DriverManager or Connecting with DataSource. For parameterized statements, see Executing Prepared 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, call the getResultSet method of the Statement.

String sql = "SELECT * FROM organizations/invites";

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 organizations/invites (email, role) VALUES ('[email protected]', 'billing')";

try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
invite_015gWxCN9Hfg2QhZwTK7Mdeu,null,null,{"email":"[email protected]","role":"billing"},false

To create a Skill, see Skills and Skill Versions.

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 organizations/workspaces SET name = 'Updated Workspace Name' WHERE workspace_id = 'wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ'";

try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ,null,null,{"name":"Updated Workspace Name"},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 organizations/invites WHERE invite_id = 'invite_015gWxCN9Hfg2QhZwTK7Mdeu'";

try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

id,errorcode,errormessage,processdata,haserrors
invite_015gWxCN9Hfg2QhZwTK7Mdeu,null,null,null,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 Statement class.

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

SELECT

Use the PreparedStatement 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 organizations/invites WHERE invite_id = ?";

try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "invite_015gWxCN9Hfg2QhZwTK7Mdeu");
    boolean ret = ps.execute();
    if (ret) {
        ResultSet rs = ps.getResultSet();
        LOGGER.info(rs.toString());
    }
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

INSERT

Use either the generic execute method or the executeUpdate method of the PreparedStatement 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 ID of inserted data, exceptions raised during execution, and the data affected by the insertion.

String sql = "INSERT INTO organizations/invites (email, role) VALUES (?, ?)";

try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "[email protected]");
    ps.setString(2, "billing");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.error(e);
}

id,errorcode,errormessage,processdata,haserrors
invite_015gWxCN9Hfg2QhZwTK7Mdeu,null,null,{"email":"[email protected]","role":"billing"},false

UPDATE

Use either the generic execute method or the executeUpdate method of the PreparedStatement 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 ID of updated data, exceptions raised during execution, and the data affected by the update.

String sql = "UPDATE organizations/workspaces SET name = ? WHERE workspace_id = ?";

try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "Updated Workspace Name");
    ps.setString(2, "wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.error(e);
}

id,errorcode,errormessage,processdata,haserrors
wrkspc_01JwQvzr7rXLA5AGx3HKfFUJ,null,null,{"name":"Updated Workspace Name"},false

DELETE

Use either the generic execute method or the executeUpdate method of the PreparedStatement 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 organizations/invites WHERE invite_id = ?";

try {
    PreparedStatement ps = connection.prepareStatement(sql);
    ps.setString(1, "invite_015gWxCN9Hfg2QhZwTK7Mdeu");
    ps.executeUpdate();
    LOGGER.info(ps.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.error(e);
}

id,errorcode,errormessage,processdata,haserrors
invite_015gWxCN9Hfg2QhZwTK7Mdeu,null,null,null,false

Skills and Skill Versions

Use the skills table to list, look up, create, or delete Skills. Use the skills/versions table to list, look up, create, or delete versions of a Skill. Skills cannot be updated in place; add a new version instead.

When you create a Skill or a Skill Version, put the Skill files in the files column. This column is required. Every Skill must include a SKILL.md file, and all files must be in the same folder.

When creating a Skill, you can optionally set display_name. When creating a version, you also need the existing skill_id.

This files column is not the same as the files table, which is used to upload files for messages.

The files column accepts:

• One Base64-encoded file. The driver uploads it as skill/SKILL.md.
• A JSON list of Base64-encoded files. Each item is uploaded as skill/SKILL.md.
• A JSON list of file objects. Use this when the Skill has more than one file.

Each file object can include:

• path (also filename or file_name) — the file path in the Skill folder, for example my-skill/SKILL.md.
• content (also file_content) — required. The file content as a Base64-encoded string.
• name and description — the Skill name and description. These are used for SKILL.md.
• content_type (also file_content_type) — optional file type. If omitted, text/markdown is used.

If you omit path but provide both name and description, the driver uses the Skill name plus /SKILL.md as the file path, for example my-skill/SKILL.md. If the path is blank or is only SKILL.md, the driver uses skill/SKILL.md.

If SKILL.md does not already include a name and description at the top of the file, the driver adds them for you from the name, description, or display_name values you provided.

You can also pass the file bytes directly with PreparedStatement.setBytes. The driver uploads those bytes as skill/SKILL.md.

String sql = "INSERT INTO skills (files, display_name) VALUES ("
        + "'[{\"path\":\"my-skill/SKILL.md\",\"name\":\"my-skill\",\"description\":\"A sample skill\",\"content\":\"dGVzdDE=\"},"
        + "{\"path\":\"my-skill/reference.md\",\"content\":\"dGVzdDI=\"}]',"
        + "'My Skill')";

try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

String sql = "INSERT INTO skills/versions (files, skill_id) VALUES ("
        + "'[{\"path\":\"my-skill/SKILL.md\",\"content\":\"dGVzdDE=\"},"
        + "{\"path\":\"my-skill/reference.md\",\"content\":\"dGVzdDI=\"}]',"
        + "'skill_01JAbcdefghijklmnopqrstuvw')";

try {
    statement.executeUpdate(sql);
    LOGGER.info(statement.getResultSet().toString());
} catch (SQLException e) {
    LOGGER.severe(e.toString());
}

Metadata Discovery

This section provides examples on how to retrieve table and column metadata using the getTables, getColumns, and getPrimaryKeys 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 that includes write-only tables, query the table system.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,TYPE_CAT,TYPE_SCHEM,TYPE_NAME,SELF_REFERENCING_COL_NAME,REF_GENERATION
null,null,organizations/analytics/apps/chat/projects,TABLE,null,null,null,null,null,null
null,null,organizations/analytics/artifacts,TABLE,null,null,null,null,null,null
null,null,organizations/analytics/connectors,TABLE,null,null,null,null,null,null
null,null,organizations/analytics/cost_report,TABLE,null,null,null,null,null,null
......

The getTables method returns the following metadata columns:

Columns

Use the getColumns method of the DatabaseMetaData interface to retrieve detailed information about database columns.

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

To get columns for write-only tables, query the table system.columns.

try {
    Connection connection = buildRestConnectionFromDriverManager();
    ResultSet rs = connection.getMetaData().getColumns(null, null, "organizations/users", 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,SCOPE_CATALOG,SCOPE_SCHEMA,SCOPE_TABLE,SOURCE_DATA_TYPE,IS_AUTOINCREMENT,IS_GENERATEDCOLUMN,DTS_TYPE
null,null,organizations/users,added_at,93,TIMESTAMP,null,null,0,0,null,null,null,93,null,null,null,null,null,null,null,null,null,null,DT_DBTIMESTAMP
null,null,organizations/users,email,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,organizations/users,id,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,null,null,null,null,null,null,DT_WSTR
null,null,organizations/users,name,12,VARCHAR,0,null,0,0,null,null,null,12,null,null,null,null,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 Anthropic.

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

TABLE_CAT,TABLE_SCHEM,TABLE_NAME,COLUMN_NAME,KEY_SEQ,PK_NAME
null,null,organizations/users,id,1,null

The getPrimaryKeys method returns the following columns:

Connection Settings