I've tried that also, but it ALSO only accepts field names. Its intention to be there is not to override previously set order clauses.
On 8월4일, 오후5시56분, Daniel Roseman <dan...@roseman.org.uk> wrote: > On Aug 4, 8:28 am, Daybreaker <daybreake...@gmail.com> wrote: > > > I want to run a query like this: > > > select * from bbs_article a, bbs_article_tags a2, bbs_tag t where t.id > > = a2.tag_id and a.id = a2.article_id order by (case when t.name = > > 'notice' then '' else t.name end) > > > which has a custom ordering rule. > > > As far as I know, Django model currently does not support such custom > > orderings, but only field-based native orderings. > > > How do I use the above sql in most clear way (like using typical model > > query with manually changed order clause), or is there any workaround > > to do the same jobs? > > Sounds like the queryset .extra() method with the order_by parameter > might > help.http://docs.djangoproject.com/en/dev/ref/models/querysets/#extra-sele... > -- > DR. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
