magic-removal: missing options from old query language

[hugo]

limit= and complex= are gone - but there is no doc on where they are gone. From the source I grok that limit= is gone to slicing, but since that's a bit different in behaviour (especially with selections where you could have less than your limit of rows - before it would just return the available rows or an empty set, now it will throw an error), this should be documented. And there is no notion on what to do with complex= query parameters, how to do those (this was done with queryset combinations, right? But there should be a sample in the docs).

If complex= is gone, shouldn't Q be removed from the source?

[Antti Kaihola]

[2485] seems to fix the case with fewer rows than the limit in the selection.

[Malcolm Tredinnick <malcolm@…>]

The complex keyword goes away and you just use a collection of Q objects now. This is partially documented in docs/db-api.txt, although it has the wrong location for Q, but a full check of those docs is needed anyhow.

I have updated RemovingTheMagic to show how to replace complex=... constructs. As akaihola mentioned, slicing has now been fixed to emulate the previous behaviour of limit. So that resolves both issues from here.

[Luke Plant]

Also, as an alternative to the 'Q' object method, you can do 'OR' queries by combining query objects directly, like this:

Reporter.objects.filter(name='Joe') | Reporter.objects.filter(name='Jane')