## Fixed#ResultSet.Retrieved__1=Retrieved ResultSet.Bad_format_for_BigDecimal=Bad format for BigDecimal ''{0}'' in column {1}.ResultSet.Bad_format_for_BigInteger=Bad format for BigInteger ''{0}'' in column {1}.ResultSet.Column_Index_out_of_range_low=Column Index out of range, {0} < 1.ResultSet.Column_Index_out_of_range_high=Column Index out of range, {0} > {1}. ResultSet.Value_is_out_of_range=Value ''{0}'' is out of range [{1}, {2}].ResultSet.Positioned_Update_not_supported=Positioned Update not supported.ResultSet.Bad_format_for_Date=Bad format for DATE ''{0}'' in column {1}.ResultSet.Bad_format_for_Column=Bad format for {0} ''{1}'' in column {2} ({3}).ResultSet.Bad_format_for_number=Bad format for number ''{0}'' in column {1}.ResultSet.Illegal_operation_on_empty_result_set=Illegal operation on empty result set.Statement.0=Connection is closed.Statement.2=Unsupported character encoding ''{0}''Statement.5=Illegal value for setFetchDirection().Statement.7=Illegal value for setFetchSize().Statement.11=Illegal value for setMaxFieldSize().Statement.13=Can not set max field size > max allowed packet of {0} bytes.Statement.15=setMaxRows() out of range. Statement.19=Illegal flag for getMoreResults(int).Statement.21=Illegal value for setQueryTimeout().Statement.27=Connection is read-only. Statement.28=Queries leading to data modification are not allowed.Statement.34=Connection is read-only. Statement.35=Queries leading to data modification are not allowed.Statement.40=Can not issue INSERT/UPDATE/DELETE with executeQuery().Statement.42=Connection is read-only. Statement.43=Queries leading to data modification are not allowed.Statement.46=Can not issue SELECT via executeUpdate().Statement.49=No operations allowed after statement closed.Statement.57=Can not issue data manipulation statements with executeQuery().Statement.59=Can not issue NULL query.Statement.61=Can not issue empty query.Statement.63=Statement not closed explicitly. You should call close() on createdStatement.64=Statement instances from your code to be more efficient.UpdatableResultSet.1=Can not call deleteRow() when on insert row.UpdatableResultSet.2=Can not call deleteRow() on empty result set.UpdatableResultSet.3=Before start of result set. Can not call deleteRow().UpdatableResultSet.4=After end of result set. Can not call deleteRow().UpdatableResultSet.7=Not on insert row.UpdatableResultSet.8=Can not call refreshRow() when on insert row.UpdatableResultSet.9=Can not call refreshRow() on empty result set.UpdatableResultSet.10=Before start of result set. Can not call refreshRow().UpdatableResultSet.11=After end of result set. Can not call refreshRow().UpdatableResultSet.12=refreshRow() called on row that has been deleted or had primary key changed.UpdatableResultSet.34=Updatable result set created, but never updated. You should only create updatable result sets when you want to update/insert/delete values using the updateRow(), deleteRow() and insertRow() methods.UpdatableResultSet.39=Unsupported character encoding ''{0}''.UpdatableResultSet.43=Can not create updatable result sets when there is no currently selected database and MySQL server version < 4.1.## Possible re-names#ResultSet.Query_generated_no_fields_for_ResultSet_57=Query generated no fields for ResultSetResultSet.Illegal_value_for_fetch_direction_64=Illegal value for fetch directionResultSet.Value_must_be_between_0_and_getMaxRows()_66=Value must be between 0 and getMaxRows()ResultSet.Query_generated_no_fields_for_ResultSet_99=Query generated no fields for ResultSetResultSet.Cannot_absolute_position_to_row_0_110=Cannot absolute position to row 0ResultSet.Operation_not_allowed_after_ResultSet_closed_144=Operation not allowed after ResultSet closedResultSet.Before_start_of_result_set_146=Before start of result setResultSet.After_end_of_result_set_148=After end of result setResultSet.Query_generated_no_fields_for_ResultSet_133=Query generated no fields for ResultSetResultSet.ResultSet_is_from_UPDATE._No_Data_115=ResultSet is from UPDATE. No Data.ResultSet.N/A_159=N/A## To fix#ResultSet.Invalid_value_for_getFloat()_-____68=Invalid value for getFloat() - \'ResultSet.Invalid_value_for_getInt()_-____74=Invalid value for getInt() - \'ResultSet.Invalid_value_for_getLong()_-____79=Invalid value for getLong() - \'ResultSet.Invalid_value_for_getFloat()_-____200=Invalid value for getFloat() - \'ResultSet.___in_column__201=\' in column ResultSet.Invalid_value_for_getInt()_-____206=Invalid value for getInt() - \'ResultSet.___in_column__207=\' in column ResultSet.Invalid_value_for_getLong()_-____211=Invalid value for getLong() - \'ResultSet.___in_column__212=\' in column ResultSet.Invalid_value_for_getShort()_-____217=Invalid value for getShort() - \'ResultSet.___in_column__218=\' in column ResultSet.Class_not_found___91=Class not found: ResultSet._while_reading_serialized_object_92=\ while reading serialized objectResultSet.Invalid_value_for_getShort()_-____96=Invalid value for getShort() - \'ResultSet.Unsupported_character_encoding____101=Unsupported character encoding \'ResultSet.Malformed_URL____104=Malformed URL \'ResultSet.Malformed_URL____107=Malformed URL \'ResultSet.Malformed_URL____141=Malformed URL \'ResultSet.Column____112=Column \'ResultSet.___not_found._113=\' not found.ResultSet.Unsupported_character_encoding____135=Unsupported character encoding \'ResultSet.Unsupported_character_encoding____138=Unsupported character encoding \'## Usage advisor messages for ResultSets#ResultSet.ResultSet_implicitly_closed_by_driver=ResultSet implicitly closed by driver.\n\nYou should close ResultSets explicitly from your code to free up resources in a more efficient manner.ResultSet.Possible_incomplete_traversal_of_result_set=Possible incomplete traversal of result set. Cursor was left on row {0} of {1} rows when it was closed.\n\nYou should consider re-formulating your query to return only the rows you are interested in using.ResultSet.The_following_columns_were_never_referenced=The following columns were part of the SELECT statement for this result set, but were never referenced: ResultSet.Too_Large_Result_Set=Result set size of {0} rows is larger than \"resultSetSizeThreshold\" of {1} rows. Application may be requesting more data than it is using. Consider reformulating the query.ResultSet.CostlyConversion=ResultSet type conversion via parsing detected when calling {0} for column {1} (column named '{2}') in table '{3}'{4}\n\nJava class of column type is '{5}', MySQL field type is '{6}'.\n\nTypes that could be converted directly without parsing are:\n{7}ResultSet.CostlyConversionCreatedFromQuery= created from query:\n\nResultSet.Value____173=Value \'ResultSetMetaData.46=Column index out of range.ResultSet.___is_out_of_range_[-127,127]_174=\' is out of range [-127,127]ResultSet.Bad_format_for_Date____180=Bad format for Date \'ResultSet.Timestamp_too_small_to_convert_to_Time_value_in_column__223=Timestamp too small to convert to Time value in column ResultSet.Precision_lost_converting_TIMESTAMP_to_Time_with_getTime()_on_column__227=Precision lost converting TIMESTAMP to Time with getTime() on column ResultSet.Precision_lost_converting_DATETIME_to_Time_with_getTime()_on_column__230=Precision lost converting DATETIME to Time with getTime() on column ResultSet.Bad_format_for_Time____233=Bad format for Time \'ResultSet.___in_column__234=\' in column ResultSet.Bad_format_for_Timestamp____244=Bad format for Timestamp \'ResultSet.___in_column__245=\' in column ResultSet.Cannot_convert_value____249=Cannot convert value \'ResultSet.___from_column__250=\' from column ResultSet._)_to_TIMESTAMP._252=\ ) to TIMESTAMP.ResultSet.Timestamp_too_small_to_convert_to_Time_value_in_column__257=Timestamp too small to convert to Time value in column ResultSet.Precision_lost_converting_TIMESTAMP_to_Time_with_getTime()_on_column__261=Precision lost converting TIMESTAMP to Time with getTime() on column ResultSet.Precision_lost_converting_DATETIME_to_Time_with_getTime()_on_column__264=Precision lost converting DATETIME to Time with getTime() on column ResultSet.Bad_format_for_Time____267=Bad format for Time \'ResultSet.___in_column__268=\' in column ResultSet.Bad_format_for_Timestamp____278=Bad format for Timestamp \'ResultSet.___in_column__279=\' in column ResultSet.Cannot_convert_value____283=Cannot convert value \'ResultSet.___from_column__284=\' from column ResultSet._)_to_TIMESTAMP._286=\ ) to TIMESTAMP.CallableStatement.2=Parameter name can not be NULL or zero-length.CallableStatement.3=No parameter named 'CallableStatement.4='CallableStatement.5=Parameter named 'CallableStatement.6=' is not an OUT parameterCallableStatement.7=No output parameters registered.CallableStatement.8=No output parameters returned by procedure.CallableStatement.9=Parameter number CallableStatement.10=\ is not an OUT parameterCallableStatement.11=Parameter index of CallableStatement.12=\ is out of range (1, CallableStatement.13=)CallableStatement.14=Can not use streaming result sets with callable statements that have output parametersCallableStatement.1=Unable to retrieve metadata for procedure.CallableStatement.0=Parameter name can not be CallableStatement.15=null.CallableStatement.16=empty.CallableStatement.21=Parameter CallableStatement.22=\ is not registered as an output parameterCommunicationsException.2=\ is longer than the server configured value of CommunicationsException.3='wait_timeout'CommunicationsException.4='interactive_timeout'CommunicationsException.5=may or may not be greater than the server-side timeout CommunicationsException.6=(the driver was unable to determine the value of either the CommunicationsException.7='wait_timeout' or 'interactive_timeout' configuration values from CommunicationsException.8=the server.CommunicationsException.9=The last communications with the server was CommunicationsException.10=\ seconds ago, which CommunicationsException.11=. You should consider either expiring and/or testing connection validity CommunicationsException.12=before use in your application, increasing the server configured values for client timeouts, CommunicationsException.13=or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.CommunicationsException.14=The driver was unable to create a connection due to CommunicationsException.15=an inability to establish the client portion of a socket.\n\nCommunicationsException.16=This is usually caused by a limit on the number of sockets imposed by CommunicationsException.17=the operating system. This limit is usually configurable. \n\nCommunicationsException.18=For Unix-based platforms, see the manual page for the 'ulimit' command. Kernel or system reconfiguration may also be required.CommunicationsException.19=\n\nFor Windows-based platforms, see Microsoft Knowledge Base Article 196271 (Q196271).CommunicationsException.19a=The configuration parameter \"localSocketAddress\" has been set to a network interface not available for use by the JVM.CommunicationsException.20=Communications link failureCommunicationsException.21=\ due to underlying exception: CommunicationsException.ClientWasStreaming=Application was streaming results when the connection failed. Consider raising value of 'net_write_timeout' on the server.NonRegisteringDriver.3=Hostname of MySQL ServerNonRegisteringDriver.7=Port number of MySQL ServerNonRegisteringDriver.13=Username to authenticate asNonRegisteringDriver.16=Password to use for authenticationNonRegisteringDriver.17=Cannot load connection class because of underlying exception: 'NonRegisteringDriver.18='.NonRegisteringDriver.37=Must specify port after ':' in connection stringSQLError.35=Disconnect errorSQLError.36=Data truncatedSQLError.37=Privilege not revokedSQLError.38=Invalid connection string attributeSQLError.39=Error in rowSQLError.40=No rows updated or deletedSQLError.41=More than one row updated or deletedSQLError.42=Wrong number of parametersSQLError.43=Unable to connect to data sourceSQLError.44=Connection in useSQLError.45=Connection not openSQLError.46=Data source rejected establishment of connectionSQLError.47=Connection failure during transactionSQLError.48=Communication link failureSQLError.49=Insert value list does not match column listSQLError.50=Numeric value out of rangeSQLError.51=Datetime field overflowSQLError.52=Division by zeroSQLError.53=Deadlock found when trying to get lock; Try restarting transactionSQLError.54=Invalid authorization specificationSQLError.55=Syntax error or access violationSQLError.56=Base table or view not foundSQLError.57=Base table or view already existsSQLError.58=Base table not foundSQLError.59=Index already exists