JDBC Driver API support¶

Methods¶

Snowflake-specific behavior¶

None.

Additional methods¶

getQueryID()¶

Purpose:

This method returns the Snowflake query ID of the most recently executed query of this CallableStatement. If no query has been executed yet with the callable statement, the method returns null.

Arguments:

None.

Returns:

This method returns the ID as a String that contains a UUID. Information about UUIDs is included in the description of the SQL function UUID_STRING.

Throws:

The method can throw SQLException.

Methods¶

Snowflake-specific behavior¶

• close()

  Closes the object. After an object has been closed, calling almost any method of the closed object will raise a SQLException. Calling close on an already closed object is harmless and will not raise an exception.

• getMetaData()

  Lets you get metadata about the JDBC driver and Snowflake. For example, you can find out whether transactions are supported.

  For more information about the methods that you can call on the returned value, see Object: DatabaseMetaData.

• prepareStatement(String sql)

  This method returns a preparedStatement object that can be used to execute the SQL statement. The preparedStatement object’s execute() method can be called to execute the statement. The statement can be executed as-is, or after binding values to the statement.

  Note

  In some systems, after a statement has been prepared, that statement can be executed repeatedly without re-compiling the statement. Preparing once and executing repeatedly can save a small amount of time and resources.

  In Snowflake, prepareStatement() does not actually compile the code. Instead, PreparedStatement.execute(), PreparedStatement.executeQuery(), and PreparedStatement.executeUpdate() compile and execute the statement. Therefore preparing the statement before execution does not save resources compared to simply using Statement.execute().

• prepareCall(String sql)

• prepareCall(String sql, boolean)

• prepareCall(String sql, int, int)

• prepareCall(String sql, int, int, int)

  As in most JDBC implementations, the prepareCall methods can be used to bind parameters to a stored procedure. For example, the following is supported:

  CallableStatement stmt = testConnection.prepareCall("call read_result_set(?,?) ");
  

  Copy

  However, in the Snowflake JDBC Driver, the prepareCall methods do not support the ? = syntax to support binding the return value of a stored procedure. For example, the following is not supported:

  CallableStatement stmt = testConnection.prepareCall("? = call read_result_set() ");  -- INVALID
  

  Copy

Additional methods¶

These methods are in addition to the methods supported by the JDBC Connection interface.

public ResultSet createResultSet(String queryID)

Purpose:

Given the queryID of an asynchronously-launched SQL statement, retrieve the query results and return them in a ResultSet object.

This method can typically be called up to 24 hours after the SQL statement finished.

Arguments:

queryID: The query ID of the query for which you want the results.

Returns:

The ResultSet. If the query has not yet finished running, the server returns an “empty” ResultSet. The user can call resultSet.unwrap(SnowflakeResultSet.class).getStatus() to find out when the data is available.

Throws:

This method can throw SQLException.

Notes:

This method is a Snowflake extension to the JDBC standard. To use this method, you must unwrap the Connection object.

Examples:

ResultSet resultSet;
resultSet = connection.unwrap(SnowflakeConnection.class).createResultSet(queryID);

Copy

See Examples of asynchronous queries for a more extensive example that includes a call to this method.

public InputStream downloadStream(String stageName, String sourceFileName, boolean decompress)

Purpose:

This method downloads a file from the given internal stage and returns an input stream.

Arguments:

stageName: Stage name.

sourceFileName: File path in stage.

decompress: True if file compressed.

Returns:

This method returns an InputStream.

Throws:

This method throws SQLException if a SQL error occurs.

Examples:

For a partial example, see Download data files directly from an internal stage to a stream.

public String getSessionID()

Purpose:

This method returns the session ID of the current session.

Arguments:

None

Returns:

Returns the session ID as a String.

Throws:

This method throws SQLException if any SQL error occurs, for example if the connection is closed.

Usage Notes:

Since the session ID does not change while the connection is open, the session ID is cached locally (rather than retrieved from the server each time) to improve performance.

public prepareStatement(String sql, Boolean skipParsing)

This method is deprecated. The skipParsing parameter no longer affects the behavior of the method; this method behaves the same as the prepareStatement(String sql) method, regardless of the setting of the skipParsing parameter.

New code should use the method prepareStatement(String sql).

When convenient, existing code that uses the two-argument version of this method should be updated to use the one-argument method prepareStatement(String sql).

public void uploadStream(String stageName, String destPrefix, InputStream inputStream, String destFileName, boolean compressData)

