MySQL Connector/J：JDBC驱动使用与参考

需积分: 10 101 浏览量更新于2024-07-30 收藏 624KB PDF 举报

"MySQL Connector/J 是MySQL数据库与Java应用程序之间的JDBC驱动程序，它使得Java开发者能够连接到MySQL服务器并执行SQL操作。本手册详细涵盖了不同版本的Connector/J、安装指南、示例、参考信息、注意事项和技术支持。此外，还包含了变更历史记录以及第三方组件的许可信息。" MySQL Connector/J是Oracle公司提供的一个关键组件，它实现了Java Database Connectivity (JDBC) API，允许Java应用与MySQL数据库进行交互。JDBC是一个Java平台的标准，提供了统一的接口，用于访问各种类型的数据库系统。 **Chapter 1. Connector/J Versions** 在这一章节中，可能会介绍各个版本的Connector/J，包括主要版本的区别、新功能、修复的bug以及对MySQL服务器版本的支持情况。了解这些信息对于选择适合项目需求的驱动版本至关重要。 **Chapter 2. Connector/J Installation** 这部分会提供安装Connector/J的详细步骤，包括如何将驱动添加到Java项目的类路径中，以及在Tomcat等应用服务器中配置连接器。此外，还会涉及不同操作系统和开发环境下的安装注意事项。 **Chapter 3. Connector/J Examples** 示例章节通常包含代码片段，演示如何创建数据库连接、执行SQL查询、处理结果集以及管理事务。这些例子对于初学者理解和使用Connector/J非常有帮助。 **Chapter 4. Connector/J (JDBC) Reference** 这个章节提供了关于Connector/J API的详细参考文档，包括类、接口和方法的描述。开发者可以查阅这个部分来了解如何使用特定的API调用来完成数据库操作。 **Chapter 5. Connector/J Notes and Tips** 这里可能包含了一些最佳实践、性能优化建议以及解决常见问题的方法。这些提示对于提升应用程序性能和解决可能出现的问题非常实用。 **Chapter 6. Connector/J Support** 这部分可能会讨论官方提供的技术支持渠道，如社区论坛、在线文档、知识库以及如何获取官方的帮助。此外，也可能包含错误报告的指导，帮助用户有效地报告和解决问题。 **Appendix A. MySQL Connector/J Change History** 变更历史记录提供了每个版本的更新详情，包括新增特性、改进和已知问题的修复，这对于跟踪驱动程序的演化和决定升级策略是很有价值的。 **Appendix B. Licenses for Third-Party Components** 这部分列出了所有使用到的第三方组件及其许可信息，这对于遵守开源软件的授权规定是必不可少的。 MySQL Connector/J是Java开发者连接MySQL数据库的重要工具，其全面的手册为用户提供了丰富的参考资料，从安装到实际应用的每一个环节都得到了详尽的说明。通过理解和熟练运用这些知识，开发者可以构建高效、稳定的Java应用与MySQL数据库之间的连接。

this.

Performance Extensions.

Property Name Definition Default

Value

Since Ver-

sion

callableStmtCacheSize If 'cacheCallableStmts' is enabled, how many callable statements

should be cached?

100 3.1.2

metadataCacheSize The number of queries to cache ResultSetMetadata for if

cacheResultSetMetaData is set to 'true' (default 50)

50 3.1.1

useLocalSessionState 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 roll-

back() method calls?

false 3.1.7

useLocalTransactionState 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?

false 5.1.7

prepStmtCacheSize If prepared statement caching is enabled, how many prepared

statements should be cached?

25 3.0.10

prepStmtCacheSqlLimit If prepared statement caching is enabled, what's the largest SQL

the driver will cache the parsing for?

256 3.0.10

alwaysSendSetIsolation 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 reques-

ted transaction isolation is different than the whichever is newer,

the last value that was set via Connec-

tion.setTransactionIsolation(), or the value that was read from the

server when the connection was established. Note that useLoc-

alSessionState=true will force the same behavior as alwaysSend-

