Home » Core Java » sql » Get JDBC Connection parameters

About Ilias Tsagklis

Ilias Tsagklis
Ilias is a software developer turned online entrepreneur. He is co-founder and Executive Editor at Java Code Geeks.

Get JDBC Connection parameters

With this example we are going to demonstrate how to get the JDBC Connection parameters. In short, to get the JDBC Connection parameters you should:

  • Load the MySQL JDBC driver, using the forName(String className) API method of the Class.
  • Get the Driver Instance. Invoke the getDriver(String url) of the DriverManager, using the database URL.
  • Get available properties, using the getPropertyInfo(String url, Properties info) of the Driver. It will return an array of DriverPropertyInfo objects describing possible properties.
  • For each one of the properties, get the name, value, description, choices and if property is required or not.

Let’s take a look at the code snippet that follows:

package com.javacodegeeks.snippets.core;

import java.sql.Driver;
import java.sql.DriverManager;
import java.sql.DriverPropertyInfo;
import java.sql.SQLException;
import java.util.Arrays;

public class ConnectionProperties {
 
  public static void main(String[] args) {

    try {


  // Load the MySQL JDBC driver

  String driverName = "com.mysql.jdbc.Driver";

  Class.forName(driverName);


  // Get the Driver instance

  String serverName = "localhost";

  String schema = "test";

  String url = "jdbc:mysql://" + serverName +  "/" + schema;

  Driver driver = DriverManager.getDriver(url);


  // Get available properties

  DriverPropertyInfo[] properties = driver.getPropertyInfo(url, null);

  for (int i=0; i < properties.length; i++) {





// Property information


String name = properties[i].name;


boolean required = properties[i].required;


String value = properties[i].value;


String description = properties[i].description;


String[] choices = properties[i].choices;



System.out.println("Property : " + name + "nRequired : " + required + "nValue : " + value + "nDescription : " + description + "nChoices : " + (choices!=null?Arrays.asList(choices):null) + "n");

  }
    } catch (ClassNotFoundException e) {

System.out.println("Could not find the database driver " + e.getMessage());
    } catch (SQLException e) {

System.out.println("Could not retrieve database metadata " + e.getMessage());
    }

  }
}

Example Output:

Property : HOST
Required : true
Value : localhost
Description : Hostname of MySQL Server
Choices : null

Property : PORT
Required : false
Value : 3306
Description : Port number of MySQL Server
Choices : null

Property : DBNAME
Required : false
Value : test
Description : Database name
Choices : null

Property : user
Required : true
Value : null
Description : Username to authenticate as
Choices : null

Property : password
Required : true
Value : null
Description : Password to use for authentication
Choices : null

Property : allowLoadLocalInfile
Required : false
Value : true
Description : Should the driver allow use of 'LOAD DATA LOCAL INFILE...' (defaults to 'true').
Choices : [true, false, yes, no]

Property : allowMultiQueries
Required : false
Value : false
Description : Allow the use of ';' to delimit multiple queries during one statement (true/false), defaults to 'false'
Choices : [true, false, yes, no]

Property : allowNanAndInf
Required : false
Value : false
Description : Should the driver allow NaN or +/- INF values in PreparedStatement.setDouble()?
Choices : [true, false, yes, no]

Property : allowUrlInLocalInfile
Required : false
Value : false
Description : Should the driver allow URLs in 'LOAD DATA LOCAL INFILE' statements?
Choices : [true, false, yes, no]

Property : alwaysSendSetIsolation
Required : false
Value : true
Description : Should the driver always communicate with the database when Connection.setTransactionIsolation() is called? If set to false, the driver will only communicate with the database when the requested transaction isolation is different than the whichever is newer, the last value that was set via Connection.setTransactionIsolation(), or the value that was read from the server when the connection was established.  Note that useLocalSessionState=true will force the same behavior as alwaysSendSetIsolation=false, regardless of how alwaysSendSetIsolation is set.
Choices : [true, false, yes, no]

Property : autoClosePStmtStreams
Required : false
Value : false
Description : Should the driver automatically call .close() on streams/readers passed as arguments via set*() methods?
Choices : [true, false, yes, no]

Property : autoDeserialize
Required : false
Value : false
Description : Should the driver automatically detect and de-serialize objects stored in BLOB fields?
Choices : [true, false, yes, no]

Property : autoGenerateTestcaseScript
Required : false
Value : false
Description : Should the driver dump the SQL it is executing, including server-side prepared statements to STDERR?
Choices : [true, false, yes, no]

Property : autoReconnect
Required : false
Value : false
Description : Should the driver try to re-establish stale and/or dead connections? If enabled the driver will throw an exception for a queries issued on a stale or dead connection, which belong to the current transaction, but will attempt reconnect before the next query issued on the connection in a new transaction. The use of this feature is not recommended, because it has side effects related to session state and data consistency when applications don't handle SQLExceptions properly, and is only designed to be used when you are unable to configure your application to handle SQLExceptions resulting from dead and stale connections properly. Alternatively, investigate setting the MySQL server variable "wait_timeout" to some high value rather than the default of 8 hours.
Choices : [true, false, yes, no]

Property : autoReconnectForPools
Required : false
Value : false
Description : Use a reconnection strategy appropriate for connection pools (defaults to 'false')
Choices : [true, false, yes, no]

Property : blobSendChunkSize
Required : false
Value : 1048576
Description : Chunk to use when sending BLOB/CLOBs via ServerPreparedStatements
Choices : null

Property : autoSlowLog
Required : false
Value : true
Description : Instead of using slowQueryThreshold* to determine if a query is slow enough to be logged, maintain statistics that allow the driver to determine queries that are outside the 99th percentile?
Choices : [true, false, yes, no]

Property : blobsAreStrings
Required : false
Value : false
Description : Should the driver always treat BLOBs as Strings - specifically to work around dubious metadata returned by the server for GROUP BY clauses?
Choices : [true, false, yes, no]

