Bug #18190 Wrong value returned by NdbRecAtt::isNull()
Submitted: 13 Mar 2006 14:25 Modified: 20 Aug 2007 11:25
Reporter: Hartmut Holzgraefe Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.0.19 OS:Linux (linux)
Assigned to: Jon Stephens CPU Architecture:Any
Tags: ndb api, NdbRecAttr

[13 Mar 2006 14:25] Hartmut Holzgraefe
The return value of NdbRecAttr::isNull() method should be (extract from doc)
-1 = Not defined (Failure or NdbTransaction::execute not yet called)
0 = Attribute value is defined, but not equal to NULL.<br>
1 = Attribute value is defined and equal to NULL.

But a call to
   NdbOperation::getValue(...), isNull() 
on the NdbRecAttr returned give 0 although execute() hasn't been called yet.

How to repeat:
see attached test program csc8750.tar.gz
[13 Mar 2006 14:27] Hartmut Holzgraefe
test project

Attachment: csc8750.tar.gz (application/x-gunzip, text), 127.32 KiB.

[14 Mar 2006 15:11] Jonas Oreland

I would say that the documentation is wrong.

isNULL will return unspecified value if called before execute.

Is this ok, or a big limitation?

[14 Apr 2006 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[20 Aug 2007 11:25] Jon Stephens
Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.