Skip to content
Permalink
Browse files

docs: add note on behavior of ResultSet.getString() (#1286) (#1528)

* docs: add note on behavior of ResultSet.getString() (#1286)

* docs: revise note on behavior of ResultSet.getString() (#1286)

revision based on comment by @bokken
  • Loading branch information...
mshajarrazip authored and davecramer committed Jul 19, 2019
1 parent aa8778d commit c30556c6c059f25d4ed43608d1b2a2f02a168389
Showing with 11 additions and 1 deletion.
  1. +11 −1 docs/documentation/94/resultset.md
@@ -16,4 +16,14 @@ The following must be considered when using the `ResultSet` interface:
* You must close a `ResultSet` by calling `close()` once you have finished using
it.
* Once you make another query with the `Statement` used to create a `ResultSet`,
the currently open `ResultSet` instance is closed automatically.
the currently open `ResultSet` instance is closed automatically.
* When PreparedStatement API is used, `ResultSet` switches to binary mode after
five query executions (this default is set by the `prepareThreshold`
connection property, see [Server Prepared Statements](server-prepare.md)).
This may cause unexpected behavior when some methods are called. For example,
results on method calls such as `getString()` on non-string data types,
while logically equivalent, may be formatted differently after execution exceeds
the set `prepareThreshold` when conversion to object method switches to one
matching the return mode.


0 comments on commit c30556c

Please sign in to comment.
You can’t perform that action at this time.