Property : functionsNeverReturnBlobs
Required : false
Value : false
Description : Should the driver always treat data from functions returning BLOBs as Strings - specifically to work around dubious metadata returned by the server for GROUP BY clauses?
Choices : [true, false, yes, no]

Property : cacheCallableStmts
Required : false
Value : false
Description : Should the driver cache the parsing stage of CallableStatements
Choices : [true, false, yes, no]

Property : cachePrepStmts
Required : false
Value : false
Description : Should the driver cache the parsing stage of PreparedStatements of client-side prepared statements, the "check" for suitability of server-side prepared and server-side prepared statements themselves?
Choices : [true, false, yes, no]

Property : cacheResultSetMetadata
Required : false
Value : false
Description : Should the driver cache ResultSetMetaData for Statements and PreparedStatements? (Req. JDK-1.4+, true/false, default 'false')
Choices : [true, false, yes, no]

Property : cacheServerConfiguration
Required : false
Value : false
Description : Should the driver cache the results of 'SHOW VARIABLES' and 'SHOW COLLATION' on a per-URL basis?
Choices : [true, false, yes, no]

Property : callableStmtCacheSize
Required : false
Value : 100
Description : If 'cacheCallableStmts' is enabled, how many callable statements should be cached?
Choices : null

Property : capitalizeTypeNames
Required : false
Value : true
Description : Capitalize type names in DatabaseMetaData? (usually only useful when using WebObjects, true/false, defaults to 'false')
Choices : [true, false, yes, no]

Property : characterEncoding
Required : false
Value : null
Description : If 'useUnicode' is set to true, what character encoding should the driver use when dealing with strings? (defaults is to 'autodetect')
Choices : null

Property : characterSetResults
Required : false
Value : null
Description : Character set to tell the server to return results as.
Choices : null

Property : clientInfoProvider
Required : false
Value : com.mysql.jdbc.JDBC4CommentClientInfoProvider
Description : The name of a class that implements the com.mysql.jdbc.JDBC4ClientInfoProvider interface in order to support JDBC-4.0's Connection.get/setClientInfo() methods
Choices : null

Property : clobberStreamingResults
Required : false
Value : false
Description : This will cause a 'streaming' ResultSet to be automatically closed, and any outstanding data still streaming from the server to be discarded if another query is executed before all the data has been read from the server.
Choices : [true, false, yes, no]

Property : clobCharacterEncoding
Required : false
Value : null
Description : The character encoding to use for sending and retrieving TEXT, MEDIUMTEXT and LONGTEXT values instead of the configured connection characterEncoding
Choices : null

Property : compensateOnDuplicateKeyUpdateCounts
Required : false
Value : false
Description : Should the driver compensate for the update counts of "ON DUPLICATE KEY" INSERT statements (2 = 1, 0 = 1) when using prepared statements?
Choices : [true, false, yes, no]

Property : connectionCollation
Required : false
Value : null
Description : If set, tells the server to use this collation via 'set collation_connection'
Choices : null

Property : connectionLifecycleInterceptors
Required : false
Value : null
Description : A comma-delimited list of classes that implement "com.mysql.jdbc.ConnectionLifecycleInterceptor" that should notified of connection lifecycle events (creation, destruction, commit, rollback, setCatalog and setAutoCommit) and potentially alter the execution of these commands. ConnectionLifecycleInterceptors are "stackable", more than one interceptor may be specified via the configuration property as a comma-delimited list, with the interceptors executed in order from left to right.
Choices : null

Property : connectTimeout
Required : false
Value : 0
Description : Timeout for socket connect (in milliseconds), with 0 being no timeout. Only works on JDK-1.4 or newer. Defaults to '0'.
Choices : null

Property : continueBatchOnError
Required : false
Value : true
Description : Should the driver continue processing batch commands if one statement fails. The JDBC spec allows either way (defaults to 'true').
Choices : [true, false, yes, no]

Property : createDatabaseIfNotExist
Required : false
Value : false
Description : Creates the database given in the URL if it doesn't yet exist. Assumes the configured user has permissions to create databases.
Choices : [true, false, yes, no]

Property : defaultFetchSize
Required : false
Value : 0
Description : The driver will call setFetchSize(n) with this value on all newly-created Statements
Choices : null

Property : useServerPrepStmts
Required : false
Value : false
Description : Use server-side prepared statements if the server supports them?
Choices : [true, false, yes, no]

Property : dontTrackOpenResources
Required : false
Value : false
Description : The JDBC specification requires the driver to automatically track and close resources, however if your application doesn't do a good job of explicitly calling close() on statements or result sets, this can cause memory leakage. Setting this property to true relaxes this constraint, and can be more memory efficient for some applications.
Choices : [true, false, yes, no]

Property : dumpQueriesOnException
Required : false
Value : false
Description : Should the driver dump the contents of the query sent to the server in the message for SQLExceptions?
Choices : [true, false, yes, no]

Property : dynamicCalendars
Required : false
Value : false
Description : Should the driver retrieve the default calendar when required, or cache it per connection/session?
Choices : [true, false, yes, no]

Property : elideSetAutoCommits
Required : false
Value : false
Description : If using MySQL-4.1 or newer, should the driver only issue 'set autocommit=n' queries when the server's state doesn't match the requested state by Connection.setAutoCommit(boolean)?
Choices : [true, false, yes, no]

Property : emptyStringsConvertToZero
Required : false
Value : true
Description : Should the driver allow conversions from empty string fields to numeric values of '0'?
Choices : [true, false, yes, no]

