[SQL] Client and server cursors // "deferred" ClientSide

[Ruslan Zasukhin]

on 3/5/03 3:49 AM, Andreas Grosam at agrosam at computerworks.ch wrote:

>>    curs = db.SqlSelect( "SELECT ...", ReadWrite, kClient )
> 
> Regarding Client versus Serve Side Cursor:

> Defaults to a third version, which first manages the resources on the server
> side - once fetched, they become onwed by the client and the server
> immediately releases the fetched rows.

Similar to mySQL's FETCH by one record, yes?

> This may be called "defered" ClientSide Cursor. Combines several advantages at
> low cost. 

I have also another idea.

Client Cursor load all data, Server kill main resources of server TMP
cursor, but to be able now UPDATE that client cursor is created proxy -
object of VDK_Cursor which do not keep recourse, but just talk to client
cursor and update records.

In the same time, CLIENT object on Server, still keep records locked.
Well, yes, locks and time of unlock are defined by Isolation level.


-- 
Best regards,
Ruslan Zasukhin      [ I feel the need...the need for speed ]
-------------------------------------------------------------
e-mail: ruslan at paradigmasoft.com
web: http://www.paradigmasoft.com

To subscribe to the Valentina mail list go to:
http://listserv.macserve.net/mailman/listinfo/valentina
-------------------------------------------------------------