Re: [patch] [doc] updatable ResultSets

20 Apr 2005 23:15:30 -0000 

Hey Mamta,

I have made the change you requested.  Ignore the
patch I posted previously and use this one instead.  
I am also attaching the html files so you can see how
they look.


--- Mamta Satoor <[EMAIL PROTECTED]> wrote:
> Hi Brenda,
> 
> The doc looks good. Just one change - in the Table
> for JDBC 2.0
> ResultSet Methods Supported, for the method void
> updateRow(), we need
> comments similar to the ones for deleteRow. Which is
> as follows
> void updateRow() After the row is updated, 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.
> 
> thanks,
> Mamta
> 
> 
> > java.sql.ResultSet
> > Table 1. JDBC 2.0 ResultSet Methods Supported
> > ReturnsSignatureImplementation Notes
> > voidafterLast() 
> > voidbeforeFirst() 
> > voidbeforeFirst() 
> > voiddeleteRow()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.
> > booleanfirst() 
> > BlobgetBlob(int columnIndex)See java.sql.Blob and
> java.sql.Clob
> > BlobgetBlob(String column-Name)
> > ClobgetClob(int columnIndex)
> > ClobgetClob(String column-Name)
> > intgetConcurrency()
> > 
> > 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.
> > intgetFetchDirection() 
> > intgetFetchSize()Always returns 1.
> > intgetRow() 
> > booleanisAfterLast() 
> > booleanisBeforeFirst 
> > booleanisFirst() 
> > booleanisLast() 
> > booleanlast() 
> > booleanprevious() 
> > booleanrelative(int rows) 
> > voidsetFetchDirection(int direction) 
> > voidsetFetchSize(int rows)A fetch size of 1 is the
> only size supported.
> > voidupdateRow()
> 

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Attachment: resultsets_changes.diff
Description: resultsets_changes.diff

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:

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() 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.
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

Reply via email to