Property : emulateLocators
Required : false
Value : false
Description : Should the driver emulate java.sql.Blobs with locators? With this feature enabled, the driver will delay loading the actual Blob data until the one of the retrieval methods (getInputStream(), getBytes(), and so forth) on the blob data stream has been accessed. For this to work, you must use a column alias with the value of the column to the actual name of the Blob. The feature also has the following restrictions: The SELECT that created the result set must reference only one table, the table must have a primary key; the SELECT must alias the original blob column name, specified as a string, to an alternate name; the SELECT must cover all columns that make up the primary key. 
Choices : [true, false, yes, no]

Property : emulateUnsupportedPstmts
Required : false
Value : true
Description : Should the driver detect prepared statements that are not supported by the server, and replace them with client-side emulated versions?
Choices : [true, false, yes, no]

Property : enablePacketDebug
Required : false
Value : false
Description : When enabled, a ring-buffer of 'packetDebugBufferSize' packets will be kept, and dumped when exceptions are thrown in key areas in the driver's code
Choices : [true, false, yes, no]

Property : enableQueryTimeouts
Required : false
Value : true
Description : When enabled, query timeouts set via Statement.setQueryTimeout() use a shared java.util.Timer instance for scheduling. Even if the timeout doesn't expire before the query is processed, there will be memory used by the TimerTask for the given timeout which won't be reclaimed until the time the timeout would have expired if it hadn't been cancelled by the driver. High-load environments might want to consider disabling this functionality.
Choices : [true, false, yes, no]

Property : explainSlowQueries
Required : false
Value : false
Description : If 'logSlowQueries' is enabled, should the driver automatically issue an 'EXPLAIN' on the server and send the results to the configured log at a WARN level?
Choices : [true, false, yes, no]

Property : exceptionInterceptors
Required : false
Value : null
Description : Comma-delimited list of classes that implement com.mysql.jdbc.ExceptionInterceptor. These classes will be instantiated one per Connection instance, and all SQLExceptions thrown by the driver will be allowed to be intercepted by these interceptors, in a chained fashion, with the first class listed as the head of the chain.
Choices : null

Property : failOverReadOnly
Required : false
Value : true
Description : When failing over in autoReconnect mode, should the connection be set to 'read-only'?
Choices : [true, false, yes, no]

Property : gatherPerfMetrics
Required : false
Value : false
Description : Should the driver gather performance metrics, and report them via the configured logger every 'reportMetricsIntervalMillis' milliseconds?
Choices : [true, false, yes, no]

Property : generateSimpleParameterMetadata
Required : false
Value : false
Description : Should the driver generate simplified parameter metadata for PreparedStatements when no metadata is available either because the server couldn't support preparing the statement, or server-side prepared statements are disabled?
Choices : [true, false, yes, no]

Property : holdResultsOpenOverStatementClose
Required : false
Value : false
Description : Should the driver close result sets on Statement.close() as required by the JDBC specification?
Choices : [true, false, yes, no]

Property : includeInnodbStatusInDeadlockExceptions
Required : false
Value : false
Description : Include the output of "SHOW ENGINE INNODB STATUS" in exception messages when deadlock exceptions are detected?
Choices : [true, false, yes, no]

Property : includeThreadDumpInDeadlockExceptions
Required : false
Value : false
Description : Include a current Java thread dump in exception messages when deadlock exceptions are detected?
Choices : [true, false, yes, no]

Property : includeThreadNamesAsStatementComment
Required : false
Value : false
Description : Include the name of the current thread as a comment visible in "SHOW PROCESSLIST", or in Innodb deadlock dumps, useful in correlation with "includeInnodbStatusInDeadlockExceptions=true" and "includeThreadDumpInDeadlockExceptions=true". 
Choices : [true, false, yes, no]

Property : ignoreNonTxTables
Required : false
Value : false
Description : Ignore non-transactional table warning for rollback? (defaults to 'false').
Choices : [true, false, yes, no]

Property : initialTimeout
Required : false
Value : 2
Description : If autoReconnect is enabled, the initial time to wait between re-connect attempts (in seconds, defaults to '2').
Choices : null

Property : interactiveClient
Required : false
Value : false
Description : Set the CLIENT_INTERACTIVE flag, which tells MySQL to timeout connections based on INTERACTIVE_TIMEOUT instead of WAIT_TIMEOUT
Choices : [true, false, yes, no]

Property : jdbcCompliantTruncation
Required : false
Value : true
Description : Should the driver throw java.sql.DataTruncation exceptions when data is truncated as is required by the JDBC specification when connected to a server that supports warnings (MySQL 4.1.0 and newer)? This property has no effect if the server sql-mode includes STRICT_TRANS_TABLES.
Choices : [true, false, yes, no]

Property : largeRowSizeThreshold
Required : false
Value : 2048
Description : What size result set row should the JDBC driver consider "large", and thus use a more memory-efficient way of representing the row internally?
Choices : null

Property : loadBalanceStrategy
Required : false
Value : random
Description : If using a load-balanced connection to connect to SQL nodes in a MySQL Cluster/NDB configuration (by using the URL prefix "jdbc:mysql:loadbalance://"), which load balancing algorithm should the driver use: (1) "random" - the driver will pick a random host for each request. This tends to work better than round-robin, as the randomness will somewhat account for spreading loads where requests vary in response time, while round-robin can sometimes lead to overloaded nodes if there are variations in response times across the workload. (2) "bestResponseTime" - the driver will route the request to the host that had the best response time for the previous transaction.
Choices : null

Property : loadBalanceBlacklistTimeout
Required : false
Value : 0
Description : Time in milliseconds between checks of servers which are unavailable.
Choices : null

Property : loadBalancePingTimeout
Required : false
Value : 0
Description : Time in milliseconds to wait for ping response from each of load-balanced physical connections when using load-balanced Connection.
Choices : null

Property : loadBalanceValidateConnectionOnSwapServer
Required : false
Value : false
Description : Should the load-balanced Connection explicitly check whether the connection is live when swapping to a new physical connection at commit/rollback?
Choices : [true, false, yes, no]

