W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2009

Resending Re: WebDatabase review: SQLResultSetRowList

From: Nikunj R. Mehta <nikunj.mehta@oracle.com>
Date: Mon, 21 Sep 2009 10:33:32 -0700
Message-Id: <46E99CE7-68F4-4FE3-ACB0-8CE4966E7C55@oracle.com>
To: Web Applications Working Group WG <public-webapps@w3.org>
I haven't seen any responses to the issues below. I hope the editors  
can respond to these and several other of my messages about the  
WebDatabase draft.

On Aug 31, 2009, at 3:56 PM, Nikunj R. Mehta wrote:
> SQLResultSetRowList
> The item() method may take a long time to process.  Shouldn't this  
> have an asynchronous version with a callback?
> The ability to randomly access rows in the row set increases the  
> likelihood that the item operation will take an arbitrarily long  
> time. Plus, supporting random access is very expensive on limited  
> memory devices.
> Offer next() and previous() methods that returns the next and  
> previous row respectively.
> Offer absolute() and relative() call that may fail.  See  
> java.sql.ResultSet.absolute() and java.sql.ResultSet.relative().
> The length attribute could require accessing all the rows, which  
> would use too much memory on limited memory devices.
> Specify that the SQLResultSetRowList that resulted from a call to  
> SQLTransaction.executeSql() can only be accessed during the  
> execution of the associated SQLStatementCallback
> Property names on result sets are based on column names used in the  
> query or defined in the view/table. These name sources (colmns,  
> selections) are case insensitive but the row object would have to  
> use case-sensitive names. Is there a way that objects can be  
> accessed without case insensitivity?

Received on Monday, 21 September 2009 17:36:49 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:18 UTC