On 10/3/07, Ben Ford <[EMAIL PROTECTED]> wrote: > Hi Ian, > OracleQuerySets currently do not have any slicing ability AFAIK, apart from > returning a slice of the qs._result_cache list... in the backend refactor > all of the logic for building the SQL is in a function called > limit_offset_sql on the DatabaseOperations class. This is overridden in > oracle/base.py to return ''. it seems this is going to be addressed in the > queryset refactor coming shortly. > Ben
Ben, I don't know what it will look like after the refactor, but in the current trunk, the limit_offset_sql function isn't flexible enough to do the level of query rewriting that's necessary to support the feature in Oracle, and so it's done by directly overriding QuerySet._get_sql_clause instead (the comment about handling limit/offset in oracle/query.py is erroneous). Supporting limit/offset was the primary reason for subclassing QuerySet in the oracle backend in the first place, so if there's a bug relating to it in trunk, I'd like to hear about it. Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