Property : loadBalanceConnectionGroup
Required : false
Value : null
Description : Logical group of load-balanced connections within a classloader, used to manage different groups independently.  If not specified, live management of load-balanced connections is disabled.
Choices : null

Property : loadBalanceExceptionChecker
Required : false
Value : com.mysql.jdbc.StandardLoadBalanceExceptionChecker
Description : Fully-qualified class name of custom exception checker.  The class must implement com.mysql.jdbc.LoadBalanceExceptionChecker interface, and is used to inspect SQLExceptions and determine whether they should trigger fail-over to another host in a load-balanced deployment.
Choices : null

Property : loadBalanceSQLStateFailover
Required : false
Value : null
Description : Comma-delimited list of SQLState codes used by default load-balanced exception checker to determine whether a given SQLException should trigger failover.  The SQLState of a given SQLException is evaluated to determine whether it begins with any value in the comma-delimited list.
Choices : null

Property : loadBalanceSQLExceptionSubclassFailover
Required : false
Value : null
Description : Comma-delimited list of classes/interfaces used by default load-balanced exception checker to determine whether a given SQLException should trigger failover.  The comparison is done using Class.isInstance(SQLException) using the thrown SQLException.
Choices : null

Property : loadBalanceEnableJMX
Required : false
Value : false
Description : Enables JMX-based management of load-balanced connection groups, including live addition/removal of hosts from load-balancing pool.
Choices : [true, false, yes, no]

Property : loadBalanceAutoCommitStatementRegex
Required : false
Value : null
Description : When load-balancing is enabled for auto-commit statements (via loadBalanceAutoCommitStatementThreshold), the statement counter will only increment when the SQL matches the regular expression.  By default, every statement issued matches.
Choices : null

Property : loadBalanceAutoCommitStatementThreshold
Required : false
Value : 0
Description : When auto-commit is enabled, the number of statements which should be executed before triggering load-balancing to rebalance.  Default value of 0 causes load-balanced connections to only rebalance when exceptions are encountered, or auto-commit is disabled and transactions are explicitly committed or rolled back.
Choices : null

Property : localSocketAddress
Required : false
Value : null
Description : Hostname or IP address given to explicitly configure the interface that the driver will bind the client side of the TCP/IP connection to when connecting.
Choices : null

Property : locatorFetchBufferSize
Required : false
Value : 1048576
Description : If 'emulateLocators' is configured to 'true', what size buffer should be used when fetching BLOB data for getBinaryInputStream?
Choices : null

Property : logger
Required : false
Value : com.mysql.jdbc.log.StandardLogger
Description : The name of a class that implements "com.mysql.jdbc.log.Log"  that will be used to log messages to. (default is "com.mysql.jdbc.log.StandardLogger", which logs to STDERR)
Choices : null

Property : logSlowQueries
Required : false
Value : false
Description : Should queries that take longer than 'slowQueryThresholdMillis' be logged?
Choices : [true, false, yes, no]

Property : logXaCommands
Required : false
Value : false
Description : Should the driver log XA commands sent by MysqlXaConnection to the server, at the DEBUG level of logging?
Choices : [true, false, yes, no]

Property : maintainTimeStats
Required : false
Value : true
Description : Should the driver maintain various internal timers to enable idle time calculations as well as more verbose error messages when the connection to the server fails? Setting this property to false removes at least two calls to System.getCurrentTimeMillis() per query.
Choices : [true, false, yes, no]

Property : maxQuerySizeToLog
Required : false
Value : 2048
Description : Controls the maximum length/size of a query that will get logged when profiling or tracing
Choices : null

Property : maxReconnects
Required : false
Value : 3
Description : Maximum number of reconnects to attempt if autoReconnect is true, default is '3'.
Choices : null

Property : retriesAllDown
Required : false
Value : 120
Description : When using loadbalancing, the number of times the driver should cycle through available hosts, attempting to connect.  Between cycles, the driver will pause for 250ms if no servers are available.
Choices : null

Property : maxRows
Required : false
Value : -1
Description : The maximum number of rows to return (0, the default means return all rows).
Choices : null

Property : metadataCacheSize
Required : false
Value : 50
Description : The number of queries to cache ResultSetMetadata for if cacheResultSetMetaData is set to 'true' (default 50)
Choices : null

Property : netTimeoutForStreamingResults
Required : false
Value : 600
Description : What value should the driver automatically set the server setting 'net_write_timeout' to when the streaming result sets feature is in use? (value has unit of seconds, the value '0' means the driver will not try and adjust this value)
Choices : null

Property : noAccessToProcedureBodies
Required : false
Value : false
Description : When determining procedure parameter types for CallableStatements, and the connected user  can't access procedure bodies through "SHOW CREATE PROCEDURE" or select on mysql.proc  should the driver instead create basic metadata (all parameters reported as IN VARCHARs, but allowing registerOutParameter() to be called on them anyway) instead  of throwing an exception?
Choices : [true, false, yes, no]

Property : noDatetimeStringSync
Required : false
Value : false
Description : Don't ensure that ResultSet.getDatetimeType().toString().equals(ResultSet.getString())
Choices : [true, false, yes, no]

Property : noTimezoneConversionForTimeType
Required : false
Value : false
Description : Don't convert TIME values using the server timezone if 'useTimezone'='true'
Choices : [true, false, yes, no]

Property : nullCatalogMeansCurrent
Required : false
Value : true
Description : When DatabaseMetadataMethods ask for a 'catalog' parameter, does the value null mean use the current catalog? (this is not JDBC-compliant, but follows legacy behavior from earlier versions of the driver)
Choices : [true, false, yes, no]

Property : nullNamePatternMatchesAll
Required : false
Value : true
Description : Should DatabaseMetaData methods that accept *pattern parameters treat null the same as '%' (this is not JDBC-compliant, however older versions of the driver accepted this departure from the specification)
Choices : [true, false, yes, no]

