Bug #37672 NDBAPI : NdbRecord option OO_ANYVALUE causes interpreted delete to abort.

Description:
When an ANYVALUE opeation option is used with an interpreted delete, the transaction aborts. 

How to repeat:
Create an NdbRecord interpreted delete with an ANYVALUE option provided.  When the delete is executed, the transaction will abort

Suggested fix:
Modify NdbRecord code handling OO_ANYVALUE to pass AnyValue as initial read for delete rather than as Final update.

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/49012

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/50876

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/50915

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/50916

Need complete version numbers in which fix will appear in order to document. Thanks.

Pushed to 6.2.16, 6.3.17 and 6.4.0

Documented bugfix in the ndb-6.2.16 and ndb-6.3.17 changelogs as follows:

        Executing an NdbRecord interpreted delete created with an ANYVALUE
        option caused the transaction to abort.

Pushed into 6.0.6-alpha  (revid:frazer@mysql.com-20080804154901-r9ijzndg9p62b0uy) (version source revid:jonas@mysql.com-20080812185642-1nevjb94zj621dqx) (pib:5)