Timeline for Postgres full text search with multiple columns, why concat in index and not at runtime?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 29, 2014 at 18:51 | answer | added | Neil McGuigan | timeline score: 6 | |
| Mar 23, 2012 at 15:03 | history | edited | latentflip | CC BY-SA 3.0 |
FIxed AND in alternative query to OR as it should have been.
|
| Mar 23, 2012 at 11:51 | answer | added | user1593 | timeline score: 3 | |
| Mar 23, 2012 at 2:51 | history | tweeted | twitter.com/#!/StackDBAs/status/183023087552430082 | ||
| Mar 22, 2012 at 16:40 | comment | added | jcolebrand♦ | You're correct in your guess. I would encourage you to self-answer if no-one else does, Jeopardy style here. | |
| Mar 22, 2012 at 15:49 | comment | added | swasheck |
I'm not really certain how concatenating the title into the body and then indexing that would give much value, though I am open to correction. I would probably just stick with indexing them separately. Also, if it was some wacky one-off that somehow required you to concatenate, then I guess you could just run the query ad-hoc.
|
|
| Mar 22, 2012 at 15:01 | history | asked | latentflip | CC BY-SA 3.0 |