MySQL Bugs: #35876: NDBAPI : Old Api scan with no bounds incorrectly handled

Bug #35876	NDBAPI : Old Api scan with no bounds incorrectly handled
Submitted:	7 Apr 13:46	Modified:	9 Jul 11:03
Reporter:	Frazer Clement
Status:	Closed
Category:	Server: NDBAPI	Severity:	S3 (Non-critical)
Version:	5.1-telco-6.3+	OS:	Any
Assigned to:	Frazer Clement	Target Version:

Description:
When creating an 'old' Api index scan, if no bounds are specified, some work is still done
internally creating a bound.
This could have various unwanted side-effects and should be fixed.

How to repeat:
1) Create old Api scan using NdbTransaction::getNdbIndexScanOperation(),
NdbIndexScanOperation::readTuples(), NdbIndexScanOperation::getValue() etc, but no calls
to NdbIndexScanOperation::setBound()

2a) Call NdbTransaction.execute() and observe flow of control.

or

2b) Call NdbTransaction.execute() and after the scan is finalised, check the value of
m_num_bounds.  It should be zero, it will be 1.

Suggested fix:
Pass a NULL IndexBound* to NdbScanOperation::scanIndexImpl() when no bound has been set by
an old Api scan

and / or

setBound() should handle the case where no bounds are set within an IndexBound object
specifically.

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/46032

ChangeSet@1.2588, 2008-04-25 16:12:47+01:00, frazer@forth.ndb.mysql.com +2 -0
  Bug # 35876 NDBAPI : Old Api scan with no bounds incorrectly handled
  
  Changes :
   - An IndexBound which has neither an upper or lower bound is rejected with new error
code
   - For old Api scans, when no bounds are set, we do not pass a bound into the scan.

Pushed into 5.1.23-ndb-6.4.0

Pushed into 5.1.24-ndb-6.3.13

Pushed into 5.1.24-ndb-6.2.14

Documented bugfix in the 5.1.23-6.2.14 and 5.1.24-ndb-6.3.13 changelogs as follows:

        Scans having no bounds set were handled incorrectly.

Closed.