Full Text Search PostgreSQL

use plainto_tsquery instead of to_tsquery, because to_tsquery does not escape the sql letters like ', \, !, so the query can be easily injected

if we need to use search on 2 tables then how to build an index in this case.
pls help <3

very helpful, thanks!

OMG when you brought up TypeORM it was like a surprise celebrity showing up. SO COOL! I feel like this made just me. Was trying to also figure ElasticSearch for our TypeORM/Postgres setup. This is perfect!

Right to the point with great examples. Thanks!

Postgres Generated columns would be really useful for generating search documents as changes are made. Its also a bit simpler than triggers.

Great explanation.. saved a lot of time that I wasted searching over the internet.

i was just looking up this topic, clicked on the video and half way though realised its from ben

very usefull, thank you.

How do you add these indexes automatically on insert or update?

trigrams

You're doing great. Keep going! Thank you very much

EXCELLENT LESSON, PERFECT, SUBLIME, THANKS THANKS BEN AWAD!!!! A HUUUUUUUUUUUUUUUUGE THANKS!!!!! :D

MySQL vs PSQL please

I noticed that using tvector make search 2 times slower comparing to "and (like '%abc%' or like '%bcd%'), on top of this tvector performance is not stable, sometimes its say 6 seconds, sometimes 11 seconds to get the response

A little late, but does anyone know how can i implement something like the initial example, that searches a bunch of keywords? The behavior I want is to get every result that matches at least one of the keywords, but ordered by number of matches (and if possible, still considering the given weights for the fields, as a match in the title is still more valuable than a match in the description)

You are the man.

I like how you followed start simple finish master approach. Thank you for your awesome contents once again!