forUpdate flag

[Joakim Schramm]

>  
> > 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
> 
Yes, but why do I want to have NULL fields? Why not just "" or 0 etc.? My
problem not getting this maybe have to do with me coming from VB were as an
example a variable doesn't have to be initialized before use. In such case I
could see a benefit in being able to test for NULL to see if value been set
once (if so to 0) but we can't do this in VB. Is it what it's about?

Joakim
> --
> 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]
> 
> 
> _______________________________________________
> Valentina mailing list
> Valentina at lists.macserve.net
> http://lists.macserve.net/mailman/listinfo/valentina
>