Purpose:

This method compresses data from a stream and uploads it at an internal stage location. The data will be uploaded as one file. No splitting is done in this method.

Arguments:

stageName: Stage name (e.g. ~ or table name or stage name).

destPrefix: Path / prefix under which the data should be uploaded on the stage.

inputStream: Input stream from which the data will be uploaded.

destFileName: Destination file name to use.

compressData: Compress data or not before uploading stream.

Returns:

Nothing.

Throws:

This method throws a java.sql.SQLException if it failed to compress and put data from a stream at the stage.

Notes:

The caller is responsible for releasing the inputStream after the method is called.

Examples:

For a partial example, see Upload data files directly from a stream to an internal stage.

Methods¶

Snowflake-specific behavior¶

public ResultSet getColumnPrivileges(String, String, String, String)

This method always returns an empty set because Snowflake does not support column-level privileges.

public ResultSet getStreams(String, String, String)

Purpose:

This method returns information about streams contained within specified databases and schemas.

Arguments:

• originalCatalog: Name of the database.

• orignalSchemaPattern: Pattern to identify the schema (supports wildcards).

• streamName: Name of the stream (supports wildcards).

Returns:

This method returns a ResultSet containing rows for each stream, with each row including the following columns:

• name: Name of the stream.

• database_name: Name of the database for the schema containing the stream.

  A database object (e.g. a stream) is contained in a schema, which in turn is contained in a database.

• schema_name: Name of the schema containing the stream.

• owner: Role that owns the stream.

• comment: Comments associated with the stream.

• table_name: Name of the table whose DML updates are tracked by the stream.

• source_type: Source object for the stream. Possible values include:

  • table

  • view

  • directory table

  • external table

• base_tables: Underlying tables for the view. This column applies only to streams on views.

• type: Type of the stream. Currently, the function always returns DELTA.

• stale: Whether the stream was last read before the stale_after time passed. If TRUE, the stream might be stale.

  When a stream is stale, it cannot be read. You can recreate the stream to resume reading from it. To prevent a stream from become stale, you should consume the stream before the stale_after time has passed.

• mode: Type of stream. Possible values include:

  • APPEND_ONLY: Indicates the stream is an append-only stream.

  • INSERT_ONLY: Indicates the stream only returns information for inserted rows. This value applies only to streams on external tables.

  • DEFAULT: Indicates the stream is on tables.

Throws:

This method throws an SQLException if a SQL error occurs.

Support for null parameters¶

Some DatabaseMetaData methods accept null values for database object names (e.g. table/catalog names). By default, a null value means that the method does not filter on that argument. For example, if you pass getColumns() a null value for the schemaPattern argument, then getColumns() returns values for all schemas.

For some of those methods, the default behavior for null arguments can be overridden with the following parameters:

• CLIENT_METADATA_REQUEST_USE_CONNECTION_CTX.

• CLIENT_METADATA_USE_SESSION_DATABASE.

Support for wildcards in database object names¶

Some DatabaseMetaData methods support pattern-matching wildcards in database object names, such as table/catalog names. The supported wildcard characters are:

• %: Matches any string of zero or more characters.

• _: Matches any one character.

The following example shows what to pass to the getColumns() method to get the names of all tables and all columns in the specified database (TEMPORARYDB1) and schema (TEMPORARYSCHEMA1):

getColumns( connection,
    "TEMPORARYDB1",      // Database name.
    "TEMPORARYSCHEMA1",  // Schema name.
    "%",                 // All table names.
    "%"                  // All column names.
    );

It is common for database object names, such as table names, to contain underscores, for example SHIPPING_ADDRESSES. Searching for SHIPPING_ADDRESSES without escaping the underscore will of course find not only the table named SHIPPING_ADDRESSES, but also tables such as SHIPPING2ADDRESSES. If you want to search for SHIPPING_ADDRESSES, but not SHIPPING2ADDRESSES, then you need to escape the wildcard character to indicate that you want it treated as a literal. To escape the character, precede it with a backslash.

The backslash character itself must also be escaped if you want to use it as a literal character. For example, to search for a table named T_&, in which the underscore, the ampersand, and the backslash are literal parts of the name, not wildcard characters or escape characters, the method call should look similar to the following:

getColumns(
    connection, "TEMPORARYDB1", "TEMPORARYSCHEMA1", "T\\_\\\\", "%" // All column names.
    );

