Re: Removing Oracle from Django core in 3.0

Firstly, greetings everyone I'm new here but I am looking to learn and use Django more so... I see the edge cases being a issue but I am for Oracle going out of core. And in order to maintain and/or expand MySQL support how is the the implementation of MariaDB going so

Re: Removing Oracle from Django core in 3.0

Another related question - https://docs.djangoproject.com/en/dev/internals/contributing/writing-code/unit-tests/#testing-other-python-versions-and-database-backends provides some terse advice for running the unit tests with different backends. Is that essentially what is happening with a

Re: Removing Oracle from Django core in 3.0

That's the query I would use. The 'oracle' keyword might not be assigned completely but you can scan through all the "Database layers" tickets fairly easily and add it to any that are missing. On Monday, November 26, 2018 at 12:25:06 PM UTC-5, Dan Davis wrote: > > Related question - how would I

Re: Removing Oracle from Django core in 3.0

Related question - how would I search for Oracle specific issues. I found this query: https://code.djangoproject.com/query?status=assigned=new=~oracle=Database+layer+(models%2C+ORM)=id=summary=status=component=owner=type=version=1=id However, I'm not sure how much I can rely on the keywords.

Re: Removing Oracle from Django core in 3.0

Indeed, the initial setup of the database takes a horrendous amount of time (like 30 minutes to init an empty database!). On Mon, 26 Nov 2018, 14:12 Johannes Hoppe To quote the documentation: > https://github.com/orf/django-docker-box/blob/85780dcc81d62a4c0c1142b45eb69e825d97b074/README.md#oracl

Re: Removing Oracle from Django core in 3.0

To quote the documentation:  https://github.com/orf/django-docker-box/blob/85780dcc81d62a4c0c1142b45eb69e825d97b074/README.md#oracle "As usual Oracle is a bit more complex to set up.” ;) -- Johannes Hoppe www.johanneshoppe.com Want to chat? Let's get a coffee!

Re: Removing Oracle from Django core in 3.0

I haven't tried it out for Oracle yet but Tom Forbes' django-docker-box seems to make it a not-too-painful process[0] Simon [0] https://github.com/orf/django-docker-box#oracle Le lundi 26 novembre 2018 04:05:41 UTC-5, Johannes Hoppe a écrit : > > > On Monday, November 26, 2018 at 9:49:46 AM

Re: Removing Oracle from Django core in 3.0

Johannes Hoppe kirjoitti ma 26. marrask. 2018 klo 11.05: > > On Monday, November 26, 2018 at 9:49:46 AM UTC+1, Florian Apolloner wrote: >> >> Hi, >> >> I personally agree with Mariusz here. Oracle might have it's own quirks, >> but the same could be said for any database. Taking my experience

Re: Removing Oracle from Django core in 3.0

Hahaha, yes kind of :P If they become a corporate sponsor it shut up immediately ;) On Monday, November 26, 2018 at 9:08:13 AM UTC+1, Carlton Gibson wrote: > > Hi Joe!  > > On 26 Nov 2018, at 09:05, Johannes Hoppe > wrote: > > I don't mind putting in extra work for an open source database. For

Re: Removing Oracle from Django core in 3.0

On Monday, November 26, 2018 at 9:49:46 AM UTC+1, Florian Apolloner wrote: > > Hi, > > I personally agree with Mariusz here. Oracle might have it's own quirks, > but the same could be said for any database. Taking my experience with the > ORM into account I do not think that Oracle requires

Re: Removing Oracle from Django core in 3.0

Hi, I personally agree with Mariusz here. Oracle might have it's own quirks, but the same could be said for any database. Taking my experience with the ORM into account I do not think that Oracle requires much more work (if at all) than any other database. I think in the end it does not matter

Re: Removing Oracle from Django core in 3.0

Hi Joe!  > On 26 Nov 2018, at 09:05, Johannes Hoppe > wrote: > > 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. Is the issue “How to squeeze money out of Oracle?” — On that, did

Re: Removing Oracle from Django core in 3.0

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

Re: Removing Oracle from Django core in 3.0

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

Re: Removing Oracle from Django core in 3.0

My employer is an Oracle shop. I would dedicate myself to Oracle specific bugs to prevent removing Oracle from core. That said, we'll probably be off Oracle and onto the cloud and Postgresql by 3.0. On Sun, Nov 25, 2018 at 1:36 PM Adam Johnson wrote: > Interestingly, I didn't receive your

Re: Removing Oracle from Django core in 3.0

Interestingly, I didn't receive your first email Johannes, only Tim's reply. I can't even find it in spam. Maybe Gmail's filters highly associate mentions of "Oracle" with spam? :/ I agree that with Tim that it's going to be easier to keep it in core if development is going to continue. Any

Re: Removing Oracle from Django core in 3.0

Move database backends out of the Django's core sounds great. Em domingo, 25 de novembro de 2018 15:54:21 UTC-2, Tim Graham escreveu: > > I can't find a past discussion specific to Oracle, but it's not a new > proposal. See >

Re: Removing Oracle from Django core in 3.0

I can't find a past discussion specific to Oracle, but it's not a new proposal. See https://groups.google.com/d/topic/django-developers/O-g06EM6XMM/discussion for "Moving database backends out of the core." I think removing Oracle from core would only increase the maintenance burden. Since