On Jun 17, 1:25 pm, Joshua Russo <joshua.rupp...@gmail.com> wrote: > Is there a generally accepted workaround for the problem of sorting > relational models by more than one field? I have a model that > represents recurring payments between a person and an object and it > would be really nice to order by the object, year, and creation date > in the admin app change list.
I forgot mention, one thought I had was to create a db column for sorting that was updated by a trigger on the table. I realize a trigger will be dbms specific, but i'm not finding many other options. Though I would also like to avoid extra steps after I run an initial snycdb for that table. Is there anywhere I can slip in arbitrary sql into the model syntax, to be run after the table is created? Or, is there functionality in Django that I can utilize as opposed to a trigger. I've seen _sort db columns in some tables. Is there a way to hook into or override the functionality in Django that manages that field? Thanks Josh --~--~---------~--~----~------------~-------~--~----~ 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 django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