Each backslash above must be escaped an extra time because the Java compiler expects backslashes to be escaped:

Java sees...............: T\\_\\%\\\\
SQL sees................: T\_\%\\
The actual table name is: T_%\

Methods¶

Snowflake-specific behavior¶

None.

Examples¶

The following code snippet shows part of a program to get property information:

  // Demonstrate the Driver.getPropertyInfo() method.
  public static void do_the_real_work(String connectionString) throws Exception {
    Properties properties = new Properties();
    Driver driver = DriverManager.getDriver(connectionString);
    DriverPropertyInfo[] dpinfo = driver.getPropertyInfo("", properties);
    System.out.println(dpinfo[0].description);
  }

Note that in the general case, the call to this method should be inside a loop. If you retrieve information about a property and then set that property, the new setting might make additional properties relevant, so you might need to retrieve those and set them.

Methods¶

Snowflake-specific behavior¶

None.

Methods¶

Snowflake-specific behavior¶

• addBatch()

  Supported for INSERT statements only.

  The addBatch method (combined with executeBatch) allows multiple rows of data to be inserted as part of a single INSERT statement.

  The difference between using a batch and not using a batch is similar to the difference between using a multi-row insert and a single-row insert:

  INSERT INTO t1 (c1, c2) VALUES (1, 'One');   -- single row inserted.
  
  INSERT INTO t1 (c1, c2) VALUES (1, 'One'),   -- multiple rows inserted.
                                 (2, 'Two'),
                                 (3, 'Three');
  

  Copy

  Inserting batches of rows is usually more efficient than inserting the same number of rows in individual INSERT statements. The advantage is even greater when using AUTOCOMMIT (i.e. when each INSERT is an individual transaction).

  For an example of using addBatch, see Batch inserts.

  Note

  There is an upper limit to the size of data that you can bind, or that you can combine in a batch. For details, see Limits on Query Text Size.

• execute()

  This method compiles and executes the SQL statement that was provided when the PreparedStatement object was created. The statement can be any type of SQL statement. The execute() method does not return a ResultSet.

  This method does not return anything. If you are executing a query and need to get a ResultSet back when the statement executes, then use the executeQuery() method.

• executeQuery()

  This method compiles and executes the SQL statement that was provided when the PreparedStatement object was created, and returns a ResultSet.

• executeUpdate()

  This method compiles and executes the SQL statement that was provided when the PreparedStatement object was created. The statement must be a DML statement (INSERT, UPDATE, DELETE, etc.) or a SQL statement that does not return anything (e.g. a DDL statement).

  The executeUpdate() method returns an integer, which is the number of rows updated if the statement was a DML statement. If the statement did not update any rows, the function returns 0.

  If you need to execute a SQL statement that returns a ResultSet, then use a different method, such as executeQuery().

• setObject()

  When you bind a timestamp variable to a timestamp column, you can use this method to specify the timestamp variation (TIMESTAMP_LTZ , TIMESTAMP_NTZ , TIMESTAMP_TZ) that should be used to interpret the timestamp value. For details, see Binding variables to timestamp columns.

Additional methods¶

The methods below are in addition to the methods supported by the PreparedStatement interface.

executeAsyncQuery()¶

Purpose:

This method performs an asynchronous query, which involves submitting an SQL statement for execution, then returning control to the caller without waiting for the query to finish.

Any SQL statement that is valid for executeQuery() is also valid for executeAsyncQuery().

Note

File transfer statements, such as PUT and GET, are valid for executeAsyncQuery(), but behave synchronously.

Arguments:

None.

Returns:

An “empty” ResultSet. The user should poll the result set by calling resultSet.unwrap(SnowflakeResultSet.class).getStatus() until the query results become available.

Throws:

This method can throw SQLException.

Notes:

This method is a Snowflake extension to the JDBC standard. To use this method, you must unwrap the PreparedStatement object.

Examples:

...
PreparedStatement prepStatement = connection.prepareStatement("insert into testTable values (?)");
prepStatement.setInt(1, 33);
ResultSet rs = prepStatement.executeAsyncQuery();
...

Copy

See Examples of asynchronous queries for a more extensive example using the very similar SnowflakeStatement.executeAsyncQuery() method.

getQueryID()

Purpose:

This method returns the Snowflake query ID of the most recently executed query of this SnowflakePreparedStatement. If no query has been executed yet with this prepared statement, the method returns null.

Arguments:

None.

Returns:

