On Monday, November 26, 2018 at 8:27:02 AM UTC+1, Mariusz Felisiak wrote: > > Hi > > I don't agree that the Oracle back-end is poor implemented (I > probably should not treat this personally 😀). It is as well maintained as > any other back-end that is in the core. We don't have much more open > tickets in the Oracle back-end then in others and IMO it is easier to > maintain it in the core. > Haha, sorry, I didn't mean to offend anyone. I hope you can see past my poor choice of works. I just noticed that a lot of oracle specific behavior is implemented in the base backend, where other backends like MySQL opt to override methods to add their db specific behavior.
> >> - *Technical:* >> - *Oracle does not support may features* >> - *due to its lack of features, a lot of edge case handling to the >> base database backend which drives overall complexity* >> >> Just like SQLite or MySQL I don't think that we should leave only > PostgreSQL in the core 😀. > They are actually a lot better maintained then Oracle, which leads me to believe it's not used that often. Besides both DBs you mentioned are open source. I don't mind putting in extra work for an open source database. For a private corp that makes 4bn in revenue... not so much. Maybe a separate backend project, would also see more support from Oracle. > >> - Development: >> - Oracle does not run in the regular CI suite, in fact master is >> broken right now >> >> I don't see any failures in djangoci.com. Maybe you use an unsupported > version of Oracle? > > Best > Mariusz > > > W dniu niedziela, 25 listopada 2018 11:21:02 UTC+1 użytkownik Johannes > Hoppe napisał: > >> Hi there, >> >> I have recently refactored some bits in the database backend and came to >> realize that a lot of the complexity in there comes from the poor >> implementation of the Oracle backend. >> Fun fact, did you know that Oracle tests don't run by default and that >> the current master, fails on oracle ;) >> >> Anyhow, I want to come to a conclusion about the following matter: >> >> Should we remove the Oracle database backend from Django core in the 3.0 >> release? >> >> Here are a couple of reasons, why I believe this to be a good idea: >> >> - License >> - Oracle is Proprietary software >> - Money >> - Oracle is not a sponsor of the Django Foundation, but makes 40bn >> in revenue >> - Technical: >> - Oracle does not support may features >> - due to its lack of features, a lot of edge case handling to the >> base database backend which drives overall complexity >> - Development: >> - Oracle does not run in the regular CI suite, in fact master is >> broken right now >> - entrance barrier for first time contributors is high >> - one needs to accept a non open source license >> - register with oracle >> - go through a very complex setup process >> >> Of course there are some users who use Oracle and I don't want to keep >> them hanging. I simply believe the database backend should be developed >> separately from Django. >> This could even be helpful for the Oracle community. Since oracle is >> enterprise only, they usually looks for longer support cycles than what >> Django want's to offer. >> >> Ok, I made my case, I am curious, what do you guys think? >> >> Best >> -Joe >> > -- 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 django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/15a8d317-7749-43f4-a760-e07bb2aab74f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
