Comparison operators on indexed+checked attrs

[dwwoelfel]

Adds $gt, $lt, $gte, and $lte comparison operators for indexed attrs with checked types.

If person.birthdate is an indexed attr typed as a date, you can do something like:

db.useQuery({person: {$: {where: {birthdate: {$gt: new Date(1986, 5, 6)}}}})

How it works
We add new partial indexes on the triples table that extracts the typed data from the json. This is the number index for example:

create index if not exists triples_number_type_idx on triples (
    app_id,
    attr_id,
    triples_extract_number_value(value),
    entity_id
  )
  where ave and checked_data_type = 'number';

Our comparison query uses the index we created:

select * from triples
where app_id = :app_id
  and ave
  and attr_id = :attr_id
  and checked_data_type = 'number'
  and triples_extract_boolean_value(value) > 10;

->  Index Scan using triples_number_type_idx on triples  (cost=0.27..8.30 rows=1 width=143) (actual time=0.027..0.226 rows=221 loops=1)
Index Cond: ((app_id = :app-id)
              AND (attr_id = :attr-id) 
              AND (triples_extract_number_value(value) > '10'::double precision))

For strings, we use a gist index with the pg_trgm extension. It allows us to use the index for like queries and potentially opens up the possibility for doing fuzzy search later.

Other changes

1. Uses the new type indexes for queries--it should be more efficient than using the regular ave index on json. I wonder if we should disable that index for untyped data.
2. Validates that the query parameters match the type of the attr. You'll get an error if you try to do:

   {:where {:checkedNumberAttr "string"}}
   

TODOS before deploy:

• Manually add all of the indexes with create index concurrently so that we don't lock up the db when running the migration
• Run the migration

[github-actions]

View Vercel preview at instant-www-js-checked-idxes-jsv.vercel.app.

[dwwoelfel]

We already do all the filtering in the store, so this saves us an extra comparison on the data.

[dwwoelfel]

Making this a macro helps jump-to-definition jump to the place is-pretty-eq? is used instead of jumping here.

[stopachka]

...This is beautiful!