10.3.2013 23:03, Petite Abeille kirjoitti:
On Mar 10, 2013, at 9:36 PM, Ian Kelly <[email protected]> wrote:
These particular lookups have a long history of being tweaked due to
users coming up with installations where the existing queries did not
work. See tickets #5985, #11017 and #14149. I'd rather not reopen
this issue unless the current implementation can documentably be shown
to be broken.
Fair enough…
Another point perhaps worthwhile mentioning:
# There's no way for the DatabaseOperations class to know the
# currently active Oracle version, so we do some setups here.
https://github.com/django/django/blob/master/django/db/backends/oracle/base.py#L574
That information can be extracted from v$version, v$instance,
dbms_db_version.version, product_component_version, etc, etc. The choice is
yours.
Well since we're using Oracle in production and even we dared to venture
in GeoDjango parts we've some expertise to share.
To my knowledge there isn't any installations that does have cx_Oracle
as prepackaged version, and considering that even 5.0 version dropped
support for Oracle 8i. cx_Oracle 5.0 was released on December 2008.
Latest major version 5.1.0 was released on March 19th, 2011 (which is
about two years already) and latest 5.1.2 was released on July 6th, 2012.
Django docs state 4.3.1 as required - considering it's been released i
2007. I think it wouldn't hurt anyone to pump required version up to
5.1+ since that's the first version uncode ready and should support
python 3.3 as well.
Django itself drops quite fast security updates - Oracle does it a bit
longer, though it doesn't hang on older databases too long either.
Oracle 9.2 support ended July 2007 (extended 2010)
Oracle 10.1 support ended January 2009 (extended 2012)
Oracle 10.2 support ended July 2010 (extended 2013)
Oracle 11.1 supports ended August 2012 (extended 2015)
Oracle 11.2 support ends January 2015 (extended 2018)
So yes, people do use older version, though considering that any
sensible organisation has updated to newer supported versions as time
passes. Considering that Oracle is really marginal backend for Django
comparing to others I think it's reasonable to drop support older ones,
like 9.2 and 10.1.
Another nasty issue is that along the road license coverage has changed:
Oracle 9i, 10g and 11g does have differet set of spatial operators
included with Locator (free part with Standard and EE versions) and
Oracle Spatial (separately licensed with EE version of Oracle).
Now here comes the fun: All installations do have all spatial operations
as well. Only way to distinguish them is to consult Oracle
Locator/Spatial reference guide.
This is very bitchy thing with GeoDjango since you can easily go and
accidentally use something that you're not licensed for.
What comes to other issues - I'm not upset if Oracle backend fails
tests, since I don't expect it even to do pass all because "it's Oracle".
What comes to magic knowledge of Oracle, that I do have and I can share
it - but someone has to ask it first.
--
Jani Tiainen
- Well planned is half done and a half done has been sufficient before...
--
You received this message because you are subscribed to the Google Groups "Django
developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
