[SQL] Client and server cursors

[Ruslan Zasukhin]

on 3/5/03 2:24 AM, john roberts at jarobe01 at athena.louisville.edu wrote:

>> What we try now implement for Valentina is ability to use the SAME cursor
>> API, that we use for local dbs.
>> 
>> So this looks as
>> 
>> curs = db.SqlSelect( "SELECT ...", ReadWrite, kClient )
>> 
>> Now if you want do modifications of records you can do simply:
>> 
>> curs.Stringfield( "name" ) = 'something new'
>> curs.Update();  <<<<<<<< this send command to server.
>> 
>> €€>> What you think about this approach ?
>> €€>> Anybody see any potential problems with this ?
>> **>> I do not remember if any other db use this way? IT seems I have see
>> always generation of new SQL command in background...
> 
> I presume this means that only changes are written back to the database.
> If so, it is neat and clean. I like that.

Yes, if cursor have 10 fields, but you change only 3 then only this 3 values
go to server by network.


In fact the same you get with update command

    UPDATE T SET f3 = 5, f6 = 6, f8 = 8

-- 
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
-------------------------------------------------------------