6.3.7 Prepared Statements

• allowNanAndInf

  Should the driver allow NaN or +/- INF values in 'PreparedStatement.setDouble()'?

  Default Value	false
  Since Version	3.1.5

• autoClosePStmtStreams

  Should the driver automatically call the method 'close()' on streams/readers passed as arguments via 'set*()' methods?

  Default Value	false
  Since Version	3.1.12

• compensateOnDuplicateKeyUpdateCounts

  Should the driver compensate for the update counts of "INSERT ... ON DUPLICATE KEY UPDATE" statements (2 = 1, 0 = 1) when using prepared statements?

  Default Value	false
  Since Version	5.1.7

• emulateUnsupportedPstmts

  Should the driver detect prepared statements that are not supported by the server, and replace them with client-side emulated versions?

  Default Value	true
  Since Version	3.1.7

• generateSimpleParameterMetadata

  Should the driver generate simplified parameter metadata for prepared statements when no metadata is available either because the server couldn't support preparing the statement, or server-side prepared statements are disabled?

  Default Value	false
  Since Version	5.0.5

• processEscapeCodesForPrepStmts

  Should the driver process escape codes in queries that are prepared? Default escape processing behavior in non-prepared statements must be defined with the property 'enableEscapeProcessing'.

  Default Value	true
  Since Version	3.1.12

• useServerPrepStmts

  Use server-side prepared statements if the server supports them? The server may limit the number of prepared statements with 'max_prepared_stmt_count' or disable them altogether. In case of not being possible to prepare new server-side prepared statements, it depends on the value of 'emulateUnsupportedPstmts' to whether return an error or fall back to client-side emulated prepared statements.

  Default Value	false
  Since Version	3.1.0

• useStreamLengthsInPrepStmts

  Honor stream length parameter in 'PreparedStatement/ResultSet.set*Stream()' method calls?

  Default Value	true
  Since Version	3.0.2