Re: [patch] [doc] updatable ResultSets

[Brenda Reyes]

Hey Mamta,

The files you requested are attached.


--- Mamta Satoor <[EMAIL PROTECTED]> wrote:
> Hi Brenda,
> 
> Can you please send the html files for 3 pages? It
> will be easier to
> review those than the diff file.
> 
> thanks,
> Mamta
> 


                
__________________________________ 
Do you Yahoo!? 
Make Yahoo! your home page 
http://www.yahoo.com/r/hs

Title: column-Name

column-Name In many places in the SQL syntax, you can represent the name of a column by qualifying it with a table-Name or correlation-Name. In some situations, you cannot qualify a column-Name with a table-Name or a correlation-Name, but must use a Simple-column-Name instead. Those situations are: creating a table (CREATE TABLE statement) specifying updatable columns in a cursor in a column's correlation name in a SELECT _expression_ (see SelectExpression) in a column's correlation name in a TableExpression (see TableExpression) You cannot use correlation-Names for updatable columns; using correlation-Names in this way will cause an SQL exception. For example: SELECT c11 AS col1, c12 AS col2, c13 FROM t1 FOR UPDATE of c11,c13 In this example, the correlation-Name col1 FOR c11 is not permitted because c11 is listed in the FOR UPDATE list of columns. You can use the correlation-Name FOR c12 because it is not in the FOR UPDATE list. Syntax [ { table-Name | correlation-Name } . ] SQL92Identifier Example -- C.Country is a column-Name qualified with a -- correlation-Name. SELECT C.Country FROM APP.Countries C Parent topic: SQL identifiers

Title: correlation-Name

correlation-Name A correlation-Name is given to a table _expression_ in a FROM clause as a new name or alias for that table. You do not qualify a correlation-Name with a schema-Name. You cannot use correlation-Names for updatable columns; using correlation-Names in this way will cause an SQL exception. For example: SELECT c11 AS col1, c12 AS col2, c13 FROM t1 FOR UPDATE of c11,c13 In this example, the correlation-Name col1 FOR c11 is not permitted because c11 is listed in the FOR UPDATE list of columns. You can use the correlation-Name FOR c12 because it is not in the FOR UPDATE list. Syntax SQL92Identifier Example -- C is a correlation-Name SELECT C.NAME FROM SAMP.STAFF C Parent topic: SQL identifiers

Title: java.sql.ResultSet

java.sql.ResultSet Table 1. JDBC 2.0 ResultSet Methods Supported Returns Signature Implementation Notes void afterLast()   void beforeFirst()   void beforeFirst()   void deleteRow() After the row is deleted, the ResultSet object will be positioned before the next row. Before issuing any methods other than close on the ResultSet object, the program will need to reposition the ResultSet object by using the next() method. boolean first()   Blob getBlob(int columnIndex) See java.sql.Blob and java.sql.Clob Blob getBlob(String column-Name) Clob getClob(int columnIndex) Clob getClob(String column-Name) int getConcurrency() If the Statement object has CONCUR_READ_ONLY concurrency, then this method will return ResultSet.CONCUR_READ_ONLY. But if the Statement object has CONCUR_UPDATABLE concurrency, then the return value will depend on whether the underlying language ResultSet is updatable or not. If the language ResultSet is updatable, then getConcurrency() will return ResultSet.CONCUR_UPDATABLE. If the language ResultSet is not updatable, then getConcurrency() will return ResultSet.CONCUR_READ_ONLY. int getFetchDirection()   int getFetchSize() Always returns 1. int getRow()   boolean isAfterLast()   boolean isBeforeFirst   boolean isFirst()   boolean isLast()   boolean last()   boolean previous()   boolean relative(int rows)   void setFetchDirection(int direction)   void setFetchSize(int rows) A fetch size of 1 is the only size supported. void updateRow()   Note: When working with scrolling insensitive ResultSets when auto-commit mode is turned on, the only positioning method that can close the ResultSet automatically is the next() method. When auto-commit mode is on, this method automatically closes the ResultSet if it is called and there are no more rows. afterLast() does not close the ResultSet, for example. JDBC is not required to have auto-commit off when using updatable ResultSets. At this moment, Derby does not support the insertRow() method for updatable ResultSets. Parent topic: JDBC Reference