Hi Paolo,
I'm quite surprised that you've started a new thread for something that
was already discussed, you could always add a comment to the existing
thread e.g.
https://groups.google.com/g/django-developers/c/dg8BUVHKOo4/m/5uFVmdWCAwAJ
> I wanted to share the frustration of seeing yet another great new ORM
feature blocked due to Oracle compatibility:
https://github.com/django/django/pull/16417
I'm not sure how you reached this conclusion. This is not blocked due
because of Oracle compatibility. I will review it and try to merge it
before the Django 5.0 feature freeze. You have to be patient, it has
nothing to do with Oracle. I just need more time as it's complicated
feature, e.g. it took me 2 weeks to review and merge PR with database
defaults. I do my best to avoid regressions and provide stable feature,
unfortunately such pedantic approach takes time.
> Over the last few months, I've tried to encourage newcomers and young
users to contribute to Django and they almost always ran into the need to
provide compatibility to Oracle, so much so that they eventually gave up
contributing.
Really? Django is not only the ORM. It is easy to demonize Oracle. I'm
working with contributors on daily basis, and don't remember anyone who
would resign because we have builtin Oracle backend. We don't have much
more open tickets in the Oracle backend then in others*. *The number of
unsupported features is similar to SQLite or MySQL.
> The point is that I think Oracle is a historical anomaly among the
database backends supported by Django because it is the only one that is
not Open Source, it has irrelevant usage numbers
It's not an anomaly. Oracle support was a conscious decision, keeping the
ORM features Oracle-compatible is a good battlefield, that helps keeping
the ORM friendly for 3rd-party database backends as we have more feature
flags and hooks for custom behaviors.
> ... and the company that earns from it does not contribute in any way to
its maintenance or support
Should be also drop support for Windows for exactly the same reason?
(rhetorical question)
> I, therefore, suggest that we start a discussion on removing Oracle from
supported databases.
This was already discussed. I'm still strongly against it.
Best,
Mariusz
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/3878edbd-23cf-4854-afcf-08aefb01e0c7n%40googlegroups.com.