Property : packetDebugBufferSize
Required : false
Value : 20
Description : The maximum number of packets to retain when 'enablePacketDebug' is true
Choices : null

Property : padCharsWithSpace
Required : false
Value : false
Description : If a result set column has the CHAR type and the value does not fill the amount of characters specified in the DDL for the column, should the driver pad the remaining characters with space (for ANSI compliance)?
Choices : [true, false, yes, no]

Property : paranoid
Required : false
Value : false
Description : Take measures to prevent exposure sensitive information in error messages and clear data structures holding sensitive data when possible? (defaults to 'false')
Choices : [true, false, yes, no]

Property : pedantic
Required : false
Value : false
Description : Follow the JDBC spec to the letter.
Choices : [true, false, yes, no]

Property : pinGlobalTxToPhysicalConnection
Required : false
Value : false
Description : When using XAConnections, should the driver ensure that operations on a given XID are always routed to the same physical connection? This allows the XAConnection to support "XA START ... JOIN" after "XA END" has been called
Choices : [true, false, yes, no]

Property : populateInsertRowWithDefaultValues
Required : false
Value : false
Description : When using ResultSets that are CONCUR_UPDATABLE, should the driver pre-populate the "insert" row with default values from the DDL for the table used in the query so those values are immediately available for ResultSet accessors? This functionality requires a call to the database for metadata each time a result set of this type is created. If disabled (the default), the default values will be populated by the an internal call to refreshRow() which pulls back default values and/or values changed by triggers.
Choices : [true, false, yes, no]

Property : prepStmtCacheSize
Required : false
Value : 25
Description : If prepared statement caching is enabled, how many prepared statements should be cached?
Choices : null

Property : prepStmtCacheSqlLimit
Required : false
Value : 256
Description : If prepared statement caching is enabled, what's the largest SQL the driver will cache the parsing for?
Choices : null

Property : processEscapeCodesForPrepStmts
Required : false
Value : true
Description : Should the driver process escape codes in queries that are prepared?
Choices : [true, false, yes, no]

Property : profilerEventHandler
Required : false
Value : com.mysql.jdbc.profiler.LoggingProfilerEventHandler
Description : Name of a class that implements the interface com.mysql.jdbc.profiler.ProfilerEventHandler that will be used to handle profiling/tracing events.
Choices : null

Property : profileSql
Required : false
Value : null
Description : Deprecated, use 'profileSQL' instead. Trace queries and their execution/fetch times on STDERR (true/false) defaults to 'false'
Choices : null

Property : profileSQL
Required : false
Value : false
Description : Trace queries and their execution/fetch times to the configured logger (true/false) defaults to 'false'
Choices : [true, false, yes, no]

Property : propertiesTransform
Required : false
Value : null
Description : An implementation of com.mysql.jdbc.ConnectionPropertiesTransform that the driver will use to modify URL properties passed to the driver before attempting a connection
Choices : null

Property : queriesBeforeRetryMaster
Required : false
Value : 50
Description : Number of queries to issue before falling back to master when failed over (when using multi-host failover). Whichever condition is met first, 'queriesBeforeRetryMaster' or 'secondsBeforeRetryMaster' will cause an attempt to be made to reconnect to the master. Defaults to 50.
Choices : null

Property : queryTimeoutKillsConnection
Required : false
Value : false
Description : If the timeout given in Statement.setQueryTimeout() expires, should the driver forcibly abort the Connection instead of attempting to abort the query?
Choices : [true, false, yes, no]

Property : reconnectAtTxEnd
Required : false
Value : false
Description : If autoReconnect is set to true, should the driver attempt reconnections at the end of every transaction?
Choices : [true, false, yes, no]

Property : relaxAutoCommit
Required : false
Value : false
Description : If the version of MySQL the driver connects to does not support transactions, still allow calls to commit(), rollback() and setAutoCommit() (true/false, defaults to 'false')?
Choices : [true, false, yes, no]

Property : reportMetricsIntervalMillis
Required : false
Value : 30000
Description : If 'gatherPerfMetrics' is enabled, how often should they be logged (in ms)?
Choices : null

Property : requireSSL
Required : false
Value : false
Description : Require SSL connection if useSSL=true? (defaults to 'false').
Choices : [true, false, yes, no]

Property : resourceId
Required : false
Value : null
Description : A globally unique name that identifies the resource that this datasource or connection is connected to, used for XAResource.isSameRM() when the driver can't determine this value based on hostnames used in the URL
Choices : null

Property : resultSetSizeThreshold
Required : false
Value : 100
Description : If the usage advisor is enabled, how many rows should a result set contain before the driver warns that it is suspiciously large?
Choices : null

Property : retainStatementAfterResultSetClose
Required : false
Value : false
Description : Should the driver retain the Statement reference in a ResultSet after ResultSet.close() has been called. This is not JDBC-compliant after JDBC-4.0.
Choices : [true, false, yes, no]

Property : rewriteBatchedStatements
Required : false
Value : false
Description : Should the driver use multiqueries (irregardless of the setting of "allowMultiQueries") as well as rewriting of prepared statements for INSERT into multi-value inserts when executeBatch() is called? Notice that this has the potential for SQL injection if using plain java.sql.Statements and your code doesn't sanitize input correctly. Notice that for prepared statements, server-side prepared statements can not currently take advantage of this rewrite option, and that if you don't specify stream lengths when using PreparedStatement.set*Stream(), the driver won't be able to determine the optimum number of parameters per batch and you might receive an error from the driver that the resultant packet is too large. Statement.getGeneratedKeys() for these rewritten statements only works when the entire batch includes INSERT statements.
Choices : [true, false, yes, no]

Property : rollbackOnPooledClose
Required : false
Value : true
Description : Should the driver issue a rollback() when the logical connection in a pool is closed?
Choices : [true, false, yes, no]

