Performance metrics - some early conclusions

[Ruslan Zasukhin]

On 11/30/05 5:33 PM, "Ed Kleban" <Ed at Kleban.com> wrote:

> I don't fully understand what  forAdd does however.   I presume that it
> prevents the SetBlank method from writing the memory buffer values back to
> the current table record, but:

> 1) Why should SetBlank do this at all?  Should the user just use
> UpdateRecord if he wants that done?

I can wish

    t.SetBlank
    t.UpdateRecord()


So on default SetBlank() MUST make copies of old values.
 
> 2) If no memory fields have been modified does use of forAdd provide any
> savings?

SetBlank() itslef ALWAYS copy all and each old values BEFORE you start write
new
 
So answer is: number of dirty fields DOES NOT affect

> 3) If no records have yet been allocated does use of forAdd provide any
> savings?

But you have some current record...

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