Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Compobj and .null.
Message
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Versions des environnements
Visual FoxPro:
VFP 5
Divers
Thread ID:
01197380
Message ID:
01197397
Vues:
22
>>Yes, NULL can't be compared. NULL is just "Don't know" If you want to compare NULLs use NVL() function:
>>
>>? NVL(oLeft.FieldWithNull,0)  == NVL(oRight.FieldWithNull,0)  && If FieldWithNull is some of the numeric fields
>>? NVL(oLeft.FieldWithNull,[]) == NVL(oRight.FieldWithNull,[]) && If FieldWithNull is char
>>? NVL(oLeft.FieldWithNull,{}) == NVL(oRight.FieldWithNull,{}) && If FieldWithNull is date
>>
>
>No I don't want to compare each field seperately, but now I understand why the my comparison results in null. Thanks.

As I said, this of NULLs as VFP (or any other language) way to say to you "I don't know". You can't compare this. The result always will be "I don't know":
"I don't know" == 1 -> I don't know :-)
Against Stupidity the Gods themselves Contend in Vain - Johann Christoph Friedrich von Schiller
The only thing normal about database guys is their tables.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform