Це відео не доступне.
Перепрошуємо.
How to implement lightning-fast case insensitive search in Bubble
Вставка
- Опубліковано 31 лип 2022
- So here is the thing, building search features in Bubble apps is hard. There is a bunch of ‘fuzzy search’ and ‘search & autocomplete’ plugins, but in my experience, they are all either slow, expensive, or unreliable.
The main reason for this is that these search plugins live in the front-end of your application, which means they run locally on your laptop or phone. Therefore they need to 1) download a ton of data and then 2) use your limited local computing power and memory to do all the searching.
So, let’s build our own super-fast search function that can search data directly in Bubble’s database without downloading it first.
Amazing tutorial! It worked really well!
Just to add more info, I tried with lowercase instead of uppercase, and it worked equally well.
Also after the :lowercase in the arbitrary text box I added the operator :trimmed because when I was writting on the search box in my phone, the autocomplete of my phone added a blank space. For example I wanted to write "Brian" and with the autocomplete it wrote "Brian " with the space. I think is a better UX taking in account that many users write using autocomplete. The trimmed operator deletes the last blank space in a text, but not the space between two words. It worked really well with this. Hope it helps.
This was a really great help, the best solution so far related to this subject. In 2 minutes I made the searches in my clients app much faster, efficient and reliable (bye bye weird plugins for this purpose). Thanks and congrats for your channel
Thanks a lot for tutorial. Sad you stopped putting more videos to the channel
Thank you so much for this tutorial
I still come back to it from time to time.
Wow, the best way to implement I've seen so far. Thank you very much.
love this tutorial, solved my problem about search input, now i can put all my category. thanks in advance
Quick question: What element were you using for your Search messages input element? Fuzzy search only allows text. The built-in searchbox only autocompletes for 1 data type. Just a text box then?
How do you include partial searches like 'fin' outputting 'finally'?
partial searches work
Hi Damian, I'd be curious how this "filtered" expression conbined with "advance" filtering in your RG performs for a list of 1000 to 10000 messages.
In my experience, this is actually very slow above 100 records, but maybe this case is different.
I'm asking because i'm looking for a solution for search of appr 10K records
omgosh, I have been trying to solve this for 20+ hours! where's your donate button?
much appreciated! don't have one though :)
Works perfectly, thanks!!!
Looks like an interessting solution. bit is it really fast with 20K entries in my database?
Well done and thank you!
Hey that was great help. I was wondering if you could do a tutorial on how to implement this search but with an external API instead? I'm having weird behaviours with Fuzzy Search plugin where it doesn't show the same matches are the data source. Often I just want to return the first item return from the Data source instead of needing to do a fuzzy match
worked for me, thanks.
I love u!
Thank you!
Love this detailed walkthrough 🙌 I would be interested to see if this could scale though. In my experience using the Advanced filtering slows Bubble down A LOT when you start getting more than a couple hundred rows in a table (which is very easy to do).
yep, unfortunately, Advanced filters are also computed client-side... maybe one could save a capitalized version of the message and avoid the advanced filter
This is great! But I’ve noticed when you have lots of data such as messages, the search function becomes really slow
yep, unfortunately, Advanced filters are also computed client-side... maybe one could save a capitalized version of the message and avoid the advanced filter
@@buildwithdamian I would love to see another tutorial on that!
Hey DJ, great video. Thanks for sharing how to do this. I've stumbled into an issue though that I can't make sense of. I've made it all the way to 7:29 in the video.
Company Name (source text) -> Filtered -> Advanced -> Source text to UPPER -> Contains -> Arbitrary Text -> Search text to UPPER.
The problem is that while case sensitivity seems to be removed, CONTAINS is not working. I have to type in the ENTIRE Company Name for this to work. But it works without case sensitivity.
Any ideas? Super strange, I've doubled-checked everything countless times.
Hi Al! Not sure what the problem is - maybe it just takes a second to do the filtering? as i found out in the meantime, the advanced search does not deal super well with large data sets, as its also executed client side...
@@buildwithdamian Don't think time is the issue. I've waited quite a while and the full-name search works quickly. Super odd.
du bisch schwizer, oder? :D
Haha saisch ma khörts?