SetIsolation=false, regardless of how alwaysSendSetIsolation is

set.

true 3.1.7

maintainTimeStats 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 re-

moves at least two calls to System.getCurrentTimeMillis() per

query.

true 3.1.9

useCursorFetch If connected to MySQL > 5.0.2, and setFetchSize() > 0 on a state-

ment, should that statement use cursor-based fetching to retrieve

rows?

false 5.0.0

blobSendChunkSize Chunk to use when sending BLOB/CLOBs via ServerPrepared-

Statements

1048576 3.1.9

cacheCallableStmts Should the driver cache the parsing stage of CallableStatements false 3.1.2

cachePrepStmts Should the driver cache the parsing stage of PreparedStatements of

client-side prepared statements, the "check" for suitability of serv-

er-side prepared and server-side prepared statements themselves?

false 3.0.10

cacheResultSetMetadata Should the driver cache ResultSetMetaData for Statements and

PreparedStatements? (Req. JDK-1.4+, true/false, default 'false')

false 3.1.1

cacheServerConfiguration Should the driver cache the results of 'SHOW VARIABLES' and

'SHOW COLLATION' on a per-URL basis?

false 3.1.5

defaultFetchSize The driver will call setFetchSize(n) with this value on all newly-

created Statements

0 3.1.9

dontTrackOpenResources 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

false 3.1.7

Connector/J (JDBC) Reference

can cause memory leakage. Setting this property to true relaxes

this constraint, and can be more memory efficient for some applic-

ations.

dynamicCalendars Should the driver retrieve the default calendar when required, or

cache it per connection/session?

false 3.1.5

elideSetAutoCommits 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)?

false 3.1.3

enableQueryTimeouts When enabled, query timeouts set via State-

ment.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 function-

ality.

true 5.0.6

holdResultsOpenOverStatementClose Should the driver close result sets on Statement.close() as required

by the JDBC specification?

false 3.1.7

largeRowSizeThreshold What size result set row should the JDBC driver consider "large",

and thus use a more memory-efficient way of representing the row

internally?

2048 5.1.1

loadBalanceStrategy If using a load-balanced connection to connect to SQL nodes in a

MySQL Cluster/NDB configuration (by using the URL prefix "jd-

bc: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 re-

quests 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.

random 5.0.6

locatorFetchBufferSize If 'emulateLocators' is configured to 'true', what size buffer should

be used when fetching BLOB data for getBinaryInputStream?

1048576 3.2.1

rewriteBatchedStatements 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 cor-

rectly. 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 Prepared-

Statement.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. State-

ment.getGeneratedKeys() for these rewritten statements only

works when the entire batch includes INSERT statements.

false 3.1.13

useDirectRowUnpack Use newer result set row unpacking code that skips a copy from

network buffers to a MySQL packet instance and instead reads dir-

ectly into the result set row data buffers.

true 5.1.1

useDynamicCharsetInfo Should the driver use a per-connection cache of character set in-

formation 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?

true 5.0.6

useFastDateParsing Use internal String->Date/Time/Timestamp conversion routines to

avoid excessive object creation?

true 5.0.5

useFastIntParsing Use internal String->Integer conversion routines to avoid excess-

ive object creation?

true 3.1.4

Connector/J (JDBC) Reference

useJvmCharsetConverters Always use the character encoding routines built into the JVM,

rather than using lookup tables for single-byte character sets?

false 5.0.1

useReadAheadInput Use newer, optimized non-blocking, buffered input stream when

reading from the server?

true 3.1.5

Debugging/Profiling.

Property Name Definition Default

Value

Since Ver-

sion

logger 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)

com.mysql.j

dbc.log.Sta

ndardLog-

ger

3.1.1

gatherPerfMetrics Should the driver gather performance metrics, and report them via

the configured logger every 'reportMetricsIntervalMillis' milli-

seconds?

false 3.1.2

profileSQL Trace queries and their execution/fetch times to the configured

logger (true/false) defaults to 'false'

