Hi folks,
I'm working on a fairly data-heavy (as opposed to content-heavy) application, and I'm trying to create some reusable code for sortable HTML tables (not relying on Javascript, since there are a number of drawbacks to that). I'd like each model to be able to provide a list of columns it's allowed to sort itself by (this will probably include complex calculated fields, so it may not be feasible in the database, and there may be fields that are in the DB but I want to prohibit sorting on), so as to decouple the sortable-field lists from the general-purpose (i.e. not model-specific) sorting code. However, since this information applies to the class, rather than to each instance of the class, it doesn't seem to make sense to create it as a normal attribute of a class, which would cause it to be saved to the database. Neither does it make sense to me to store it entirely outside the class, since it's information about the class. Can I add things to Meta? Or should I define the sorting options in a manager for each class (since sorting is a table-level operation), alongside the methods that pull up the querysets and append the calculated fields to them? Or does this belong somewhere else entirely (like a specialized method for each view)? Any suggestions? Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
