Uses of Class com.mysql.jdbc.CallableStatement (MySQL Connector/J v5.1.6)

Overview

Package

Class

Use

Tree

Deprecated

Index

Help

MySQL Connector/J size='-1'>5.1.6

PREV NEXT

FRAMES NO FRAMES

Uses of Class
com.mysql.jdbc.CallableStatement

Packages that use CallableStatement
com.mysql.jdbc

Uses of CallableStatement in com.mysql.jdbc

Subclasses of CallableStatement in com.mysql.jdbc
`class`	`JDBC4CallableStatement`

Methods in com.mysql.jdbc that return CallableStatement
`protected static CallableStatement`	`CallableStatement.getInstance(ConnectionImpl conn, CallableStatement.CallableStatementParamInfo paramInfo)` Creates a callable statement instance -- We need to provide factory-style methods so we can support both JDBC3 (and older) and JDBC4 runtimes, otherwise the class verifier complains when it tries to load JDBC4-only interface classes that are present in JDBC4 method signatures.
`protected static CallableStatement`	`CallableStatement.getInstance(ConnectionImpl conn, java.lang.String sql, java.lang.String catalog, boolean isFunctionCall)` Creates a callable statement instance -- We need to provide factory-style methods so we can support both JDBC3 (and older) and JDBC4 runtimes, otherwise the class verifier complains when it tries to load JDBC4-only interface classes that are present in JDBC4 method signatures.

Methods in com.mysql.jdbc that return CallableStatement

protected static CallableStatement CallableStatement.getInstance(ConnectionImpl conn, CallableStatement.CallableStatementParamInfo paramInfo)
Creates a callable statement instance -- We need to provide factory-style methods so we can support both JDBC3 (and older) and JDBC4 runtimes, otherwise the class verifier complains when it tries to load JDBC4-only interface classes that are present in JDBC4 method signatures.

protected static CallableStatement CallableStatement.getInstance(ConnectionImpl conn, java.lang.String sql, java.lang.String catalog, boolean isFunctionCall)
Creates a callable statement instance -- We need to provide factory-style methods so we can support both JDBC3 (and older) and JDBC4 runtimes, otherwise the class verifier complains when it tries to load JDBC4-only interface classes that are present in JDBC4 method signatures.