Property : roundRobinLoadBalance
Required : false
Value : false
Description : When autoReconnect is enabled, and failoverReadonly is false, should we pick hosts to connect to on a round-robin basis?
Choices : [true, false, yes, no]

Property : runningCTS13
Required : false
Value : false
Description : Enables workarounds for bugs in Sun's JDBC compliance testsuite version 1.3
Choices : [true, false, yes, no]

Property : secondsBeforeRetryMaster
Required : false
Value : 30
Description : How long should the driver wait, when failed over, before attempting 
Choices : null

Property : selfDestructOnPingSecondsLifetime
Required : false
Value : 0
Description : If set to a non-zero value, the driver will report close the connection and report failure when Connection.ping() or Connection.isValid(int) is called if the connnection's lifetime exceeds this value.
Choices : null

Property : selfDestructOnPingMaxOperations
Required : false
Value : 0
Description : =If set to a non-zero value, the driver will report close the connection and report failure when Connection.ping() or Connection.isValid(int) is called if the connnection's count of commands sent to the server exceeds this value.
Choices : null

Property : serverTimezone
Required : false
Value : null
Description : Override detection/mapping of timezone. Used when timezone from server doesn't map to Java timezone
Choices : null

Property : sessionVariables
Required : false
Value : null
Description : A comma-separated list of name/value pairs to be sent as SET SESSION ... to the server when the driver connects.
Choices : null

Property : slowQueryThresholdMillis
Required : false
Value : 2000
Description : If 'logSlowQueries' is enabled, how long should a query (in ms) before it is logged as 'slow'?
Choices : null

Property : slowQueryThresholdNanos
Required : false
Value : 0
Description : If 'useNanosForElapsedTime' is set to true, and this property is set to a non-zero value, the driver will use this threshold (in nanosecond units) to determine if a query was slow.
Choices : null

Property : socketFactory
Required : false
Value : com.mysql.jdbc.StandardSocketFactory
Description : The name of the class that the driver should use for creating socket connections to the server. This class must implement the interface 'com.mysql.jdbc.SocketFactory' and have public no-args constructor.
Choices : null

Property : socketTimeout
Required : false
Value : 0
Description : Timeout on network socket operations (0, the default means no timeout).
Choices : null

Property : statementInterceptors
Required : false
Value : null
Description : A comma-delimited list of classes that implement "com.mysql.jdbc.StatementInterceptor" that should be placed "in between" query execution to influence the results. StatementInterceptors are "chainable", the results returned by the "current" interceptor will be passed on to the next in in the chain, from left-to-right order, as specified in this property. 
Choices : null

Property : strictFloatingPoint
Required : false
Value : false
Description : Used only in older versions of compliance test
Choices : [true, false, yes, no]

Property : strictUpdates
Required : false
Value : true
Description : Should the driver do strict checking (all primary keys selected) of updatable result sets (true, false, defaults to 'true')?
Choices : [true, false, yes, no]

Property : overrideSupportsIntegrityEnhancementFacility
Required : false
Value : false
Description : Should the driver return "true" for DatabaseMetaData.supportsIntegrityEnhancementFacility() even if the database doesn't support it to workaround applications that require this method to return "true" to signal support of foreign keys, even though the SQL specification states that this facility contains much more than just foreign key support (one such application being OpenOffice)?
Choices : [true, false, yes, no]

Property : tcpNoDelay
Required : false
Value : true
Description : If connecting using TCP/IP, should the driver set SO_TCP_NODELAY (disabling the Nagle Algorithm)?
Choices : [true, false, yes, no]

Property : tcpKeepAlive
Required : false
Value : true
Description : If connecting using TCP/IP, should the driver set SO_KEEPALIVE?
Choices : [true, false, yes, no]

Property : tcpRcvBuf
Required : false
Value : 0
Description : If connecting using TCP/IP, should the driver set SO_RCV_BUF to the given value? The default value of '0', means use the platform default value for this property)
Choices : null

Property : tcpSndBuf
Required : false
Value : 0
Description : If connecting using TCP/IP, should the driver set SO_SND_BUF to the given value? The default value of '0', means use the platform default value for this property)
Choices : null

Property : tcpTrafficClass
Required : false
Value : 0
Description : If connecting using TCP/IP, should the driver set traffic class or type-of-service fields ?See the documentation for java.net.Socket.setTrafficClass() for more information.
Choices : null

Property : tinyInt1isBit
Required : false
Value : true
Description : Should the driver treat the datatype TINYINT(1) as the BIT type (because the server silently converts BIT -> TINYINT(1) when creating tables)?
Choices : [true, false, yes, no]

Property : traceProtocol
Required : false
Value : false
Description : Should trace-level network protocol be logged?
Choices : [true, false, yes, no]

Property : treatUtilDateAsTimestamp
Required : false
Value : true
Description : Should the driver treat java.util.Date as a TIMESTAMP for the purposes of PreparedStatement.setObject()?
Choices : [true, false, yes, no]

Property : transformedBitIsBoolean
Required : false
Value : false
Description : If the driver converts TINYINT(1) to a different type, should it use BOOLEAN instead of BIT for future compatibility with MySQL-5.0, as MySQL-5.0 has a BIT type?
Choices : [true, false, yes, no]

Property : useBlobToStoreUTF8OutsideBMP
Required : false
Value : false
Description : Tells the driver to treat [MEDIUM/LONG]BLOB columns as [LONG]VARCHAR columns holding text encoded in UTF-8 that has characters outside the BMP (4-byte encodings), which MySQL server can't handle natively.
Choices : [true, false, yes, no]

Property : utf8OutsideBmpExcludedColumnNamePattern
Required : false
Value : null
Description : When "useBlobToStoreUTF8OutsideBMP" is set to "true", column names matching the given regex will still be treated as BLOBs unless they match the regex specified for "utf8OutsideBmpIncludedColumnNamePattern". The regex must follow the patterns used for the java.util.regex package.
Choices : null

