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.
Default Value false Since Version 3.0.9
Should the driver allow conversions from empty string fields to numeric values of '0'?
Default Value true Since Version 3.1.8
Should the driver close result sets on Statement.close() as required by the JDBC specification?
Default Value false Since Version 3.1.7
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.
Default Value true Since Version 3.1.2
The maximum number of rows to return (0, the default means return all rows).
Default Value -1 Since Version all versions
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)
Default Value 600 Since Version 5.1.0
If a result set column has the CHAR type and the value does not fill the amount of characters specified in the DDL for the column, should the driver pad the remaining characters with space (for ANSI compliance)?
Default Value false Since Version 5.0.6
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.
Default Value false Since Version 5.0.5
Should the driver contradict the JDBC API and tolerate and support backward and absolute cursor movement on result sets of type 'ResultSet.TYPE_FORWARD_ONLY'?
Regardless of this setting, cursor-based and row streaming result sets cannot be navigated in the prohibited directions.
Default Value false Since Version 8.0.24
Should the driver do strict checking (all primary keys selected) of updatable result sets (true, false, defaults to 'true')?
Default Value true Since Version 3.0.4
Should the driver treat the datatype TINYINT(1) as the BIT type (because the server silently converts BIT -> TINYINT(1) when creating tables)?
Default Value true Since Version 3.0.16
If the driver converts TINYINT(1) to a different type, should it use BOOLEAN instead of BIT for future compatibility with MySQL-5.0, as MySQL-5.0 has a BIT type?
Default Value false Since Version 3.1.9