Opened 7 years ago

Closed 7 years ago

#5499 closed (wontfix)


Reported by: tunix@… Owned by: nobody
Component: Database layer (models, ORM) Version: master
Severity: Keywords: db api intersect
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: UI/UX:


In my example, I have a model called Event. I have a search box and want to search against 3 fields of the model: title, tags and text. When the user types "keg" in the box, all events that have "keg" in their title OR tags OR text will be displayed. If the user types "keg" and "ger" in the box, then all events that both have "keg" and "ger" in their title OR tags OR text will be displayed.

As a result, the queries must be intersected to do achieve this. It would be nice if we could have a intersect() function in the DB-API.

Attachments (0)

Change History (1)

comment:1 Changed 7 years ago by Simon G. <dev@…>

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to wontfix
  • Status changed from new to closed

I think you're well into the custom SQL zone here...

Add Comment

Modify Ticket

Change Properties
<Author field>
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.