Add initialization in StringMatchingFilterObj class
In order to support LIKE statement filter in OVO objects,
StringMatchingFilterObj class is introduced. However, this class
does not provide initial attributes of "starts", "contains" and
"ends".
In real usage, if these attributes are not initialized, we will
hit failures in method apply_filters() in db/_model_query.py.
This patch adds the initialization back.
Secondly, a typo of "obj_utils.StringMatchingContains" is revised
in this patch too.
Reviewed: https:/ /review. openstack. org/512944 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=28e8265651d a2aad1d253f3a47 c0e71525dd5e1b
Committed: https:/
Submitter: Zuul
Branch: master
commit 28e8265651da2aa d1d253f3a47c0e7 1525dd5e1b
Author: Lujin <email address hidden>
Date: Wed Oct 18 15:09:37 2017 +0900
Add initialization in StringMatchingF ilterObj class
In order to support LIKE statement filter in OVO objects, ingFilterObj class is introduced. However, this class
StringMatch
does not provide initial attributes of "starts", "contains" and
"ends".
In real usage, if these attributes are not initialized, we will
hit failures in method apply_filters() in db/_model_query.py.
This patch adds the initialization back.
Secondly, a typo of "obj_utils. StringMatchingC ontains" is revised
in this patch too.
Change-Id: If828068d8d08ff 09dff6c63d53320 bc397d32448
Closes-Bug: #1724446