| From: | "Jackson, DeJuan" <djackson(at)cpsgroup(dot)com> |
|---|---|
| To: | Frank Morton <fmorton(at)base2inc(dot)com>, pgsql-sql(at)postgreSQL(dot)org |
| Subject: | RE: [SQL] Faster LIKE |
| Date: | 1999-01-20 16:17:21 |
| Message-ID: | F10BB1FAF801D111829B0060971D839F5F80BC@cpsmail |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
> I have an image database with keywords assigned to each record
> in the field "keywords" and often do:
>
> select * from images where keywords like 'dog';
>
> which works great with a small database, but slows down quickly
> with a large database.
>
> since the "keywords" field can have multiple entries, such as
> 'dog mammals fuzzy small' I was considering creating a separate
> keywords table where each word was an individual row and could
> therefore be indexed and fast.
>
> however, in the above example, I would like to match on "mammal"
> also (i.e., no "s" on the end) or any substring within the field, so
> the separate table does not do it either.
>
> This has to be a common thing. Are there any good solutions or
> research out there to solve this problem? Thanks.
See: pgsql/contrib/fulltextindex
Hope this helps,
-DEJ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jackson, DeJuan | 1999-01-20 16:20:42 | RE: [SQL] A path through a tree |
| Previous Message | Frank Morton | 1999-01-20 16:15:21 | Faster LIKE |