···192192 --attach=foo:attendees.db \
193193 --sql="select Twitter from foo.attendees"
194194195195+## Running searches
196196+197197+The `search` command runs a search against the Twitter [standard search API](https://developer.twitter.com/en/docs/tweets/search/api-reference/get-search-tweets).
198198+199199+ $ twitter-to-sqlite search tweets.db "dogsheep"
200200+201201+This will import up to around 320 tweets that match that search term into the `tweets` table. It will also create a record in the `search_runs` table recording that the search took place, and many-to-many recorsd in the `search_runs_tweets` table recording which tweets were seen for that search at that time.
202202+203203+You can use the `--since` parameter to check for previous search runs with the same arguments and only retrieve tweets that were posted since the last retrieved matching tweet.
204204+205205+The following additional options for `search` are supported:
206206+207207+* `--geocode`: `latitude,longitude,radius` where radius is a number followed by mi or km
208208+* `--lang`: ISO 639-1 language code e.g. `en` or `es`
209209+* `--locale`: Locale: only `ja` is currently effective
210210+* `--result_type`: `mixed`, `recent` or `popular`. Defaults to `mixed`
211211+* `--count`: Number of results per page, defaults to the maximum of 100
212212+* `--stop_after`: Stop after this many results
213213+* `--since_id`: Pull tweets since this Tweet ID. You probably want to use `--since` instead of this.
214214+195215## Capturing tweets in real-time with track and follow
196216197217This functionality is **experimental**. Please [file bug reports](https://github.com/dogsheep/twitter-to-sqlite/issues) if you find any!