Changes between Initial Version and Version 5 of Ticket #16481


Ignore:
Timestamp:
Aug 21, 2011, 6:06:32 AM (13 years ago)
Author:
Aymeric Augustin
Comment:

Oracle doesn't support the combination of LIMIT and OFFSET. This is a very common source of question in forums.

I found this page which provides an analysis of this problem on several RDBMS: ​http://troels.arvin.dk/db/rdbms/#select-limit-offset

It says that the SQL we currently use, ORDER BY ... LIMIT ... OFFSET ..., isn't standard. But it's supported by PostgreSQL, MySQL and SQLite at least (the test passes on those engines). Also, it's the only solution supported by MySQL, and it's simple. As a consequence, I chose to add a special case for Oracle, and a comment to warn about the use of non-standard SQL.

Since the database cache backend isn't an industrial grade concept, I don't believe someone who has the resources to purchase an Oracle license will ever use it. This patch may be a bit hackish but it fixes the test suite with limited changes.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #16481

    • Property Keywords Oracle added
    • Property Owner changed from nobody to Aymeric Augustin
    • Property Triage Stage Unreviewed → Accepted
    • Property Has patch set

  • Ticket #16481 – Description

    initial v5  
     1
     2==  ==
    13{{{
    24$ python runtests.py --settings=test_settings.oracle cache
Back to Top