false 3.1.0

profileSql Deprecated, use 'profileSQL' instead. Trace queries and their exe-

cution/fetch times on STDERR (true/false) defaults to 'false'

2.0.14

reportMetricsIntervalMillis If 'gatherPerfMetrics' is enabled, how often should they be logged

(in ms)?

30000 3.1.2

maxQuerySizeToLog Controls the maximum length/size of a query that will get logged

when profiling or tracing

2048 3.1.3

packetDebugBufferSize The maximum number of packets to retain when 'enablePacketDe-

bug' is true

20 3.1.3

slowQueryThresholdMillis If 'logSlowQueries' is enabled, how long should a query (in ms)

before it is logged as 'slow'?

2000 3.1.2

slowQueryThresholdNanos If 'useNanosForElapsedTime' is set to true, and this property is set

to a non-zero value, the driver will use this threshold (in nano-

second units) to determine if a query was slow.

0 5.0.7

useUsageAdvisor Should the driver issue 'usage' warnings advising proper and effi-

cient usage of JDBC and MySQL Connector/J to the log

(true/false, defaults to 'false')?

false 3.1.1

autoGenerateTestcaseScript Should the driver dump the SQL it is executing, including server-

side prepared statements to STDERR?

false 3.1.9

autoSlowLog 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?

true 5.1.4

clientInfoProvider 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

com.mysql.j

dbc.JDBC4

Com-

mentCli-

entInfoPro-

vider

5.1.0

dumpMetadataOnColumnNotFound Should the driver dump the field-level metadata of a result set into

the exception message when ResultSet.findColumn() fails?

false 3.1.13

dumpQueriesOnException Should the driver dump the contents of the query sent to the server

in the message for SQLExceptions?

false 3.1.3

enablePacketDebug 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

false 3.1.3

explainSlowQueries If 'logSlowQueries' is enabled, should the driver automatically is-

sue an 'EXPLAIN' on the server and send the results to the con-

figured log at a WARN level?

false 3.1.2

Connector/J (JDBC) Reference

includeInnodbStatusInDeadlockExcep-

tions

Include the output of "SHOW ENGINE INNODB STATUS" in

exception messages when deadlock exceptions are detected?

false 5.0.7

includeThreadDumpInDeadlockExcep-

tions

Include a current Java thread dump in exception messages when

deadlock exceptions are detected?

false 5.1.15

includeThreadNamesAsStatement-

Comment

Include the name of the current thread as a comment visible in

"SHOW PROCESSLIST", or in Innodb deadlock dumps, useful in

correlation with "includeInnodbStatusInDeadlockExcep-

tions=true" and "includeThreadDumpInDeadlockExcep-

tions=true".

false 5.1.15

logSlowQueries Should queries that take longer than 'slowQueryThresholdMillis'

be logged?

false 3.1.2

logXaCommands Should the driver log XA commands sent by MysqlXaConnection

to the server, at the DEBUG level of logging?

false 5.0.5

profilerEventHandler Name of a class that implements the interface

com.mysql.jdbc.profiler.ProfilerEventHandler that will be used to

handle profiling/tracing events.

com.mysql.j

dbc.profiler.

Logging-

Pro-

filerEventH

andler

5.1.6

resultSetSizeThreshold If the usage advisor is enabled, how many rows should a result set

contain before the driver warns that it is suspiciously large?

100 5.0.5

traceProtocol Should trace-level network protocol be logged? false 3.1.2

useNanosForElapsedTime For profiling/debugging functionality that measures elapsed time,

should the driver try to use nanoseconds resolution if available

(JDK >= 1.5)?

false 5.0.7

Miscellaneous.

Property Name Definition Default

Value

Since Ver-

sion

useUnicode 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'

true 1.1g

characterEncoding If 'useUnicode' is set to true, what character encoding should the

driver use when dealing with strings? (defaults is to 'autodetect')

1.1g

characterSetResults Character set to tell the server to return results as. 3.0.13

