Photo Organizer

  • Status Closed
  • Percent Complete
  • Task Type Feature Request
  • Category Backend / Core
  • Assigned To
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version Devel
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Photo Organizer
Opened by pizza - 2006-05-12
Last edited by pizza - 2007-03-23

FS#55 - Speed up searches with temporary tables/views

Once a search is complete, cache the results in a temp table so we don't have to re-perform the search when we're paging through the results.

Closed by  pizza
2007-03-23 03:43
Reason for closing:  Won't implement
Additional comments about closing:  It's not going to happen, at least not this way.
pizza commented on 2006-06-06 21:18

What I have in mind -- create a new table, search_results { user_id, search_id, image, search_time }, and that would be populated with the list of matching images.

When a user performs a search, we erase the results of searches performed more than, say, 24 hours ago.

Sorting order would be performed on the final view.

pizza commented on 2006-06-06 21:27

search_id would be a sequence, naturally. the search_results table would need to be global.

temporary tables only last out the current "session", which is to say they'd go away as soon as the page is loaded, thanks to the non-persistent nature of our database connections.

pizza commented on 2006-09-20 19:12

We need to expand this to include a blob that contains the search parameters too. (eg advanced search, with X, Y, Z parameters)

pizza commented on 2006-11-30 19:40

OR, we can use the new session code; store the search results in the session. ooooo.

this simplifies (and vastly speeds up) the search code considerably!


Available keyboard shortcuts


Task Details

Task Editing