forUpdate flag

[Ruslan Zasukhin]

On 6/28/06 11:30 PM, "Joakim Schramm" <joakim at astrocalc.com> wrote:

Hi Joakim,

> I wonder a bit about the inAccess forUpdate flag, is there any benefit in
> blanking the RAM buffer when updating a record compared to NOT doing it when
> updating a record and some values may have changed while others stays the
> same? Like if I set values to all field although some may be the same as
> already there (which I of course have to do if I Blank the record)?

If you blank record, then you need setup back all fields.
Usually IF you do update you change only few fields.
Usually you do not use SetBlank() + Update.
 
> Or in another scenario if I know just 1 or 2 fields have changed, any
> difference if I just set new values to this 2 fields or if I "SetBlank
> forUpdate" and fill all fields with fresh values (although I may not have
> to)?

Wrong. All you need is

    table.goto

    f1 = 
    f2 = 

    table.update
 
> Another question about Nullable fields, are there any Pro/Cons or special
> benefit of having nullable fields? I know they add 1 bit to each record, but
> do I "save" something for those fileds that are NULL compared to those
> having a value?

Rule is simple: 
    IF you need keep NULL values or this field
    you make it Nullable. Otherwise do not make it nullable

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