📄 localizederrormessages.properties
字号:
MysqlIO.59=send() packet payload:\nMysqlIO.60=Unable to open file MysqlIO.63=for 'LOAD DATA LOCAL INFILE' command.MysqlIO.64=Due to underlying IOException: MysqlIO.65=Unable to close local file during LOAD DATA LOCAL INFILE commandMysqlIO.68=\ message from server: "MysqlIO.70=Unknown columnMysqlIO.72=\ message from server: "MysqlIO.75=No name specified for socket factoryMysqlIO.76=Could not create socket factory 'MysqlIO.77=' due to underlying exception: MysqlIO.79=Unexpected end of input streamMysqlIO.80=Unexpected end of input streamMysqlIO.81=Unexpected end of input streamMysqlIO.82=Unexpected end of input streamMysqlIO.83=Packets received out of orderMysqlIO.84=Packets received out of orderMysqlIO.85=Unexpected end of input streamMysqlIO.86=Unexpected end of input streamMysqlIO.87=Unexpected end of input streamMysqlIO.88=Packets received out of orderMysqlIO.89=Packets received out of orderMysqlIO.91=Failed to create message digest 'SHA-1' for authentication. MysqlIO.92=\ You must use a JDK that supports JCE to be able to use secure connection authenticationMysqlIO.93=Failed to create message digest 'SHA-1' for authentication. MysqlIO.94=\ You must use a JDK that supports JCE to be able to use secure connection authenticationMysqlIO.95=Failed to create message digest 'SHA-1' for authentication. MysqlIO.96=\ You must use a JDK that supports JCE to be able to use secure connection authenticationMysqlIO.97=Unknown type 'MysqlIO.98=\ in column MysqlIO.99=\ of MysqlIO.100=\ in binary-encoded result set.MysqlIO.102=, underlying cause: MysqlIO.EOF=Can not read response from server. Expected to read {0} bytes, read {1} bytes before connection was unexpectedly lost.MysqlIO.NoInnoDBStatusFound=No InnoDB status output returned by server.MysqlIO.InnoDBStatusFailed=Couldn't retrieve InnoDB status due to underlying exception: MysqlIO.LoadDataLocalNotAllowed=Server asked for stream in response to LOAD DATA LOCAL INFILE but functionality is disabled at client by 'allowLoadLocalInfile' being set to 'false'.NotImplemented.0=Feature not implementedPreparedStatement.0=SQL String can not be NULLPreparedStatement.1=SQL String can not be NULLPreparedStatement.2=Parameter index out of range (PreparedStatement.3=\ > PreparedStatement.4=)PreparedStatement.16=Unknown Types valuePreparedStatement.17=Cannot convert PreparedStatement.18=\ to SQL type requested due to PreparedStatement.19=\ - PreparedStatement.20=Connection is read-only. PreparedStatement.21=Queries leading to data modification are not allowedPreparedStatement.25=Connection is read-only. PreparedStatement.26=Queries leading to data modification are not allowedPreparedStatement.32=Unsupported character encoding 'PreparedStatement.33='PreparedStatement.34=Connection is read-only. PreparedStatement.35=Queries leading to data modification are not allowedPreparedStatement.37=Can not issue executeUpdate() for SELECTsPreparedStatement.40=No value specified for parameter PreparedStatement.43=PreparedStatement created, but used 1 or fewer times. It is more efficient to prepare statements once, and re-use them many timesPreparedStatement.48=PreparedStatement has been closed. No further operations allowed.PreparedStatement.49=Parameter index out of range (PreparedStatement.50=\ < 1 ).PreparedStatement.51=Parameter index out of range (PreparedStatement.52=\ > number of parameters, which is PreparedStatement.53=).PreparedStatement.54=Invalid argument value: PreparedStatement.55=Error reading from InputStream PreparedStatement.56=Error reading from InputStream PreparedStatement.61=SQL String can not be NULLServerPreparedStatement.2=Connection is read-only. ServerPreparedStatement.3=Queries leading to data modification are not allowedServerPreparedStatement.6=\ unable to materialize as string due to underlying SQLException: ServerPreparedStatement.7=Not supported for server-side prepared statements.ServerPreparedStatement.8=No parameters defined during prepareCall()ServerPreparedStatement.9=Parameter index out of bounds. ServerPreparedStatement.10=\ is not between valid values of 1 and ServerPreparedStatement.11=Driver can not re-execute prepared statement when a parameter has been changed ServerPreparedStatement.12=from a streaming type to an intrinsic data type without calling clearParameters() first.ServerPreparedStatement.13=Statement parameter ServerPreparedStatement.14=\ not set.ServerPreparedStatement.15=Slow query (exceeded ServerPreparedStatement.15a=\ ms., duration:\ ServerPreparedStatement.16=\ ms): ServerPreparedStatement.18=Unknown LONG DATA type 'ServerPreparedStatement.22=Unsupported character encoding 'ServerPreparedStatement.24=Error while reading binary stream: ServerPreparedStatement.25=Error while reading binary stream: ByteArrayBuffer.0=ByteArrayBuffer has no NIO buffersByteArrayBuffer.1=Unsupported character encoding 'AssertionFailedException.0=ASSERT FAILS: Exception AssertionFailedException.1=\ that should not be thrown, was thrownNotUpdatable.0=Result Set not updatable.NotUpdatable.1=This result set must come from a statement NotUpdatable.2=that was created with a result set type of ResultSet.CONCUR_UPDATABLE, NotUpdatable.3=the query must select only one table, can not use functions and must NotUpdatable.4=select all primary keys from that table. See the JDBC 2.1 API Specification, NotUpdatable.5=section 5.6 for more details.NotUpdatableReason.0=Result Set not updatable (references more than one table).NotUpdatableReason.1=Result Set not updatable (references more than one database).NotUpdatableReason.2=Result Set not updatable (references no tables).NotUpdatableReason.3=Result Set not updatable (references computed values or doesn't reference any columns or tables).NotUpdatableReason.4=Result Set not updatable (references no primary keys).NotUpdatableReason.5=Result Set not updatable (referenced table has no primary keys).NotUpdatableReason.6=Result Set not updatable (references unknown primary key {0}).NotUpdatableReason.7=Result Set not updatable (does not reference all primary keys).JDBC4Connection.ClientInfoNotImplemented=Configured clientInfoProvider class '{0}' does not implement com.mysql.jdbc.JDBC4ClientInfoProvider.InvalidLoadBalanceStrategy=Invalid load balancing strategy '{0}'.Connection.BadValueInServerVariables=Invalid value '{1}' for server variable named '{0}', falling back to sane default of '{2}'.LoadBalancingConnectionProxy.badValueForRetriesAllDown=Bad value '{0}' for property "retriesAllDown".LoadBalancingConnectionProxy.badValueForLoadBalanceBlacklistTimeout=Bad value '{0}' for property "loadBalanceBlacklistTimeout".Connection.UnableToConnect=Could not create connection to database server.Connection.UnableToConnectWithRetries=Could not create connection to database server. \Attempted reconnect {0} times. Giving up.Connection.UnexpectedException=Unexpected exception encountered during query.Connection.UnhandledExceptionDuringShutdown=Unexpected exception during server shutdown.## ConnectionProperty Categories#ConnectionProperties.categoryConnectionAuthentication=Connection/AuthenticationConnectionProperties.categoryNetworking=NetworkingConnectionProperties.categoryDebuggingProfiling=Debugging/ProfilingConnectionProperties.categorryHA=High Availability and ClusteringConnectionProperties.categoryMisc=MiscellaneousConnectionProperties.categoryPerformance=Performance ExtensionsConnectionProperties.categorySecurity=Security## ConnectionProperty Descriptions#ConnectionProperties.loadDataLocal=Should the driver allow use of 'LOAD DATA LOCAL INFILE...' (defaults to 'true').ConnectionProperties.allowMultiQueries=Allow the use of ';' to delimit multiple queries during one statement (true/false), defaults to 'false'ConnectionProperties.allowNANandINF=Should the driver allow NaN or +/- INF values in PreparedStatement.setDouble()?ConnectionProperties.allowUrlInLoadLocal=Should the driver allow URLs in 'LOAD DATA LOCAL INFILE' statements?ConnectionProperties.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 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.ConnectionProperties.autoClosePstmtStreams=Should the driver automatically call .close() on streams/readers passed as arguments via set*() methods?ConnectionProperties.autoDeserialize=Should the driver automatically detect and de-serialize objects stored in BLOB fields?ConnectionProperties.autoGenerateTestcaseScript=Should the driver dump the SQL it is executing, including server-side prepared statements to STDERR?ConnectionProperties.autoReconnect=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.ConnectionProperties.autoReconnectForPools=Use a reconnection strategy appropriate for connection pools (defaults to 'false')ConnectionProperties.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?ConnectionProperties.blobsAreStrings=Should the driver always treat BLOBs as Strings - specifically to work around dubious metadata returned by the server for GROUP BY clauses?ConnectionProperties.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?ConnectionProperties.blobSendChunkSize=Chunk to use when sending BLOB/CLOBs via ServerPreparedStatementsConnectionProperties.cacheCallableStatements=Should the driver cache the parsing stage of CallableStatementsConnectionProperties.cachePrepStmts=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?ConnectionProperties.cacheRSMetadata=Should the driver cache ResultSetMetaData for Statements and PreparedStatements? (Req. JDK-1.4+, true/false, default 'false')ConnectionProperties.cacheServerConfiguration=Should the driver cache the results of 'SHOW VARIABLES' and 'SHOW COLLATION' on a per-URL basis?ConnectionProperties.callableStmtCacheSize=If 'cacheCallableStmts' is enabled, how many callable statements should be cached?ConnectionProperties.capitalizeTypeNames=Capitalize type names in DatabaseMetaData? (usually only useful when using WebObjects, true/false, defaults to 'false')ConnectionProperties.characterEncoding=If 'useUnicode' is set to true, what character encoding should the driver use when dealing with strings? (defaults is to 'autodetect')ConnectionProperties.characterSetResults=Character set to tell the server to return results as.ConnectionProperties.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() methodsConnectionProperties.clobberStreamingResults=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.ConnectionProperties.clobCharacterEncoding=The character encoding to use for sending and retrieving TEXT, MEDIUMTEXT and LONGTEXT values instead of the configured connection characterEncodingConnectionProperties.compensateOnDuplicateKeyUpdateCounts=Should the driver compensate for the update counts of "ON DUPLICATE KEY" INSERT statements (2 = 1, 0 = 1) when using prepared statements?
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -