SetBlank with inAccess = EvValueAccess.forAdd

[Ruslan Zasukhin]

On 11/28/05 7:58 PM, "Ed Kleban" <Ed at Kleban.com> wrote:

Hi Ed,

> I'm having a bit of difficulty understanding the following paragraph under
> "SetBlank":
> 
> " Parameter inAccess can be used to speed up SetBlank() if you add records.
> In this case  you can specify its value forAdd, so Valentina will not save
> copies of previouse field values. In the same time you can always use the
> default value forUpdate and everyhting will work correctly. "

> Does this mean that when you use SetBlank with forUpdate instead of with
> forAdd, that it always writes the current value of every field in the buffer
> to the current record before setting all fields to blank values?

Yes. So this is overhead.

I have idea how to improve this to drop down overhead to zero.
If success, then this parameter will be deprecated.

For now it exists.
 
> Or is it clever enough to only write out field values that have changed?

Yes we put on disk only dirty fields
 
> I would think that unless the user issues an explicit "Table.UpdateRecord()"
> call that they should not expect modified field values to be transferred to
> the table record.  Or is the default value of forUpdate intended to be a
> "convenience" so that users don't have to remember to call
> "Table.UpdateRecord()"?
> 
> Somehow I think I'm missing something here.

-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]