Property : utf8OutsideBmpIncludedColumnNamePattern
Required : false
Value : null
Description : Used to specify exclusion rules to "utf8OutsideBmpExcludedColumnNamePattern". The regex must follow the patterns used for the java.util.regex package.
Choices : null

Property : useCompression
Required : false
Value : false
Description : Use zlib compression when communicating with the server (true/false)? Defaults to 'false'.
Choices : [true, false, yes, no]

Property : useColumnNamesInFindColumn
Required : false
Value : false
Description : Prior to JDBC-4.0, the JDBC specification had a bug related to what could be given as a "column name" to ResultSet methods like findColumn(), or getters that took a String property. JDBC-4.0 clarified "column name" to mean the label, as given in an "AS" clause and returned by ResultSetMetaData.getColumnLabel(), and if no AS clause, the column name. Setting this property to "true" will give behavior that is congruent to JDBC-3.0 and earlier versions of the JDBC specification, but which because of the specification bug could give unexpected results. This property is preferred over "useOldAliasMetadataBehavior" unless you need the specific behavior that it provides with respect to ResultSetMetadata.
Choices : [true, false, yes, no]

Property : useConfigs
Required : false
Value : null
Description : Load the comma-delimited list of configuration properties before parsing the URL or applying user-specified properties. These configurations are explained in the 'Configurations' of the documentation.
Choices : null

Property : useCursorFetch
Required : false
Value : false
Description : If connected to MySQL > 5.0.2, and setFetchSize() > 0 on a statement, should that statement use cursor-based fetching to retrieve rows?
Choices : [true, false, yes, no]

Property : useDynamicCharsetInfo
Required : false
Value : true
Description : Should the driver use a per-connection cache of character set information queried from the server when necessary, or use a built-in static mapping that is more efficient, but isn't aware of custom character sets or character sets implemented after the release of the JDBC driver?
Choices : [true, false, yes, no]

Property : useDirectRowUnpack
Required : false
Value : true
Description : Use newer result set row unpacking code that skips a copy from network buffers  to a MySQL packet instance and instead reads directly into the result set row data buffers.
Choices : [true, false, yes, no]

Property : useFastIntParsing
Required : false
Value : true
Description : Use internal String->Integer conversion routines to avoid excessive object creation?
Choices : [true, false, yes, no]

Property : useFastDateParsing
Required : false
Value : true
Description : Use internal String->Date/Time/Timestamp conversion routines to avoid excessive object creation?
Choices : [true, false, yes, no]

Property : useHostsInPrivileges
Required : false
Value : true
Description : Add '@hostname' to users in DatabaseMetaData.getColumn/TablePrivileges() (true/false), defaults to 'true'.
Choices : [true, false, yes, no]

Property : useInformationSchema
Required : false
Value : false
Description : When connected to MySQL-5.0.7 or newer, should the driver use the INFORMATION_SCHEMA to derive information used by DatabaseMetaData?
Choices : [true, false, yes, no]

Property : useJDBCCompliantTimezoneShift
Required : false
Value : false
Description : Should the driver use JDBC-compliant rules when converting TIME/TIMESTAMP/DATETIME values' timezone information for those JDBC arguments which take a java.util.Calendar argument? (Notice that this option is exclusive of the "useTimezone=true" configuration option.)
Choices : [true, false, yes, no]

Property : useLocalSessionState
Required : false
Value : false
Description : Should the driver refer to the internal values of autocommit and transaction isolation that are set by Connection.setAutoCommit() and Connection.setTransactionIsolation() and transaction state as maintained by the protocol, rather than querying the database or blindly sending commands to the database for commit() or rollback() method calls?
Choices : [true, false, yes, no]

Property : useLocalTransactionState
Required : false
Value : false
Description : Should the driver use the in-transaction state provided by the MySQL protocol to determine if a commit() or rollback() should actually be sent to the database?
Choices : [true, false, yes, no]

Property : useLegacyDatetimeCode
Required : false
Value : true
Description : Use code for DATE/TIME/DATETIME/TIMESTAMP handling in result sets and statements that consistently handles timezone conversions from client to server and back again, or use the legacy code for these datatypes that has been in the driver for backwards-compatibility?
Choices : [true, false, yes, no]

Property : useNanosForElapsedTime
Required : false
Value : false
Description : For profiling/debugging functionality that measures elapsed time, should the driver try to use nanoseconds resolution if available (JDK >= 1.5)?
Choices : [true, false, yes, no]

Property : useOldAliasMetadataBehavior
Required : false
Value : false
Description : Should the driver use the legacy behavior for "AS" clauses on columns and tables, and only return aliases (if any) for ResultSetMetaData.getColumnName() or ResultSetMetaData.getTableName() rather than the original column/table name? In 5.0.x, the default value was true.
Choices : [true, false, yes, no]

Property : useOldUTF8Behavior
Required : false
Value : false
Description : Use the UTF-8 behavior the driver did when communicating with 4.0 and older servers
Choices : [true, false, yes, no]

Property : useOnlyServerErrorMessages
Required : false
Value : true
Description : Don't prepend 'standard' SQLState error messages to error messages returned by the server.
Choices : [true, false, yes, no]

Property : useReadAheadInput
Required : false
Value : true
Description : Use newer, optimized non-blocking, buffered input stream when reading from the server?
Choices : [true, false, yes, no]

Property : useSqlStateCodes
Required : false
Value : true
Description : Use SQL Standard state codes instead of 'legacy' X/Open/SQL state codes (true/false), default is 'true'
Choices : [true, false, yes, no]

Property : useSSL
Required : false
Value : false
Description : Use SSL when communicating with the server (true/false), defaults to 'false'
Choices : [true, false, yes, no]

Property : useSSPSCompatibleTimezoneShift
Required : false
Value : false
Description : If migrating from an environment that was using server-side prepared statements, and the configuration property "useJDBCCompliantTimeZoneShift" set to "true", use compatible behavior when not using server-side prepared statements when sending TIMESTAMP values to the MySQL server.
Choices : [true, false, yes, no]

