niphlod / pydal

79%

master: 54%

LAST BUILD ON BRANCH fix/like_escaping

branch: SELECT

CHANGE BRANCH

x

• No branch selected
• coverage
• enhancement/README
• enhancement/READMEv2
• enhancement/coverage
• enhancement/coveralls
• enhancement/docs
• enhancement/repr_cache
• enhancement/tests_with_travis_docker
• fix/820
• fix/close_on_tests
• fix/coveralls
• fix/drivers
• fix/like_escaping
• fix/mssql_substrings
• master
• tests/appveyor
• v15.02
• v15.02.27
• v15.03
• v15.05.29

Build # 108

Build Type

push

travis-ci

Committed by niphlod

Commit Message

fixes a few intricacies properly escaping LIKE statements

specifically, we used like with startswith and endswith, and contains,
improperly. We need correct (and "automagic") escaping when dealing with
those "pythonic" methods, else subtle bugs creep in.
As always, "like()" and "ilike()" maps to the exact statement in the
backend,with the usual behaviour.
like() and ilike() got also a new "escape" parameter in order to pass
whatever escaping character the user feel right. By default, the escape
character is `\`, and the term passed to the like is escaped with it.

well, it's been fun. 1st absolute time that a feature gets backported
from mssql to all t-sql backends. As usual, NoSQL is out of my reach,
and left as an exercise to the ones more well-versed into the matter.

Coverage Stats

247 of 313 relevant lines covered (78.91%)

10551.19 hits per line