[V4RB] 3 simple [?] questions

[Ruslan Zasukhin]

on 2/26/03 6:01 PM, Keith DeLong at delong at redcort.com wrote:

> Hi Frank,
>> ...
>>> It's really much better to use cursors:
>>> 
>>> d.totalseconds = cursor.doublefield("MyDate").value
>>> cursor.add   //or cursor.update
>> 
>> ...
>> 
>> Short question: Why? What's wrong with BaseObject.AddRecord?
> 
> In my thinking there are two reasons:
> 
> First, it is a safety issue. All parsing or populating of a record happens
> at the cursor level apart from the actual base object. This allows me to
> spend as much time as required with the cursor without concern for the
> actual db should a crash or other unforeseen event occur. When I'm done with
> my record manipulation, an add or update then becomes a single interaction
> with the cursor actually writing to the table itself 'all at once'.
> 
> Second, for version 2 (with a client/server model), it's vital. Abstracting
> all db manipulation to cursors rather than direct access to the tables will
> make moving a project to a client/server model much, much easier.
> 
> Ruslan (or anyone else) please feel free to correct me if I'm wrong :)

You are right Keith.

Model of BaseObject and classes must be also expanded in V4RB in future, to
reach at least current c++ SDK. But again this model is great for local db,
not for remote db access.

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