Property : useStreamLengthsInPrepStmts
Required : false
Value : true
Description : Honor stream length parameter in PreparedStatement/ResultSet.setXXXStream() method calls (true/false, defaults to 'true')?
Choices : [true, false, yes, no]

Property : useTimezone
Required : false
Value : false
Description : Convert time/date types between client and server timezones (true/false, defaults to 'false')?
Choices : [true, false, yes, no]

Property : ultraDevHack
Required : false
Value : false
Description : Create PreparedStatements for prepareCall() when required, because UltraDev is broken and issues a prepareCall() for _all_ statements? (true/false, defaults to 'false')
Choices : [true, false, yes, no]

Property : useUnbufferedInput
Required : false
Value : true
Description : Don't use BufferedInputStream for reading data from the server
Choices : [true, false, yes, no]

Property : useUnicode
Required : false
Value : true
Description : Should the driver use Unicode character encodings when handling strings? Should only be used when the driver can't determine the character set mapping, or you are trying to 'force' the driver to use a character set that MySQL either doesn't natively support (such as UTF-8), true/false, defaults to 'true'
Choices : [true, false, yes, no]

Property : useUsageAdvisor
Required : false
Value : false
Description : Should the driver issue 'usage' warnings advising proper and efficient usage of JDBC and MySQL Connector/J to the log (true/false, defaults to 'false')?
Choices : [true, false, yes, no]

Property : yearIsDateType
Required : false
Value : true
Description : Should the JDBC driver treat the MySQL type "YEAR" as a java.sql.Date, or as a SHORT?
Choices : [true, false, yes, no]

Property : zeroDateTimeBehavior
Required : false
Value : exception
Description : What should happen when the driver encounters DATETIME values that are composed entirely of zeros (used by MySQL to represent invalid dates)? Valid values are "exception", "round" and "convertToNull".
Choices : [exception, round, convertToNull]

Property : useJvmCharsetConverters
Required : false
Value : false
Description : Always use the character encoding routines built into the JVM, rather than using lookup tables for single-byte character sets?
Choices : [true, false, yes, no]

Property : useGmtMillisForDatetimes
Required : false
Value : false
Description : Convert between session timezone and GMT before creating Date and Timestamp instances (value of "false" is legacy behavior, "true" leads to more JDBC-compliant behavior.
Choices : [true, false, yes, no]

Property : dumpMetadataOnColumnNotFound
Required : false
Value : false
Description : Should the driver dump the field-level metadata of a result set into the exception message when ResultSet.findColumn() fails?
Choices : [true, false, yes, no]

Property : clientCertificateKeyStoreUrl
Required : false
Value : null
Description : URL to the client certificate KeyStore (if not specified, use defaults)
Choices : null

Property : trustCertificateKeyStoreUrl
Required : false
Value : null
Description : URL to the trusted root certificate KeyStore (if not specified, use defaults)
Choices : null

Property : clientCertificateKeyStoreType
Required : false
Value : JKS
Description : KeyStore type for client certificates (NULL or empty means use the default, which is "JKS". Standard keystore types supported by the JVM are "JKS" and "PKCS12", your environment may have more available depending on what security products are installed and available to the JVM.
Choices : null

Property : clientCertificateKeyStorePassword
Required : false
Value : null
Description : Password for the client certificates KeyStore
Choices : null

Property : trustCertificateKeyStoreType
Required : false
Value : JKS
Description : KeyStore type for trusted root certificates (NULL or empty means use the default, which is "JKS". Standard keystore types supported by the JVM are "JKS" and "PKCS12", your environment may have more available depending on what security products are installed and available to the JVM.
Choices : null

Property : trustCertificateKeyStorePassword
Required : false
Value : null
Description : Password for the trusted root certificates KeyStore
Choices : null

Property : verifyServerCertificate
Required : false
Value : true
Description : If "useSSL" is set to "true", should the driver verify the server's certificate? When using this feature, the keystore parameters should be specified by the "clientCertificateKeyStore*" properties, rather than system properties.
Choices : [true, false, yes, no]

Property : useAffectedRows
Required : false
Value : false
Description : Don't set the CLIENT_FOUND_ROWS flag when connecting to the server (not JDBC-compliant, will break most applications that rely on "found" rows vs. "affected rows" for DML statements), but does cause "correct" update counts from "INSERT ... ON DUPLICATE KEY UPDATE" statements to be returned by the server.
Choices : [true, false, yes, no]

Property : passwordCharacterEncoding
Required : false
Value : null
Description : What character encoding is used for passwords? Leaving this set to the default value (null), uses the platform character set, which works for ISO8859_1 (i.e. "latin1") passwords. For passwords in other character encodings, the encoding will have to be specified with this property, as it's not possible for the driver to auto-detect this.
Choices : null

Property : maxAllowedPacket
Required : false
Value : -1
Description : Maximum allowed packet size to send to server. If not set, the value of system variable 'max_allowed_packet' will be used to initialize this upon connecting. This value will not take effect if set larger than the value of 'max_allowed_packet'.
Choices : null

 
This was an example of how to get the JDBC Connection parameters in Java.

(No Ratings Yet)
Start the discussion Views Tweet it!

Do you want to know how to develop your skillset to become a Java Rockstar?

Subscribe to our newsletter to start Rocking right now!

To get you started we give you our best selling eBooks for FREE!

 

1. JPA Mini Book

2. JVM Troubleshooting Guide

3. JUnit Tutorial for Unit Testing

4. Java Annotations Tutorial

5. Java Interview Questions

6. Spring Interview Questions

7. Android UI Design

 

and many more ....

 

Receive Java & Developer job alerts in your Area

 

Leave a Reply

avatar
  Subscribe  
Notify of