Ticket #453 (task)
Opened 4 years ago
Last modified 3 years ago
Cache user preferences
Status: new
| Reported by: | douglm | Assigned to: | douglm |
|---|---|---|---|
| Priority: | major | Milestone: | Bedework 3.7 |
| Component: | unclassified | Version: | |
| Keywords: | Cc: | ||
We get a lot of sql to read preferences at the start of a request. Perhaps the server should cache preferences and look for a change (seq# will do it)
Change History
11/11/09 10:11:36: Modified by douglm
12/09/09 01:14:51: Modified by douglm
- milestone changed from Bedework 3.6 to Bedework 3.7.

This wasn't prefs - it's multiple requests of this form:
select collection0_.viewid as viewid0_, collection0_.bw_calpath as bw2_0_, collection0_.bw_path_positon as bw3_0_ from bw_view_collections collection0_ where collection0_.viewid=?When building a filter. Probably from a call on getViewFilter