The method returns the ID as a String that contains a UUID.

Throws:

The method can throw SQLException.

Notes:

This method is a Snowflake extension to the JDBC standard. To use this method, you must unwrap the SnowflakePreparedStatement.

For asynchronous queries, the query ID does not become available until the execution of the statement completes. If you call SnowflakePreparedStatement.getQueryID() after calling executeAsyncQuery() but before the statement finishes executing, the return value could be NULL. Instead, call resultSet.unwrap(SnowflakeResultSet.class).getQueryID() on the ResultSet object returned by executeAsyncQuery().

Examples:

This partial example shows how to call the method:

    // Retrieve the query ID from the PreparedStatement.
    String queryID;
    queryID = preparedStatement.unwrap(SnowflakePreparedStatement.class).getQueryID();

Copy

Enum constants¶

Each enum constant represents a different possible status for the asynchronous query.

Methods¶

The enum type defines the following methods, which you can use to get details about an error when the query status is FAILED_WITH_ERROR.

getErrorCode()¶

Purpose:

If an error occurred during the execution of the query, this method returns the error code from the server.

Arguments:

None.

Returns:

The method returns the error code as an int. If no error occurred, the method returns the value 0.

Examples:

QueryStatus queryStatus = resultSet.unwrap(SnowflakeResultSet.class).getStatus();
if (queryStatus == queryStatus.FAILED_WITH_ERROR) {
  // Print the error code to stdout
  System.out.format("Error code: %d%n", queryStatus.getErrorCode());
}

Copy

See Examples of asynchronous queries for a more extensive example that includes a call to this method.

getErrorMessage()¶

Purpose:

If an error occurred during the execution of the query, this method returns the error message from the server.

Arguments:

None.

Returns:

The method returns the error message as a String. If no error occurred, the method returns the value No error reported.

Examples:

QueryStatus queryStatus = resultSet.unwrap(SnowflakeResultSet.class).getStatus();
if (queryStatus == queryStatus.FAILED_WITH_ERROR) {
  // Print the error message to stdout
  System.out.format("Error message: %s%n", queryStatus.getErrorMessage());
}

Copy

See Examples of asynchronous queries for a more extensive example that includes a call to this method.

Methods¶

Snowflake-specific behavior¶

• close()

  Closes the object. After an object has been closed, calling almost any method of the closed object will raise a SQLException. Calling close on an already closed object is harmless and will not raise an exception.

• getDate(), getTime(), getTimestamp()

  In version 3.12.17 and later versions of the JDBC Driver, these methods use the session time zone (specified by the TIMEZONE parameter). Older versions use the time zone of the JVM.

  To change these methods to use the time zone of the JVM, set the JDBC_USE_SESSION_TIMEZONE parameter to FALSE.

• getMetaData()

  If the ResultSet object is for an asynchronous query, then this method will block until the query has finished executing. You can use resultSet.unwrap(SnowflakeResultSet.class).getStatus() to get the query status before calling this method.

• next()

  This makes the next row in the result set the “current” row. Calls to the get*() methods, such as getInt(), get values from the current row.

  If the ResultSet has been closed by a call to the close method, then subsequent calls to next return false, rather than raise an exception.

  If the ResultSet object is for an asynchronous query, then this method will block until the results are available. You can use resultSet.unwrap(SnowflakeResultSet.class).getStatus() to get the query status before calling this method.

Additional methods¶

getQueryID()

Purpose:

This method returns the Snowflake query ID of the statement that generated this result set.

Arguments:

None.

Returns:

The method returns the ID as a String that contains a UUID.

Notes:

This method is a Snowflake extension to the JDBC standard. To use this method, you must unwrap the ResultSet.

Examples:

    String queryID2;
    queryID2 = resultSet.unwrap(SnowflakeResultSet.class).getQueryID();

Copy

getStatus()¶

Purpose:

For a ResultSet returned by an asynchronous query, such as SnowflakeStatement.executeAsyncQuery(), this method returns the status of the query. The status indicates whether the query finished successfully, finished unsuccessfully, or has not yet finished.

Arguments:

None.

Returns:

A QueryStatus enum constant.

Throws:

This method can throw SQLException.

Notes:

This method is a Snowflake extension to the JDBC standard. To use this method, you must unwrap the ResultSet object.

Examples:

QueryStatus queryStatus = resultSet.unwrap(SnowflakeResultSet.class).getStatus();

Copy

