Hi there, I've just been looking at some of django's internals trying to get my head round the backend refactor...
I seem to have no luck slicing oracle flavoured QuerySets. From reading the source it seems that the limit_offset_sql logic is going to be moved to a separate module (called query.py in the backend) but this file doesn't exist. There's also what appears to be a lot of limit and offset looking code in the _get_sql_clause function of the OracleQuerySet class. I'm not at all familiar with oracle I'm afraid, but am I right in thinking that this stuff should live in the limit_offset_sql function of the DatabaseOperations class and just needs to be moved? Or is there a deeper issue causing problems? Thanks Ben -- Regards, Ben Ford [EMAIL PROTECTED] +6281317958862 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
