My Notes

`or` behavior

User ored a condition that checked a property with an empty set value which caused a previous query result to go away
Confusing for users because or generally leads to more results, not less
Final condition was intuitively false even though it was actually {}, but that doesn’t change the fact that other conditions were true which leads to surprise around the result
or? operator?
working with booleans Working with booleans — Cheatsheets | EdgeDB Docs
- Surface this sooner
user should use ?= instead of = for comparison where the value may be empty
Talk about it when talking about filtering in selects, first place this comes
Messaging around losing FTS in 3.0
- Sent to Elvis via Slack DM 2023-04-06
- indexing?
- Stashed for 4.0. Could ship in a future 3.x release.
- “We are not just exposing postgres” Ask if anyone asks why not expose the PG API
- Can share some RFCs to answer those questions
- Only tested on PG, not on elastic
- To play it safe, holding it back from 3.0
- Not exposing: want to have pluggable. Exposing PG
- Want to offer an elasticsearch-like thing in Cloud (Not for user consumption) or can use locally with PG
- Look at full-text search RFC
- Write something and Elvis will help edit it.

Interactive tutorial- embed explain UI
- Show how to look at the explain output and analyze queries