See Examples of asynchronous queries for a more extensive example that includes a call to this method.

Methods¶

Snowflake-specific behavior¶

• The ResultSetMetaData class does not have a close() method. An open ResultSetMetaData object is implicitly closed when the user closes the ResultSet from which the ResultSetMetaData object was created.

• getCatalogName(), getSchemaName(), getTableName()

  If the ResultSet object is for an asynchronous query, these methods return empty strings.

• For GEOGRAPHY columns, getColumnTypeName returns GEOGRAPHY.

  Note that the getColumnType and getColumnClassName methods do not indicate that the column type is GEOGRAPHY.

Additional methods¶

getColumnIndex(String columnName):

Purpose:

Returns the index of the column that corresponds to the columnName. For example, if a column named “BirthDate” is the third column in the table, then getColumnIndex(“BirthDate”) returns 2. (Indexes are 0-based, not 1-based.)

Arguments:

The name of the column for which you want to find the index.

Returns:

Returns an integer that contains the index of the column that corresponds to the columnName. If the columnName does not match any column in the result set, this returns -1.

Throws:

The method can throw SQLException.

getColumnNames():

Purpose:

This function returns the list of all column names in the resultset.

This is different from the function getColumnName(int column) in ResultSetMetaData, which returns a single column name based on an index.

Arguments:

None.

Returns:

The data type of the returned value is “List<String>”. The list contains the names of the columns. The names are in the same order as the column indexes.

Throws:

The method can throw SQLException.

getInternalColumnType(int column):

Purpose:

Returns the data type of the specified column.

Arguments:

column: This indicates the index (1-based) of the column for which you want the data type.

Returns:

Returns the data type of the specified column. The data type is an integer.

Throws:

The method can throw SQLException.

getQueryID()

Purpose:

Returns the Snowflake query ID of the query to which this metadata applies.

Arguments:

None.

Returns:

This method returns the query ID of the query for which this metadata was generated. The query ID is a String that contains a UUID. Information about UUIDs is included in the description of the SQL function UUID_STRING.

Throws:

The method can throw SQLException.

Methods¶

SnowflakeTimestampWithTimezone(
    long seconds,
    int nanoseconds,
    TimeZone tz)

SnowflakeTimestampWithTimezone(
    Timestamp ts,
    TimeZone tz)

SnowflakeTimestampWithTimezone(
    Timestamp ts)

Snowflake-specific behavior¶

• getTimezone()

  Returns the time zone from the time stamp.

  import java.sql.Timestamp;
  import java.time.ZonedDateTime;
  import java.util.TimeZone;
  
  public void testGetTimezone() {
      String timezone = "Australia/Sydney";
  
      // Create a timestamp from a point in time
      Long datetime = System.currentTimeMillis();
      Timestamp currentTimestamp = new Timestamp(datetime);
      SnowflakeTimestampWithTimezone ts =
          new SnowflakeTimestampWithTimezone(currentTimestamp, TimeZone.getTimeZone(timezone));
  
      // Verify timezone was set
      assertEquals(ts.getTimezone().getID(), timezone);
  }
  

  Copy

• toZonedDateTime()

  Converts a SnowflakeTimestampWithTimezone time stamp to a zoned date time (Java ZonedDateTime object).

  import java.sql.Timestamp;
  import java.time.ZonedDateTime;
  import java.util.TimeZone;
  
  public void testToZonedDateTime() {
      String timezone = "Australia/Sydney";
      String zonedDateTime = "2022-03-17T10:10:08+11:00[Australia/Sydney]";
  
      // Create a timestamp from a point in time
      Long datetime = 1647472208000L;
      Timestamp timestamp = new Timestamp(datetime);
      SnowflakeTimestampWithTimezone ts =
          new SnowflakeTimestampWithTimezone(timestamp, TimeZone.getTimeZone(timezone));
      ZonedDateTime zd = ts.toZonedDateTime();
  
      // Verify timestamp was converted to zoned datetime
      assertEquals(zd.toString(), zonedDateTime);
  }
  

  Copy

Methods¶

Snowflake-specific behavior¶

• close()

  This method closes the object. After an object has been closed, calling almost any method of the closed object will raise a SQLException. Calling close on an already closed object is harmless and will not raise an exception.

