Excellent work on this akaariai! I think the best way I could help with this ticket, would be to use it in development in our future branch over the next few months with some of our complex reporting systems. Absolutely packed with work at the moment, so this would be in the next 2 - 3 months. Either way, this patch will defo get used :)
Cal On Wed, Jun 29, 2011 at 10:11 PM, Jeremy Dunck <[email protected]> wrote: > On Wed, Jun 29, 2011 at 3:55 PM, Simon Riggs <[email protected]> > wrote: > ... > > I'm not sure I like your ORM syntax to generate that though. Why not > > just pass through the case statement directly? That way *any* legal > > CASE statement can be used, without inventing new ORM syntax each > > time. > > Tables get aliased depending on queryset construction, so I doubt the > tables could be referred to in a stable manner. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
