On Monday, December 11, 2017 at 11:19:12 PM UTC+1, Thijs van Dien wrote: > > In case there's an ORDER BY, I suppose you would need a wrapper. It's what > got me here in the first place; I was surprised how much difficulty this > user was having when attempting something rather basic: > https://stackoverflow.com/q/47716183/1163893. To come back to your point, > if the potential implementation could be smart about whether a wrapper is > needed, I don't object to that. >
Well, in the case of this specific issue, the error in question is caused by the choice of the database. It would have worked just fine in Postgresql :D As for removing the restrictions: By all means, patches welcome -- I'll happily review them. When I initially wrote union support I had a very specific usecase and a deadline (1.11 freeze) to get them in… Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/6bd443b7-114c-4ba6-8991-fe880f2cce2c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