• getBatchQueryID()

  This method returns a list of the Snowflake query IDs of the most recently executed query batch of this Statement. If no query has been executed yet with the statement, the method returns null.

  This method is a Snowflake extension to the JDBC standard. To use this method, you must unwrap the statement. For example:

      connection.setAutoCommit(false);
      statement.addBatch("SELECT 1;");
      statement.addBatch("SELECT 2;");
      statement.executeBatch();
      connection.commit();
      connection.setAutoCommit(true);
      List<String> batchQueryIDs1;
      // Since getQueryID is not standard JDBC API, we must call unwrap() to
      // use these Snowflake methods.
      batchQueryIDs1 = statement.unwrap(SnowflakeStatement.class).getBatchQueryIDs();
      int num_query_ids = batchQueryIDs1.size();
      if (num_query_ids != 2) {
        System.out.println("ERROR: wrong number of query IDs in batch 1.");
      }
      // Check that each query ID is plausible.
      for (int i = 0; i < num_query_ids; i++) {
        String qid = batchQueryIDs1.get(i);
        if (!is_plausible_query_id(qid)) {
          msg = "SEVERE WARNING: suspicious query ID in batch";
          System.out.println("msg");
          System.out.println(qid);
        }
      }
  

  Copy

• getUpdateCount()

  This method returns the number of rows updated by the most recently executed SQL statement.

  • If the statement was a DML statement (INSERT, UPDATE, DELETE, etc.), then getUpdateCount() returns the number of rows that were added, deleted, or changed. Note that this value can be 0 if no rows were changed.

  • If the statement was a SELECT statement, then getUpdateCount() returns -1.

  • If the statement was a DDL statement, then getUpdateCount() returns -1.

Additional methods¶

executeAsyncQuery(String)

Purpose:

This method performs an asynchronous query, which involves submitting an SQL statement for execution, then returning control to the caller without waiting for the query to finish.

Arguments:

A string containing the SQL command to execute. Any SQL statement that is valid for executeQuery() is also valid for executeAsyncQuery().

Note

File transfer statements, such as PUT and GET, are valid for executeAsyncQuery(), but behave synchronously.

Returns:

An “empty” ResultSet. The user should poll the result set by calling resultSet.unwrap(SnowflakeResultSet.class).getStatus() until the query results become available.

Throws:

The method can throw SQLException.

Notes:

This method is a Snowflake extension to the JDBC standard. To use this method, you must unwrap the Statement object.

Examples:

See Examples of asynchronous queries for an example that includes a call to this method.

getQueryID()

Purpose:

This method returns the Snowflake query ID of the most recently executed query of this Statement.

Arguments:

None.

Returns:

The query ID of the most recently executed query of this statement. The query ID is a String that contains a UUID. If no query has been executed yet with the statement, the method returns null.

Throws:

The method can throw SQLException.

Notes:

This method is a Snowflake extension to the JDBC standard. To use this method, you must unwrap the Statement.

For asynchronous queries, the query ID does not become available until the execution of the statement completes. If you call SnowflakeStatement.getQueryID() after calling executeAsyncQuery() but before the statement finishes executing, the return value could be NULL. Instead, call resultSet.unwrap(SnowflakeResultSet.class).getQueryID() on the ResultSet object returned by executeAsyncQuery().

Examples:

    String queryID1;
    queryID1 = statement.unwrap(SnowflakeStatement.class).getQueryID();

Copy

setParameter(String parameter_name, <type> <value>)¶

Purpose:

The SnowflakeStatement class provides the setParameter method as a Snowflake extension. This allows the caller to set Snowflake-specific JDBC parameters.

The method is overloaded. Different JDBC parameters require different data types. A method exists for each valid data type that can be passed as the second argument to the function.

Arguments:

parameter_name:

This string must contain the name of a pre-defined Snowflake JDBC parameter. The pre-defined JDBC parameters (and their valid values or ranges) are listed below:

JDBC Parameter	Notes
MULTI_STATEMENT_COUNT	Integer specifying the number of statements (0 = unlimited number of statements; 1 or higher indicates the exact number of statements that should be executed).

value:

This is the value to assign to the specified JDBC parameter. Make sure that the data type is compatible with the JDBC parameter you specified.

Returns:

Nothing.

Throws:

This function can throw SQLException.

Notes:

This method is a Snowflake extension to the JDBC standard. To use this method, you must unwrap the Statement.

Examples:

Statement statement1;
...
// Tell Statement to expect to execute 2 statements:
statement1.unwrap(SnowflakeStatement.class).setParameter(
        "MULTI_STATEMENT_COUNT", 2);

Copy