Bug#24568, NdbScanFilter NAND/NOR operations sometimes do not works as expected

this patch is an absolutely necessary supplement of the previous patch,
the previous patch doesnot cover isnull() and isnotnull() methods' effect.
parent 72f91a02
...@@ -328,11 +328,17 @@ NdbScanFilterImpl::cond_col(Interpreter::UnaryCondition op, Uint32 AttrId){ ...@@ -328,11 +328,17 @@ NdbScanFilterImpl::cond_col(Interpreter::UnaryCondition op, Uint32 AttrId){
int int
NdbScanFilter::isnull(int AttrId){ NdbScanFilter::isnull(int AttrId){
if(m_impl.m_negative == 1)
return m_impl.cond_col(Interpreter::IS_NOT_NULL, AttrId);
else
return m_impl.cond_col(Interpreter::IS_NULL, AttrId); return m_impl.cond_col(Interpreter::IS_NULL, AttrId);
} }
int int
NdbScanFilter::isnotnull(int AttrId){ NdbScanFilter::isnotnull(int AttrId){
if(m_impl.m_negative == 1)
return m_impl.cond_col(Interpreter::IS_NULL, AttrId);
else
return m_impl.cond_col(Interpreter::IS_NOT_NULL, AttrId); return m_impl.cond_col(Interpreter::IS_NOT_NULL, AttrId);
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment