Opened 18 years ago
Last modified 19 months ago
#3254 new New feature
[patch] experimental fulltext search support for postgres, oracle and mssql — at Version 19
| Reported by: | Ronny Pfannschmidt | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | |
| Severity: | Normal | Keywords: | oracle fulltext search postgresql postgres mysql |
| Cc: | sam@…, johann.queuniet@…, hv@…, rboumart@…, dan.fairs@…, twidi@…, Matt Boersma, justinlilly@…, James Pic, robinchew@…, niwi@…, slav0nic@…, mpessas@…, tomi.kyostila@…, Matt Goldman | Triage Stage: | Accepted |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
I didn't like it was missing.
oracle, mssql : add a FulltextIndex for the Fields
postgresql: for each FulltextField add a extra tsvector Field named like "%(fieldname)_tsv"
Problems with sqlite fts:
- they stated a match statement may only be used once in a query
- it needs a very specific syntax to search multiple fields
- i have no idea how to get that into the ORM
Change History (22)
by , 18 years ago
| Attachment: | fts-pstgres-oracle-mssql.patch added |
|---|
comment:1 by , 18 years ago
| Summary: | [patch] experimental fts support for postgres, oracle and mssql → [patch] experimental fulltext search support for postgres, oracle and mssql |
|---|---|
| Triage Stage: | Unreviewed → Design decision needed |
comment:2 by , 18 years ago
| Cc: | added |
|---|
comment:3 by , 17 years ago
Typo in patch: plainto_tsquery in psycoph2/base.py should be to_tsquery
Corrected patch attached.
comment:4 by , 17 years ago
#4676 was a duplicate, and has an alternate implementation for PostgreSQL.
comment:5 by , 17 years ago
Patches attached to this ticket do not work correctly with PostgreSQL, please use patch http://code.djangoproject.com/attachment/ticket/4676/sql.diff in ticket #4676 (which also describes the correct database set-up by the way).
comment:6 by , 17 years ago
| Component: | Metasystem → Database wrapper |
|---|---|
| Needs documentation: | set |
| Needs tests: | set |
| Patch needs improvement: | set |
| Triage Stage: | Design decision needed → Accepted |
comment:7 by , 17 years ago
| Cc: | added |
|---|
comment:8 by , 17 years ago
| Reporter: | changed from to |
|---|
follow-up: 10 comment:9 by , 17 years ago
Postgres 8.3 now has full-text searching. Not sure if this changes anything here or not...
comment:10 by , 17 years ago
Replying to anonymous:
Postgres 8.3 now has full-text searching. Not sure if this changes anything here or not...
comment:11 by , 17 years ago
| Cc: | added |
|---|
comment:13 by , 17 years ago
Sorry, I meant june 2007 (The date format of trac is hard to read for germans ...)
comment:14 by , 17 years ago
| Cc: | added |
|---|
I added a Patch against 7231. It is only for postgres. But i think it would be straight forward for the other backend.
comment:15 by , 16 years ago
| Cc: | added |
|---|
comment:16 by , 16 years ago
| Cc: | added |
|---|
comment:17 by , 16 years ago
| Cc: | added |
|---|
comment:18 by , 16 years ago
| Keywords: | oracle fulltext search added |
|---|
This is a very simple little patch - if accepted it'll need some docs. Shouldn't be too hard to implement MySQL fulltext searching too, but this will require a special index to be created.