#1990: [patch] Oracle support in latest trunk
------------------------------+---------------------------------------------
Reporter: tzellman | Owner: adrian
Type: enhancement | Status: new
Priority: normal | Milestone: Version 0.92
Component: Database wrapper | Version: SVN
Severity: normal | Resolution:
Keywords: ORACLE |
------------------------------+---------------------------------------------
Comment (by anonymous):
Looking at the patch code, I see that the offset/limit implementation is
done using Oracle's row_number analytic function rather than using the
rownum pseudo-column. It seems to me that rownum would be simpler and
better. Tom Kyte
[http://asktom.oracle.com/pls/ask/f?p=4950:8:::::F4950_P8_DISPLAYID:44376372354520#44460244068927
says]:
{{{
If you use row_number() when you can use rownum (SHOULD use rownum) the
only thing you'll achieve:
lack of performance
increased resource usage
Your choice.
}}}
Also, I think the row_number function works from 9i onward. That shouldn't
be a huge roadblock since most have moved on from 8i by now.
--
Ticket URL: <http://code.djangoproject.com/ticket/1990>
Django <http://code.djangoproject.org/>
The web framework for perfectionists with deadlines.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" 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-updates
-~----------~----~----~----~------~----~------~--~---
