gloda could expose all support fulltext search variants on message objects

RESOLVED FIXED

Status

RESOLVED FIXED
10 years ago
10 years ago

People

(Reporter: asuth, Assigned: asuth)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

10 years ago
Created attachment 349862 [details] [diff] [review]
v1 add subject, attachment names, and everybody fulltext searches

Today, you can only fulltext search against the body of a message.  But imagine a world where you could fulltext search against subjects.  And a world where you could fulltext search against attachment names.  And yet another world where you can do all three at once!  But if you were to try and combine those worlds, they would explode, so don't do that[1].

1: The MATCH operator can only be used once per fulltext search table in a query.  I feel like this should be documented or enforced somehow in less of a "surprise, exception!" sort of way.  If we start more explicitly binding UI to constraints, it should probably be integrated into that.
Attachment #349862 - Flags: review?(dmose)
(Assignee)

Updated

10 years ago
Whiteboard: [has patch][needs review dmose]
(Assignee)

Comment 1

10 years ago
Now that I think about it, there will be no explosions.  Our queries are structured in such a way that I find it hard to believe we would run up against the MATCH operator limitations.  Mix and match fulltext searches to your heart's content.
(Assignee)

Updated

10 years ago
Attachment #349862 - Flags: review?(dmose) → review?(bienvenu)

Updated

10 years ago
Attachment #349862 - Flags: review?(bienvenu) → review+

Updated

10 years ago
Keywords: checkin-needed
Whiteboard: [has patch][needs review dmose]

Comment 2

10 years ago
fixed
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.