The FASTEST possible way to query data

[@adebiyial]

“Sequential table scan" is a very nice and helpful description

[@JonMeyers]

It makes a lot of sense!

[@adebiyial]

@@JonMeyers Yes, it does, particularly because it helps me picture how slow some operations can be due to that.

[@whoman7930]

That end gave me a good giggle 😆

[@Karnadagan]

yeah, it was so cool!

[@timondalton8731]

Super clear explanation. Thank you

[@letopizdetz]

I need to brush up on multicolumn index. thanks for reminding me

[@JonMeyers]

We have another video coming soon specifically focused on multi column indexes and the differences between that and a covering index! 👍

[@mrrolandlawrence]

multi column indexes and indexed views are the way!

[@JonMeyers]

Videos coming soon on both of these!

[@eleah2665]

Cool. Thanks Jon, Sincerely, Ehd

[@JonMeyers]

Glad you enjoyed it! 🙌

[@sumitpurohit8849]

Please make this indexing one for vector embeddings as well.

[@JonMeyers]

Great idea! This one is coming soon!

[@flnnx]

If our backend has a relatively big function that needs to execute multiple DB operations, is it okay if we extract some of the code into utility functions and re-initialize the Supabase client to perform those tasks, or would it be better to pass down the already initialized Supabase client from the main function to the utility functions?

[@himesh_89]

How does this effect while working the supabase js package?

[@TobiasMars]

Nice video! but where is my file upload/download and storage with Remix.js tutorial? :DDD

[@joshredgrift5133]

would this also improve performance on LIKE clauses? e.g. (SELECT * FROM people WHERE username LIKE '%jo%';)

[@luisandrade1291]

Why was this video reuploaded?

[@Noita_]

So I could see it

[@JonMeyers]

We didn’t want ​@@Noita_ to miss it!

[@cesarsfalcao]

it grows lily -nearly XD