connectionCollation If set, tells the server to use this collation via 'set colla-

tion_connection'

3.0.13

useBlobToStoreUTF8OutsideBMP 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.

false 5.1.3

utf8OutsideBmpExcludedColumnNam

ePattern

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.

5.1.3

utf8OutsideBmpIncludedColumnName

Pattern

Used to specify exclusion rules to

"utf8OutsideBmpExcludedColumnNamePattern". The regex must

follow the patterns used for the java.util.regex package.

5.1.3

loadBalanceEnableJMX Enables JMX-based management of load-balanced connection

groups, including live addition/removal of hosts from load-

balancing pool.

false 5.1.13

Connector/J (JDBC) Reference

sessionVariables A comma-separated list of name/value pairs to be sent as SET

SESSION ... to the server when the driver connects.

3.1.8

useColumnNamesInFindColumn 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 cla-

rified "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 ver-

sions of the JDBC specification, but which because of the specific-

ation bug could give unexpected results. This property is preferred

over "useOldAliasMetadataBehavior" unless you need the specific

behavior that it provides with respect to ResultSetMetadata.

false 5.1.7

allowNanAndInf Should the driver allow NaN or +/- INF values in PreparedState-

ment.setDouble()?

false 3.1.5

autoClosePStmtStreams Should the driver automatically call .close() on streams/readers

passed as arguments via set*() methods?

false 3.1.12

autoDeserialize Should the driver automatically detect and de-serialize objects

stored in BLOB fields?

false 3.1.5

blobsAreStrings Should the driver always treat BLOBs as Strings - specifically to

work around dubious metadata returned by the server for GROUP

BY clauses?

false 5.0.8

capitalizeTypeNames Capitalize type names in DatabaseMetaData? (usually only useful

when using WebObjects, true/false, defaults to 'false')

true 2.0.7

clobCharacterEncoding The character encoding to use for sending and retrieving TEXT,

MEDIUMTEXT and LONGTEXT values instead of the con-

figured connection characterEncoding

5.0.0

clobberStreamingResults This will cause a 'streaming' ResultSet to be automatically closed,

and any outstanding data still streaming from the server to be dis-

carded if another query is executed before all the data has been

read from the server.

false 3.0.9

compensateOnDuplicateKeyUpdate-

Counts

Should the driver compensate for the update counts of "ON DU-

PLICATE KEY" INSERT statements (2 = 1, 0 = 1) when using

prepared statements?

false 5.1.7

continueBatchOnError Should the driver continue processing batch commands if one

statement fails. The JDBC spec allows either way (defaults to

'true').

true 3.0.3

createDatabaseIfNotExist Creates the database given in the URL if it doesn't yet exist. As-

sumes the configured user has permissions to create databases.

false 3.1.9

emptyStringsConvertToZero Should the driver allow conversions from empty string fields to

numeric values of '0'?

true 3.1.8

emulateLocators 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(), get-

Bytes(), 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.

false 3.1.0

emulateUnsupportedPstmts Should the driver detect prepared statements that are not supported

by the server, and replace them with client-side emulated ver-

sions?

true 3.1.7

exceptionInterceptors Comma-delimited list of classes that implement

com.mysql.jdbc.ExceptionInterceptor. These classes will be in-

stantiated one per Connection instance, and all SQLExceptions

5.1.8

Connector/J (JDBC) Reference

剩余144页未读，继续阅读

summerhai

粉丝: 13
资源: 13

MySQL Connector/J：JDBC驱动使用与参考

mysql Connector/J 5.1.31 官网下载最新版

mysql-connector-java-8.0.15.jar

MySQL Connector/J-5.1.9

MySQL的jar包，包含mysql-connector-java-5.1.49和mysql-connector-j-8.1.0

mysql-connector-j-5.0.5

mysql-connector-j-8.0.33.jar

mysql-connector-j-8.0.32.jar

mysql-connector-j-8.0.32.zip

mysql-connector-j-8.2.0.zip

mysql-connector-j和mysql-connector-java

最新资源