1.1.1

ps.setAsciiStream(2, fin, fileLength);
ps.execute();
conn.commit();
java.sql.ResultSet Interface
Do not assume any implicit ordering of result set rows. If you require ordering, use an ORDER BY clause.
java.sql.SavePoint Class
This release of SQLFire does not support SavePoints.
java.sql.SQLException Class
SQLExceptions that are thrown by SQLFire do not always match the Exception that a Derby database would
throw. The getSQLState() method on SQLException may also return a different value in some cases.
java.sql.Statement Class
SQLFire does not implement the setEscapeProcessing method of java.sql.Statement. In addition,
the cancel method raises a "Feature not supported" exception.
ResultSet Objects
An error that occurs when a SELECT statement is first executed prevents a ResultSet object from being
opened on it. The same error does not close the ResultSet if it occurs after the ResultSet is opened. For
example, a divide-by-zero error that occurs while the executeQuery method is called on a
java.sql.Statement or java.sql.PreparedStatement throws an exception and returns no result
set at all, while if the same error occurs while the next method is called on a ResultSet object, it does not
close the result set.
Errors can occur when a ResultSet is first being created if the system partially executes the query before the
first row is fetched. This errors can occur on any query that uses more than one table and on queries that use
aggregates, GROUP BY, ORDER BY, DISTINCT, INTERSECT, EXCEPT, or UNION. (See SQL Language
Limitations on page 707.) Closing a Statement causes all open ResultSet objects on that statement to be
closed as well.The cursor name for the cursor of a ResultSet can be set before the statement is executed.
However, once it is executed, the cursor name cannot be altered.
javax.sql.XADataSource
This release of SQLFire does not support javax.sql.XADataSource.
363
JDBC API