#37219 closed Cleanup/optimization (fixed)
Add GeneratedField example to PostgreSQL search reference.
| Reported by: | Carlton Gibson | Owned by: | Carlton Gibson |
|---|---|---|---|
| Component: | Documentation | Version: | 6.0 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I was reading the Performance section of the Postgres Full text search reference.
The requirement to use a trigger with SearchVectorField made me think of using a GeneratedField. I think that would be a good example to add.
Change History (7)
comment:1 by , 3 weeks ago
comment:2 by , 3 weeks ago
| Triage Stage: | Unreviewed → Accepted |
|---|
I think we should even considering replacing/dropping the trigger section entirely given there is almost no reason I can think of where it's preferable over a generated field particularly if Postgres eventually add support for indexing virtual ones.
comment:3 by , 3 weeks ago
I wondered if there might be an example (maybe cross model) that wasn’t compatible with generated field’s constraints. (But I don’t have one to hand.)
comment:4 by , 3 weeks ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
Note:
See TracTickets
for help on using tickets.
PR