#35053: Limiting QuerySets is not database platform agnostic
-------------------------------------+-------------------------------------
Reporter: irfanhakim | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: duplicate
Keywords: queryset, database, | Triage Stage:
documentation | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => duplicate
* easy: 1 => 0
Comment:
Duplicate of #10099.
> Django's documentations on ​Limiting QuerySets and ​MariaDB notes does
not seem to indicate that the Limiting QuerySets feature should not be
database platform agnostic.
We cannot document all database caveats, and the current error is clear
enough.
> I would also appreciate any pointers on how to still achieve a similar
enough outcome of limiting a QuerySet to a specified number when using
MariaDB (or other supported databases that is not PostgreSQL).
This is a support question, for which you should use
[https://code.djangoproject.com/wiki/TicketClosingReasons/UseSupportChannels
support channels].
--
Ticket URL: <https://code.djangoproject.com/ticket/35053#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018c8aa30872-e91a1743-02ed-41a1-9e83-c096b4f25440-000000%40eu-central-1.amazonses.com.
