MySQL Connector/J JDBC驱动指南：面向英语学习者的入门文档

需积分: 4 150 浏览量更新于2024-07-27 收藏 609KB PDF 举报

MySQL Connector/J 是一个专为Java开发者设计的JDBC（Java Database Connectivity）实现，用于与MySQL数据库服务器进行高效、安全的通信。此文档是一份详细的用户手册，旨在指导初学者和英语爱好者了解如何通过Java语言与MySQL进行集成，包括连接配置、执行SQL查询、处理结果集以及遵循最佳实践等关键概念。文档生成日期为2008年10月20日，版本号为12106，它由MySQL AB公司和Sun Microsystems, Inc.共同维护。MySQL Connector/J的版权归属在这段时间内有所变化，早期由MySQL AB持有，而在2008年后则纳入了Sun Microsystems的版权范围。这份文档并非遵循GPL（GNU通用公共许可证），其使用权限有限制：用户仅限于个人用途下创建打印副本，且在转为其他格式时必须保持内容原貌不变，不得擅自修改或编辑。重要的是，未经授权，不得以任何形式（包括纸质复印件或在其他出版物中使用）发布或分发这份文档，除非是通过与软件一起以电子形式在线提供，或者在CD-ROM等相似介质上随软件一同分发，且需确保文档的分发方式与Sun Microsystems的标准分发方式类似。在使用MySQL Connector/J时，关键知识点包括： 1. 安装与配置：文档会指导用户如何下载并安装该驱动程序，以及如何在Java应用程序中正确配置连接参数，如URL、用户名和密码等。 2. 连接管理：学习如何建立和关闭与MySQL服务器的连接，理解连接池的概念以提高性能和资源利用率。 3. 执行SQL操作：涵盖如何使用PreparedStatement对象发送预编译的SQL语句，以及如何执行基本的SELECT、INSERT、UPDATE和DELETE操作。 4. 结果集处理：讲解如何处理查询结果，包括ResultSet对象的遍历、获取单个值、获取多个值以及处理BLOB和CLOB数据类型。 5. 错误处理与异常处理：提供如何识别和处理可能出现的连接错误、SQL语法错误以及其他运行时异常的策略。 6. 安全性与加密：介绍如何配置SSL/TLS连接以增强数据传输的安全性，以及如何处理用户身份验证和权限管理。 7. 最佳实践：包含关于代码优化、性能调优、线程管理和资源清理等方面的实用建议。 8. 更新与兼容性：可能包含关于最新版本之间的差异、向下兼容性以及与MySQL服务器版本的适配指南。 MySQL Connector/J帮助文档对于任何希望在Java应用中使用MySQL数据库的开发人员来说，是不可或缺的学习资源，提供了详尽的操作指南和参考。阅读并掌握其中内容，将有助于提升开发效率和数据库管理能力。

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.

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

can cause memory leakage. Setting this property to true relaxes

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

ations.

false 3.1.7

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

random 5.0.6

Connector/J (JDBC) Reference

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.

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

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

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

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

Connector/J (JDBC) Reference

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

includeInnodbStatusInDeadlockExcep-

tions

Include the output of "SHOW ENGINE INNODB STATUS" in

exception messages when deadlock exceptions are detected?

false 5.0.7

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

Connector/J (JDBC) Reference

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

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

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

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-

false 3.1.0

Connector/J (JDBC) Reference

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.

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

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

false 5.0.8

generateSimpleParameterMetadata Should the driver generate simplified parameter metadata for Pre-

paredStatements when no metadata is available either because the

server couldn't support preparing the statement, or server-side pre-

pared statements are disabled?

false 5.0.5

ignoreNonTxTables Ignore non-transactional table warning for rollback? (defaults to

'false').

false 3.0.9

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

true 3.1.2

maxRows The maximum number of rows to return (0, the default means re-

turn all rows).

-1 all versions

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

600 5.1.0

noAccessToProcedureBodies When determining procedure parameter types for CallableState-

ments, 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 registerOut-

Parameter() to be called on them anyway) instead of throwing an

exception?

false 5.0.3

noDatetimeStringSync Don't ensure that Result-

Set.getDatetimeType().toString().equals(ResultSet.getString())

false 3.1.7

noTimezoneConversionForTimeType Don't convert TIME values using the server timezone if 'use-

Timezone'='true'

false 5.0.0

nullCatalogMeansCurrent When DatabaseMetadataMethods ask for a 'catalog' parameter,

does the value null mean use the current catalog? (this is not JD-

BC-compliant, but follows legacy behavior from earlier versions

of the driver)

true 3.1.8

nullNamePatternMatchesAll Should DatabaseMetaData methods that accept *pattern paramet-

ers treat null the same as '%' (this is not JDBC-compliant, however

older versions of the driver accepted this departure from the spe-

cification)

true 3.1.8

overrideSupportsIntegrityEnhance-

mentFacility

Should the driver return "true" for Database-

MetaData.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)?

false 3.1.12

padCharsWithSpace If a result set column has the CHAR type and the value does not false 5.0.6

Connector/J (JDBC) Reference

剩余118页未读，继续阅读

wwe619000

粉丝: 0
资源: 1

MySQL Connector/J JDBC驱动指南：面向英语学习者的入门文档

MySql命令帮助文档

MYSQL5.1 CHM版中文帮助文档.zip_MYSQL_msql 5.1 API文档

Mysql中文帮助文档

php中文帮助文档-mysql中文帮助文档-php-mysql-DBHlper

mysql帮助文档

Mysql帮助文档

mysql 离线帮助文档 下载

MySQL连接工具

php mysql 连接

Mysql 连接 Tool

最新资源

mysql 离线帮助文档下载