I'll agree with you. Thinking about it again 6 seconds is pretty bad. I don't know how the authorized_values or icon sets are laid out in the database. I'm sure it wouldn't be hard to add the dimensions to the authorized_values. As I recall those are structure something like MARC, so just give some subfield to the dimensions. Having it stored with the iconset would be good too, but I don't know if or where that is in the database.
My idea in the beginning was something to this effect. I don't really feel like trying to figure out authorized values right now, but I will look to see if iconsets are kept in the database somewhere other than that. On Thu, 2009-02-12 at 11:10 -0500, Galen Charlton wrote: > Hi, > > On Thu, Feb 12, 2009 at 10:57 AM, Michael Hafen > <mdha...@tech.washk12.org> wrote: > > Given 20 search results on a page, and (currently) at most 3 items per > > results, that's about an extra 6 seconds per page load, worst case. > > That doesn't seem terrible to me. > > That actually sounds rather expensive to me - six seconds is an > *eternity*. ;) I suggest storing the dimensions in the database when > an icon is added or assigned to an itemtype or authorized_values, > rather than recalculating it every time. Alternatively, the maximum > height and width could be stored as an attribute of the iconset. > > Regards, > > Galen -- Michael Hafen Systems Analyst and Programmer Washington County School District Utah, USA for Koha checkout http://koha-dev.washk12.org or git://koha-dev.washk12.org/koha _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha.org http://lists.koha.org/mailman/listinfo/koha-devel
