···104104105105#### Fuzzy Matching Example
106106107107-The `fuzzy` filter uses PostgreSQL's trigram similarity for typo-tolerant search:
107107+The `fuzzy` filter uses PostgreSQL's trigram similarity for typo-tolerant
108108+search:
108109109110```graphql
110111query FuzzySearch {
···124125```
125126126127This will match track names like:
128128+127129- "Love" (exact)
128130- "Love Song"
129131- "Lovely"
···132134- "Loveless"
133135134136The fuzzy filter is great for:
137137+135138- Handling typos and misspellings
136139- Finding similar variations of text
137140- Flexible search without exact matching
138141139139-**Note**: Fuzzy matching works on the similarity between strings (using trigrams), so it's more flexible than `contains` but may return unexpected matches if the similarity threshold is met.
142142+**Note**: Fuzzy matching works on the similarity between strings (using
143143+trigrams), so it's more flexible than `contains` but may return unexpected
144144+matches if the similarity threshold is met.
140145141146#### Date Range Example
142147···773778 uri
774779 alt
775780 photo {
776776- url(preset: "fullsize")
781781+ url(preset: "feed_fullsize")
777782 }
778783 socialGrainPhotoExifs {
779784 fNumber
···795800query MyGrainGalleries {
796801 socialGrainGalleries(
797802 where: { actorHandle: { eq: "chadtmiller.com" } }
798798- orderBy: { field: "createdAt", direction: DESC }
803803+ sortBy: [{ field: createdAt, direction: desc }]
799804 ) {
800805 edges {
801806 node {
···829834 uri
830835 alt
831836 photo {
832832- url(preset: "fullsize")
837837+ url(preset: "avatar")
833838 }
834839 aspectRatio
835840 createdAt