NDB Cluster APIs: Incorrect results, usually an empty result set, were returned when
setBound()
was used to specify aNULL
bound. This issue appears to have been caused by a problem in gcc, limited to cases using the old version of this method (which does not employNdbRecord
), and is fixed by rewriting the problematic internal logic in the old implementation. (Bug #89468, Bug #27461752)-
Queries using very large lists with
IN
were not handled correctly, which could lead to data node failures. (Bug #27397802)References: See also: Bug #28728603.
ndb_restore
--print-data
--hex
did not print trailing 0s ofLONGVARBINARY
values. (Bug #65560, Bug #14198580)