Connector/J commit: r6499 - branches/branch_5_1/connector-j/src/com/mysql/jdbc

[mcbrown]

Modified:
   branches/branch_5_1/connector-j/src/com/mysql/jdbc/LocalizedErrorMessages.properties
Log:
Correcting some typos in descriptions



Modified:
branches/branch_5_1/connector-j/src/com/mysql/jdbc/LocalizedErrorMessages.properties
===================================================================
---
branches/branch_5_1/connector-j/src/com/mysql/jdbc/LocalizedErrorMessages.properties	2007-08-29
14:05:58 UTC (rev 6498)
+++
branches/branch_5_1/connector-j/src/com/mysql/jdbc/LocalizedErrorMessages.properties	2007-08-29
14:11:48 UTC (rev 6499)
@@ -484,7 +484,7 @@
 ConnectionProperties.interactiveClient=Set the CLIENT_INTERACTIVE flag, which tells MySQL
to timeout connections based on INTERACTIVE_TIMEOUT instead of WAIT_TIMEOUT
 ConnectionProperties.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)?
 ConnectionProperties.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?
-ConnectionProperties.loadBalanceStrategy=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 balancin 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.
+ConnectionProperties.loadBalanceStrategy=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.
 ConnectionProperties.localSocketAddress=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.
 ConnectionProperties.locatorFetchBufferSize=If 'emulateLocators' is configured to 'true',
what size buffer should be used when fetching BLOB data for getBinaryInputStream?
 ConnectionProperties.logger=The name of a class that implements \"{0}\"  that will be
used to log messages to. (default is \"{1}\", which logs to STDERR)
@@ -507,7 +507,7 @@
 ConnectionProperties.paranoid=Take measures to prevent exposure sensitive information in
error messages and clear data structures holding sensitive data when possible? (defaults
to 'false')
 ConnectionProperties.pedantic=Follow the JDBC spec to the letter.
 ConnectionProperties.pinGlobalTxToPhysicalConnection=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
-ConnectionProperties.populateInsertRowWithDefaultValues=When using ResultSets that are
CONCUR_UPDATABLE, should the driver pre-poulate 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.
+ConnectionProperties.populateInsertRowWithDefaultValues=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.
 ConnectionProperties.prepStmtCacheSize=If prepared statement caching is enabled, how many
prepared statements should be cached?
 ConnectionProperties.prepStmtCacheSqlLimit=If prepared statement caching is enabled,
what's the largest SQL the driver will cache the parsing for?
 ConnectionProperties.processEscapeCodesForPrepStmts=Should the driver process escape
codes in queries that are prepared?
@@ -522,7 +522,7 @@
 ConnectionProperties.resourceId=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
 ConnectionProperties.resultSetSizeThreshold=If the usage advisor is enabled, how many
rows should a result set contain before the driver warns that it is suspiciously large?
 ConnectionProperties.retainStatementAfterResultSetClose=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.
-ConnectionProperties.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 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 optimium 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.
+ConnectionProperties.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 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.
 ConnectionProperties.rollbackOnPooledClose=Should the driver issue a rollback() when the
logical connection in a pool is closed?
 ConnectionProperties.roundRobinLoadBalance=When autoReconnect is enabled, and
failoverReadonly is false, should we pick hosts to connect to on a round-robin basis?
 ConnectionProperties.runningCTS13=Enables workarounds for bugs in Sun's JDBC compliance
testsuite version 1.3
@@ -554,7 +554,7 @@
 ConnectionProperties.useCursorFetch=If connected to MySQL > 5.0.2, and setFetchSize()
> 0 on a statement, should that statement use cursor-based fetching to retrieve rows?
 ConnectionProperties.useDynamicCharsetInfo=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?
 ConnectionProperties.useFastIntParsing=Use internal String->Integer conversion
routines to avoid excessive object creation?
-ConnectionProperties.useFastDateParsing=Use internal String->Date/Time/Teimstamp
conversion routines to avoid excessive object creation?
+ConnectionProperties.useFastDateParsing=Use internal String->Date/Time/Timestamp
conversion routines to avoid excessive object creation?
 ConnectionProperties.useHostsInPrivileges=Add '@hostname' to users in
DatabaseMetaData.getColumn/TablePrivileges() (true/false), defaults to 'true'.
 ConnectionProperties.useInformationSchema=When connected to MySQL-5.0.7 or newer, should
the driver use the INFORMATION_SCHEMA to derive information used by DatabaseMetaData?
 ConnectionProperties.useJDBCCompliantTimezoneShift=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.)