Java Doc for ResultSetTest.java in  » Database-JDBC-Connection-Pool » jTDS » net » sourceforge » jtds » test » Java Source Code / Java DocumentationJava Source Code and Java Documentation

1. isNullable() always returns columnNoNulls.

This illustrates the logic added to fix:

1. [1323363] Deadlock Exception not reported (SQL Server)
2. [1283472] Unable to cancel statement with cursor resultset

Assertions tested:

• The current row is always the first row returned by the last fetch, regardless of what fetch type was used.
• Row number parameter is ignored by fetch types other than absolute and relative.
• Refresh fetch type simply reruns the previous request (it ignores both row number and number of rows) and will not affect the current row.
• Fetch next returns the packet of rows right after the last row returned by the last fetch (regardless of what type of fetch that was).
• Fetch previous returns the packet of rows right before the first row returned by the last fetch (regardless of what type of fetch that was).
• If a fetch previous tries to read before the start of the ResultSet the requested number of rows is returned, starting with row 1 and the error code returned is non-zero (2).

Previously jTDS was not able to close a ResultSet/Statement/Connection after an OutOfMemoryError because the input stream pointer usually remained inside a packet and further attempts to dump the rest of the response failed because of "protocol confusions".

1. isNullable() always returns columnNoNulls.
2. isSigned returns true in error for TINYINT columns.
3. Type names for numeric / decimal have (prec,scale) appended in error.
4. Type names for auto increment columns do not have "identity" appended.

Conversion of float values to String adds grouping to the value, which cannot then be parsed.