suffix. .between(low, high) Search for values between low and high. .regexp(exp) Regular expression match. .bin_and(value) Binary AND. .bin_or(value) Binary OR. .in_(value) IN lookup (identical to <<) where(DocumentIndex.match(phrase)) .order_by(DocumentIndex.bm25())) Warning: All SQL queries on FTSModel classes will be slow except full-text searches and docid lookups. Continued examples: # Use the "match" operation .select() .where(DocumentIndex.match('some query'))) # To sort by best match, use the custom "rank" function. best = (DocumentIndex .select() .where(DocumentIndex.match('some query')) .order_by(DocumentIndex

suffix. .between(low, high) Search for values between low and high. .regexp(exp) Regular expression match. .bin_and(value) Binary AND. .bin_or(value) Binary OR. .in_(value) IN lookup (identical to <<) DocumentIndex, on=(Document.id == DocumentIndex.docid)) .where(DocumentIndex.match(phrase)) .order_by(DocumentIndex.bm25())) Warning All SQL queries on FTSModel classes # Use the "match" operation for FTS queries. matching_docs = (DocumentIndex .select() .where(DocumentIndex.match('some query'))) # To sort by best match, use the custom

one owner, so when we performed the join from Pet to Person, there was always going to be a single match. The situation is different when we are joining from Person to Pet because a person may have zero Search for values between low and high. .regexp(exp) Regular expression match (case-sensitive). .iregexp(exp) Regular expression match (case-insensitive). .bin_and(value) Binary AND. .bin_or(value) Binary native datetime data-type). The default supported formats are: Note If the incoming value does not match a format, it is returned as-is. '%Y-%m-%d %H:%M:%S.%f' # year-month-day hour-minute- second.microsecond

one owner, so when we performed the join from Pet to Person, there was always going to be a single match. The situation is different when we are joining from Person to Pet because a person may have zero Search for values between low and high. .regexp(exp) Regular expression match (case-sensitive). .iregexp(exp) Regular expression match (case-insensitive). .bin_and(value) Binary AND. .bin_or(value) Binary native datetime data-type). The default supported formats are: Note If the incoming value does not match a format, it is returned as-is. '%Y-%m-%d %H:%M:%S.%f' # year-month-day hour-minute- second.microsecond

one owner, so when we performed the join from Pet to Person, there was always going to be a single match. The situation is different when we are joining from Person to Pet because a person may have zero Search for values between low and high. .regexp(exp) Regular expression match (case-sensitive). .iregexp(exp) Regular expression match (case-insensitive). .bin_and(value) Binary AND. .bin_or(value) Binary native datetime data-type). The default supported formats are: Note: If the incoming value does not match a format, it is returned as-is. '%Y-%m-%d %H:%M:%S.%f' # year-month-day hour-minute-second.microsecond

one owner, so when we performed the join from Pet to Person, there was always going to be a single match. The situation is different when we are joining from Person to Pet because a person may have zero Search for values between low and high. .regexp(exp) Regular expression match (case-sensitive). .iregexp(exp) Regular expression match (case-insensitive). .bin_and(value) Binary AND. .bin_or(value) Binary 154 Chapter 1. Contents: peewee Documentation, Release 3.4.0 Note: If the incoming value does not match a format, it is returned as-is. '%Y-%m-%d %H:%M:%S.%f' # year-month-day hour-minute-second.microsecond

one owner, so when we performed the join from Pet to Person, there was always going to be a single match. The situation is different when we are joining from Person to Pet because a person may have zero suffix. .between(low, high) Search for values between low and high. .regexp(exp) Regular expression match. .bin_and(value) Binary AND. .bin_or(value) Binary OR. .in_(value) IN lookup (identical to <<) native datetime data-type). The default supported formats are: Note: If the incoming value does not match a format, it is returned as-is. '%Y-%m-%d %H:%M:%S.%f' # year-month-day hour-minute-second.microsecond

one owner, so when we performed the join from Pet to Person, there was always going to be a single match. The situation is different when we are joining from Person to Pet because a person may have zero Search for values between low and high. .regexp(exp) Regular expression match (case-sensitive). .iregexp(exp) Regular expression match (case-insensitive). Method Meaning .bin_and(value) Binary AND. .bin_or(value) group_by(Latest.user) .alias('latest_query')) # Our join predicate will ensure that we match tweets based on their # timestamp *and* user_id. predicate = ((Tweet.user == latest_query.c.user_id)

one owner, so when we performed the join from Pet to Person, there was always going to be a single match. The situation is different when we are joining from Person to Pet because a person may have zero Search for values between low and high. .regexp(exp) Regular expression match (case-sensitive). .iregexp(exp) Regular expression match (case-insensitive). .bin_and(value) Binary AND. .bin_or(value) Binary alias('max_ts')) .group_by(Latest.user) .alias('latest_query')) # Our join predicate will ensure that we match tweets based on their # timestamp *and* user_id. predicate = ((Tweet.user == latest_query.c.user_id)

one owner, so when we performed the join from Pet to Person, there was always going to be a single match. The situation is different when we are joining from Person to Pet because a person may have zero between(low, high) Search for values between low and high. Method Meaning .regexp(exp) Regular expression match. .bin_and(value) Binary AND. .bin_or(value) Binary OR. .in_(value) IN lookup (identical to <<) native datetime data-type). The default supported formats are: Note If the incoming value does not match a format, it is returned as-is. '%Y-%m-%d %H:%M:%S.%f' # year-month-day hour-minute- second.microsecond