https://futureofcoding.org/ logo
Join Slack
Powered by
I added `ORDER BY` and `LIMIT` to the Firestore qu...
# share-your-work
m
I added 
ORDER BY
and 
LIMIT
to the Firestore query parser and I decided to create a playground for it: - Run queries - Load examples - See intermediate representations https://instadeq.github.io/firestore-query-parser-js/playground.html

https://www.youtube.com/watch?v=vgkMPdwBcS8▾

🍰 1
t
FWIW the most powerful and least understood semantics are the 'in' and 'array-contains-any', this is how you can do something similar to SQL joins efficiently.
maybe you could translate SQL joins to clientside joins
m
array operators are supported in the language
t
wait what are you building?
oh yeah cool
Copy code
a == 4 and b in ["r"] and c < 4.5 ORDER BY a, b DESC, c ASC LIMIT 5
m
we are adding firestore as a source on instadeq and until we have a visual query builder we needed a concise way to express queries, that's why I build this, it's just a way to take a query in and apply it to the firestore object
at some point I will implement the visual query builder and this one will dissapear from the UI
🍰 1
t
yeah like a SQL translation layer, yeah, thats cool!
BTW this popped up recently which seems to be trying to normalize access to DBs too https://observablehq.com/@observablehq/database-client-specification this is so their data cell query UI can hit multiple DB techs
👏🏽 1
Open in Slack
PreviousNext
Powered by