Added to Query.search method & tests

[wearp]

to resolve #32

[eugene-eeo]

I think it's better to do getattr(re, self.re_method) or use different classes entirely, like QueryRegexSearch. Such conditionals should typically be avoided since they cause problems and repetition.

[msiemens]

since they cause problems and repetition.

I don't think using getattr is any better. Easiest solution I can see would be to pass the actual function as re_method, e.g:

return QueryRegex(self._key, regex, re_method=re.match)

[eugene-eeo]

If we do that, then it is just a Query.test with a different constructor.

[msiemens]

Is there a problem with that?

[eugene-eeo]

Not saying that it's a problem, just that the repr wouldn't update properly.

[msiemens]

Hmm... In any case match and search should produce different reprs as a query's hash value is calculated from it (needed when using queries as dict keys, see query caching). Otherwise this may happen:

>>> d = {
    where('key').matches('asd'): [...]
}
>>> where('key').search('asd') in d
True

[msiemens]

I'll merge this PR, but we should fix the repr problem before releasing the next version of TinyDB.

EDIT: Calculating the hash of a QueryRegex is broken even without this patch. Will work on it.

[msiemens]

Mentined problems are fixed in 20d245c